Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Webinar transcript online-services-release-18 july2018


Published on

Webinar transcript: Online Services Release 27 & 28 – Technical Updates
Presented by Joel Benn from the ARDC

Published in: Education
  • Be the first to comment

  • Be the first to like this

Webinar transcript online-services-release-18 july2018

  1. 1. [Unclear] w ordsare denoted in square brackets and time stamps may be used to indicate their location w ithin the audio. Webinar: Online Services Release 27 & 28 – Technical Updates 18 July 2018 Video and slides available from the ANDS Website START OF TRANSCRIPT Gerry Ryder: Good afternoon everybody my name's Gerry Ryder I work with the ARDC, the Australian research data Commons, and I'm based in Adelaide. It's my pleasure to welcome you all here today to our webinar, where we'll learn about some of the latest updates to our online services and hear from the ARDC DevOps manager Joel Benn who I'm sure many of you are familiar with. So that's probably enough from me I'd like to hand over now to Joel who'll take us through the recent changes to ANDS Online Services Joel Benn: Well thanks everyone for tuning in I'm Joel Benn if you have met me I'm the DevOps manager for software development within ANDS, well ARDC I should say, and I'm going to walk through today some of the changes that we've put in for release 27 and 28. So things to be covered today I'm going to talk a little bit about the DOI service changes that were implemented in R28, a new feature in research data Australia which is a relationships graph visualization. As Gerry has mentioned already the international geo sample number service that was developed and I'll go through the the RVA increases vocabularies Australian notifications we've put in in release 28. I’m sorry I'm on a different computer and the mouse scrolls the complete
  2. 2. Transcript: Online Services Release 27 & 28 – Technical Updates Page 2 of 16 opposite way and so I'm bound to trip over a few times. I'll start with the DOI changes. So as part of R 28 we've put in a few changes which were sort of instigated from both DataCite and ANDS. We put out an email for comments to all DOI clients to feedback if there was any impacts on them and one of the changes that we proposed was the removal of client identifies from DOI strings. So there's a little example up here where you can see the top DOI got 16 which is client identifier and then realize how it will look now without those identifiers. So in the early days when we initiated the DOI system within ANDS we came up with the notion of putting a client identifies with in the DOI strings so that we could they identify who's DOI’s were who's. And also in a future enhancement we were looking at doing some sort of reporting on DOIs based on these identifiers. Now the reporting never eventuated and there are other ways now to get reports on your DOIs and there's also a new piece of functionality which I'll go into in a minute where DOI’s can now be transferred between owners. So, the client identifier sort of became redundant within the DOI string so we've decided to remove those out and it makes the DOI obviously a little bit simpler, a little less clunky I should say. So, the next change was around providing a separate prefix to each one of our DIY clients. So, this was a request that came through from DataCite earlier this year where they wanted ANDS to allocate a separate prefix to each one of our clients. And they've taken this approach globally so a lot of the other clients that are working through data side already have separate prefixes for their clients and we were one of the ones that were sort of lagging behind in updating our system. So DataCite asked us to do this for two reasons. One it reduces the chance of identifier clashes when people are minting so we're more likely to be unique when clients have their own prefix and it will also make again the DOI transfer between owners a bit easier. All clients as part of R28 have been updated so everyone has their new prefix and DOI clients probably already noticed that these are
  3. 3. Transcript: Online Services Release 27 & 28 – Technical Updates Page 3 of 16 sort of 10.2 something prefixes. and any DOIs were minted with the previous prefixes so therefore two, two five, six and seven will still be able to be updated by everybody so that there shouldn't be any impacts to anybody in regards to this change. One thing I will just make a note of is with the prefix that are assigned aren’t necessarily they aren't a client's prefix because they can obviously be transferred with this new functionality which I'll discuss in a second, so they're not owned by a client but they are allocated individually to clients. So the transfer of ownership. Some new functionality has been put in place within DataCite that allows enables and the transfer of DOIs between different clients or even different allocators. So ANDS is obviously an allocator but it could be another allocated signed up and people want to move to that allocator so that can also be done. And it could be one DOI, could be simple DOIs, could be all DOIs over the client has it to be transferred. To sort of start the process you drop an email to and they'll sort of walk you through the process. There's also some documentation up on the ANDS documentation space outlining sort of the steps that will be required. One of the main things is there will be sort of an email or I guess assigned sort of acceptance of the transfer of the DOIs between parties. That the new party that's going to be the owner has to have agreed to be taking these on board and be the manager going forward. The last one I'll just go on in the DOI changes. When we put out the proposal for R 28 we also were proposing to move to a new method of testing through the DOI service. This was the idea was to have a single test account for everybody so that it just be one account that people would hit. All the DOIs that people were testing would be listed under that single account. We did receive some valid feedback from clients and some concerns about this approach. So, we postponed that change and we're coming up with a new proposal will be sent out in a few weeks’ time for comment. Then we were aiming to sort of
  4. 4. Transcript: Online Services Release 27 & 28 – Technical Updates Page 4 of 16 release that in release 29 and we're sort of aiming for the lowest impact possible on our clients. So we'll be in touch then. The next piece of functionality is the Research Data Australia relationships graph. You can see on the right here this is kind of what it looks like. I'll go into the system in a second. So this originated from some work coming out of Research Data Alliance, and it was a project which was dubbed the research data switchboard. This project basically aggregates information from different publishers in all sort of areas of research output and draws connections between those to provide value. We’ve sort of taken that idea into Research Data Australia for our own data. The graph provides a visual representation of the relationships within RDA. Now one of the things that the graph sort of does that that we can't see in an RDA, in the existing RDA, was to find valuable relationships between objects. They can't easily be seen in a list view and I'll show you some examples in a second once I get into the system. We're looking at a future enhancement we will actually be pulling information out of the research data switchboard. So this will be things like where the research data switchboard knows about all things that are connected to say research outputs like ORCIDS or publications or data that we don't have in RDA. So that will sort of be a nice value add. There are some known issues primarily with Internet Explorer at the moment. We're having some issues with the rendering of SVG's in IE11 and Edge and so we're working on that at the moment and we'll hopefully get fixed out soon. The graph does still display but it's not as pretty as it should be. And so off we go over to the system so you can have a quick look. So here is a dataset within Research Data Australia. I'll just scroll down hopefully where I can see that. So, I have just scrolled down to sort of where the relationships section starts within a dataset record in RDA and you can now obviously see that this part of a card which is the graph visualization. By default, when you come in it's kind of minimized down so that we didn't take up too much real estate within the record but it also gives users a sort of indication that there is
  5. 5. Transcript: Online Services Release 27 & 28 – Technical Updates Page 5 of 16 something there. You can hover your mouse over and it will tell you sort of click to explore the graph but there's also this expanded collapse icon on the right here. So, underneath is the sort of view that we've had in the existing system up until now. This is the list few of the relationships between the objects that are either within RDA or external to RDA. The graph view basically is not a one-to-one representation of that list view because it does provide additional information, but what we can see in the graph is, I’ll just reorganize this a little bit so it is easier to see. We have this node here which is representing the current collection that I'm viewing or the data set that I'm viewing. It’s what we call a primary node and it's indicated by this grey ring around the collection. You can hover over each of the nodes and it will give you the title and its type so we can see here that we've got a data set and this is the title. So we can do that to each of the nodes. If you want to navigate off so if this this object exists in RDA or it is a resolvable link, so a link that exists on the web, so actually the title of the node will be provided as a link and you can click on that and navigate off to a website, a publication, or another object within Research Data Australia. The relationships between each of the nodes in the graph are displayed on bit sort of connector. We can see here we have association between two data sets. You can also hover over the connectors to find out the text for that relationship as well. There are instances where there are multiple relationships between two nodes. If I come over between this group and an activity I can see that the connector actually has the text multiple on it. Now if I hover over there I can see that there's multiple relationships and the’re expressed between the activity and the group there. One of things that that you can do within the graph: so, you can obviously zoom in and out within the graph, you can also reposition the graph. So when you start to get a really big graph you can zoom quite far out and reposition it to sort of fit the whole lot in view. You can also explore other nodes with a graph. So when the graph first loads we get the primary node and any sort of direct relationships to that node or some other nodes which I'll discuss in a minute. But there's also a way to
  6. 6. Transcript: Online Services Release 27 & 28 – Technical Updates Page 6 of 16 explore these extra nodes that were displayed in the graph. So, we can see between this data set we have - managed by this party, which is John Scott. Now whoever's discovered this record they may have come from Google doing a search and discover this data set and what they've found is the found that John Scott's actually the manager of this data set. And they may like to know what other data sets John has a connection to. What we can do is we can double click on John and this will basically attempt to load any other relationships that John has within Research Data Australia. So, this is brought in another node that's directly related to John. So, from this you can see that this node is quite a bit bigger and this is what we call a cluster node. We basically put clusters within the graph when there are more than 20 single nodes with the same relationship to another node and they are the same type. So, if I hover over the cluster you can see here that we've got 103 datasets that are managed by John. One of the nice things in the clusters are that they tidy up the graph a bit so if I didn't have the cluster I would have 103 nodes on my graph making it look a bit like a hedgehog. It also provides a way to access these records within RDA. All these datasets they exist in RDA and the link up here will basically take me to a search result where I can then further filter those records down by all the other filters within RDA. It might be by subjects or by type. It just makes it a little bit easier to sort or find what the user might be looking for. I'll just flick back to the graph. In terms of highlighting the relationships within the graph you can hover your mouse over a node and it will basically gray out that anything that's not directly related to the node that you're hovering over. here we can see this activity is related to almost everything except the data set on the right and the cluster above. One of the things that can happen is, if there are no additional relationships and you double click a node, it'll basically just sit there. But this activity again, user might I have come across this collection and they want to find out this there's a bit of interest here because this collection or this data set is an output of an activity, what else came
  7. 7. Transcript: Online Services Release 27 & 28 – Technical Updates Page 7 of 16 out of this activity? I can double click on the activity, like I could do before for John, and this will now load any of the relationships to this activity. What we'll get is an extremely busy graph, so I'll just zoom out a bit. Now we can see this activity that we've just double clicked on has relationship to a lot of other data. This is obviously a really good way to say that there's really lots more information within RDA than what you can see within the list view. If the user wanted to drill down into some of these activities, there's clusters in here or they can go into the activity record itself and then find out more about that activity and some of the outputs. Let’s click over to another example. Here's just another example where we can see some other object types. I'm showing this example because of this subject which is a website and this publication and they don't actually exist within research data Australia, but we can navigate off to those publications and websites based on the link within the toolkit. The other thing I'd like to mention is this was sort of the first iteration. We are in the process of updating the graph already and that will come out in the next couple of weeks. So there is I guess a limitation at the moment within the current version of the graph in that there is no controls to maneuver the zoom in and out on the graph. So if the user doesn't have a scroll wheel they're really really stuck in terms of what they can do with the graph. This is sort of work in progress but you can see we've got some controls up here where we can zoom in and out of the graph. I don’t know if any of these nodes have lots and lots of connections but if we were say we can re center the graph if it was quite big to fit things within the view. We also have a limited help which opens the Research Data Australia help. So there will be a new tab in the RDA help which describes the different types of nodes that you can have and how that how to work with a graph and what's represented within the graph. So that will be coming out in probably about two weeks’ time. So keep an eye out for that. Gerry can you let me know if there are any questions. I’m finding it really hard on this computer.
  8. 8. Transcript: Online Services Release 27 & 28 – Technical Updates Page 8 of 16 Gerry Ryder: We do have one on that particular aspect of the graph from Nick who asked is there a way to find out more about a relationship on the graph than just the label of the relationship? Like a definition for it? I think that may have been answered a bit later in your presentation . Joel Benn: There’s not a lot yet in RDA in terms of the description of those relationships. We do obviously have pages on the ANDS website and for the RIF-CS documentation which describes those relationships. But that could be an enhancement we will get in the future to provide a bit more information within those pop outs about the sort of relationships. Okay so the next feature I'm going to go through is the ANDS ISGN service. So those who don't know what an IGSN is, it is an international geo sample number. They are globally unique system identifies for physical samples and specimens. They're citeable and they facilitate the linking between sample, related data, publications, and people. The global IGSN system is managed by the IGSN-ev organization, and technically it's underpinned by the handle system. So that they work, they're very similar I guess as DOIs in that you have some metadata that's associated with the identifier that describes the object. They're unique, they're persistent and they are resolvable. So, you can see underneath here I've got an example of how an IGSN looks. It’s pretty similar to a DOI. We have some prefix and then some of the suffix which is actually the identifier portion. I guess the unique proportion. You can obviously resolve them by using the handle service you can resolve them via So in terms of the IGSN service, this was a collaboration between AuScope ANDS, and CSIRO and it was implemented as part of the geosciences data and enhanced virtual laboratory project. It's based upon IGSN and software that was written by CSIRO and enhanced a little bit for ANDS needs. It's free to use and intended for use by the Australian earth science research community. It's accessed via the AuScope website and requires AFF login at this at this stage. Now when users go to mint an IGSN they're required to provide, or when you mint and IGSN,
  9. 9. Transcript: Online Services Release 27 & 28 – Technical Updates Page 9 of 16 you’re required to provide a minimum set of metadata and also a landing page. There obviously needs to be somewhere where that IGSN resolves to. When users mint through the ANDS IGSN service, the web interface I should say, the landing page is actually created for the user based on the metadata that they're into entering. So there's no need for them to host a landing page somewhere on their own systems, it's all done within that the ANDS service. If users are using the API service then they will need to host the page somewhere or talk to ANDS about possibly hosting that for them. At the moment it is pretty much restricted, or not restricted, but intended for use by the Geo science community, but ANDS is obviously interested in extending the service out for other physical sample types. I guess I should mention they're not the IGSN, the international IGSN is also looking at expanding things out for other sample types. So if there are any anyone on the line that's interested and they're in different domains and they can get in touch with ANDS and we can talk through a process for extending this service. The other thing to mention is that both CSIRO and Geoscience Australia also have IGSN services, so the ARDC / ANDS service is really focusing in on the research community, the academic research community which is not really covered by geosciences or Geoscience Australia or CSIRO. So just we'll go into the system for a second. As I said that the way to access is through the AuScope website, and so I'm just going into AuScope. So this is the access point within the AuScope website. It tells you a little bit about IGSN and some of the conditions that apply for using this service obviously has to be associated with Australian research, need to provide a minimum set of metadata etc etc. So to access the service there's a link down the bottom here which is “Click here to access the ANDS IGSN Service”. I'll just point out that there is also some documentation on the ANDS website. It's linked to from this page. Clicking in will navigate me off to the AAF where I can choose my institution. I mentioned before that the service is free anyone with an AAF can log-in like I just did you don't need to be affiliated with an
  10. 10. Transcript: Online Services Release 27 & 28 – Technical Updates Page 10 of 16 organization like our other services at this point in time. Anyone that logs in through the AuScope website kind of get an affiliation to AuScope and so anyone in the Geoscience community we sort of tracked through the AuScope login. Once you're in you basically land on sort of the page to mint an IGSN. I'll point out, just before we get into it, just at the top we have a link to some documentation so it's a little bit of help around the form. Now you can log out. You can list your resources that you've already minted in the past - you can sort of manage those who can go in and edit those or view them. And then a link then to obviously add another resource. Now in terms of the form there's a number of required fields which are highlighted in red and they're really around describing some of the core elements of a sample, the sample type, the material type and who's the curator for that sample. You can also set the visibility of the metadata. If I click on the drop down here and you can have metadata for this IGSN publicly visible. That will obviously resolve all within the ANDS service. You can have it private so if someone does try to resolve it they will actually get to a login page, and they'll have to have access before they can view that. You can also put your IGSNs under an embargo for a certain time period. Then once that embargo elapses that the metadata automatically becomes publicly visible. In terms of the other fields, so if I scroll down a little bit you can obviously describe location, pretty important for a lot of physical samples, and then you can go in to describe to the related resources. So, you might have other contributors that you want to describe and you can put in some relationship types and contributor types between these objects. Related resources, so you might want to really relate to publications and data or even other IGSNs. There might be a hierarchy between the IGSNs where you have a core sample that's then broken down into two individual samples that you sort of want to link together. There is another information tab which is excess metadata around the IGSN and so you can put in some classifications, the method that was
  11. 11. Transcript: Online Services Release 27 & 28 – Technical Updates Page 11 of 16 used, and also linked to a project and any other comments to do with the sample. Now open it then there are the link context help items for each of the fields. Sometimes they make sense and sometimes they're a little bit ambiguous. A lot of this is sort of the code that we took on board and we will enhance going forward. Once you’ve minted once, so I'll just mint a sample that’s publically visible. I’ll just fill out the basics here. So once I’ve registered an IGSN it takes a little while obviously because we're heading to the global system, to register with IGSN and then obviously into the handle system. You'll get a little pop out to say that your handle has been minted. You can find the resolution URL here. You can view the metadata, have another IGSN or just click ok which leads you on this page. You can basically use the same metadata to register another IIGSN with a few tweaks. I'll click on the view metadata and it will take me over to the view page - that's really big I’ll see if I can zoom out a little bit. This is basically the landing page that gets generated for your IGSNs within the web GUI. Whenever somebody resolves one of your public IGSNs this is the metadata page that that will land on. They obviously won't be logged into the system and won’t be able to, edit but this is the descriptive metadata they will find. If I put sort of locations in the map that would show up here. Now if you are the owner of the IGSN and you're logged in there is an edit button, or you can find in your list of resources. You can find the IGSN that you've minted in the past and view and edit those as you need. So, it might be that it was private and you now want to make it public, or vice versa or edit the metadata and republish that IGSN. That’s pretty much it on IGSN this time. We will be putting out a minor update which in the next few, in the next couple of weeks where we're going to make it a little bit easier for users to link to ORCID IDs and grant information related to samples. So that should be coming out in the next few weeks. Gerry Ryder: oel, we do have one question about the IGSN service. Nick’s asking is ANDS's posting IGSN metadata directly to the IGSN server service?
  12. 12. Transcript: Online Services Release 27 & 28 – Technical Updates Page 12 of 16 The reason he asks is that there’s only one handle server for IGSNs internationally and maybe there's a requirement for some redundancy? Joel Benn: Totally agree. We are sending the metadata directly to IGSN and I believe that there is an application going in for some funding for IGSN. I don't know the exact specifics but I'm if they get that funding I think there's going to be some work on the metadata kernel and making the system a little bit more robust. But to answer Nick’s question we are sending it directly to the IGSN service and they have a single handle prefix for that. So yeah there is a need for redundancy there. Gerry Ryder: Ok thanks Joel. Joel Benn: Ok so the next item is the RVA notifications. So, again this one was put into R 28. What I'll say before I get into the notification stuff we have done a huge amount of work for Research Vocabularies Australia in the last six to eight months. There is very little of it which is noticeable to the end-user, but basically the whole back end of RVA was rewritten in the last eight months. Some of the real benefits of that are things like the notification system that we can implement. There's also an API which is currently being documented and will be released in the next few weeks, so that will allow users to basically communicate with the RVA system machine-to-machine and publish vocabularies. It's also enabled us to put in lots of hooks for future enhancements that are sort of sitting in the backlog that people have asked for. We've done a huge amount of work and RVA so I things looking pretty good there. Now in terms of the notification system, these allow users to subscribe basically to vocabs or vocab owners. It allows then to stay to up to date with any of the changes for when new vocabularies are published. On the list here, users have the choice of subscribing to mailing lists for changes to a specific vocab or they can subscribe to any vocab from that owner, so that is new or changed vocabs. Or they can subscribe to everything in RVA, so whenever a vocab is changed or a new vocabulary is published they’ll get a digest email to notify them. At the moment emails are sent out weekly on
  13. 13. Transcript: Online Services Release 27 & 28 – Technical Updates Page 13 of 16 Wednesday mornings so when you subscribe you don't actually have a choice of frequency at this point of time they just adjust on a weekly basis on Wednesday mornings. If I go over into RVA, basically I'll just jump into any vocab. You can see the top here in the title bar there's now a subscribe label. Basically we can click that and it will open a subscription dialog box, and this is where you can basically subscribe and add your preferences to the mailing lists. We can see here that “I’d like to subscribe to a weekly email digest” and as I said there are those three choices at this stage where you can subscribe to the individual vocabulary, all the vocabularies from the owner ANDS, so ANDS is the vocabulary owner for this agrovoc, or newer change vocabularies from all owners within RVA. There's radio button group and you select one of those. There's also an option here to be notified of any service updates and features. This is when we do service software updates to RVA. You can take that box and that will add you to the mailing list for RVA features and updates and that will be sent out on as it as needed basis. So, whenever we do a software update to RVA we send out an email to all the users on that mailing list. That's pretty straightforward. You just put in an email address has to be valid. Obviously we do have a CAPTCHA in place. Most of the time the CAPTCHA will realize that you are an end user and you won't actually have to do the CAPTCHA clicking on images and then you can just click Subscribe. You'll see this I didn't need to do it and it will basically just say that you've successfully subscribed to that mailing list. So, on a weekly basis let me just … Gerry Ryder: While Joel's sorting out that little technical glitch we have had a question from Jackie asking about whether some journals are actually requiring IGSN samples, IGSNs for samples in order for articles to be published, which is becoming increasingly a requirement for research data. As far as I'm aware that's not yet a requirement but there are a number of journals that will enable the linking from a journal article to an IGSN and they're actively supporting and encouraging that. We do have a page on the ARDC website or the ANDS website that provides
  14. 14. Transcript: Online Services Release 27 & 28 – Technical Updates Page 14 of 16 some background about IGSN generally: what they are, how they can be used, how they can be cited and I'll pop that URL into the question pod so that people can follow up. It may be useful too if you're talking to colleagues or researchers about IGSN just to give a bit more background on what they are and how they can be used. Joel Benn: Sorry about that. Gerry Ryder: No worries, Joel over to you. Joel Benn: Sorry I had the address completely wrong. I should have put it in the slides would have been easier. So, I've just come into the test mail server just to show an example of sort of a weekly digest email that gets sent out. This is basically what users will receive. If they're subscribed to whatever mailing list, but no changes have happened within that week they won’t actually receive an email. So, it's only when things actually change that they impact the preferences that they have. Here's an example of a weekly digest and, basically the email’s broken into a number of sections. I've got one. This one you can see the section here which is to do with vocabularies that you're subscribed to directly. You can see here the name of the vocab and there is a link of off of that vocab directly within RVA. Then we can see a list of other changes that have taken place over the last week. It will tell you if the status of the vocabularies changed, it's not obviously here. Then it will tell you the descriptive metadata elements that were changed. We can see that the title was changed within the last week. Then it's broken down a little bit further into the version changes so it'll detailed some of the things that have changed within each of the versions. We can see that a new, another version here was added and it's set to current which means that the other two versions that were there would have been updated to superseded. There are some changes to NEI version 1 here. The version is no longer published by the linked data API so some of the flags within the CMS in RVA will change for this version. Then down the bottom of the email there is a button which allows you to obviously manage your subscription preferences. Because there's no requirement for users to log in when
  15. 15. Transcript: Online Services Release 27 & 28 – Technical Updates Page 15 of 16 they subscribe the only way that they can sort of get to manage their subscriptions is through their email. So, until you get an email you can't actually update your subscription preferences. You have to wait for the first email to come through. The other example I was showing before, the other section that's within the email is owner changes, so when you've subscribed to particular owners or all owners within RVA. It will break down the vocabularies under each of those owners. So I think in this one ANDS may have several, so here ANDS is the owner and we have the different vocabularies under the owner that have changed. We can see here this one's actually under quite a lot of changes within this of last reporting period. I'll scroll to the bottom and click manage subscriptions button. That will take you back to RVA. This is the manage subscriptions page where you can obviously unsubscribe from each of your preferred mailing lists. Again it's broken down into that sort of two categories so we have the vocabularies that you directly subscribe to and also the publishers that you subscribe to. Now I'll just point out that the two options down the bottom here we have All. This is that sort of special category where you want to be notified of everything but you can also specify that you're interested in in just vocab from this owner. So, the second or third option down here the AUTestingOrgRole is not really required at this stage because you're going to get everything anyway from the first option. We can obviously unsubscribe from that one and leave AUTesting there. It's pretty much as simple as that. Where you are subscribed to the service updates, so the software sort of updates notifications there is also another option that's displayed on this page which is enables you to unsubscribe from that mailing list as well. So, I think that's pretty much it. There is obviously some documentation around each of these pieces of functionality so I think we're going to send out the slides so that the links will be in there if you want to investigate a little bit further and read some of the documentation. That's pretty much everything. Are there any questions that I didn't answer or people have?
  16. 16. Transcript: Online Services Release 27 & 28 – Technical Updates Page 16 of 16 Gerry Ryder: Thank you Joel and thank you for bravely doing so many live demos. It does enhance things being able to see the actual functionality. We do have one question unanswered and it’s back on the IGSN service, from Les who asks: can the metadata be extracted from an IGSN over some kind of service? Joel Benn: Yes, absolutely so one of the requirements of running an IGSN services to have publicly accessible OAI-PMH endpoint. So, we have that running. Any of the metadata associated with public IGSNs, or once they've had embargo periods that have expired, will be available via that service. That service will also be used to feed into the IGSN portal which is run by CSIRO at this stage. They'll be harvesting from us as well and that will be discoverable through that service. Gerry Ryder: Well we don't have any more questions come in now so I think we'll give ourselves an early minute. Thank you again Joel for your time and for running us through what's been an awful lot of work being done by the dev team and thanks to all our participants for coming along today for your questions and we certainly hope to see you at another webinar again soon. END OF TRANSCRIPT