Release 13: Research Data Australia - A Closer look - 21 July 2014
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Benn, Joel
An overview of what's new in release 13 of Research data Australia. Joel Benn from ANDS took us through recent changes to Research Data Australia and ANDS Registry including improved functionality with: ORCID, EndNote, Thomson Reuters Data Citation Index, RDA Theme pages. The webinar will cover enhancements and changes to: Research Data Australia: - Implementation of an export to Endnote function from view pages - Enhancement to RDA's URLs to support Search Engine Optimisation - Implementation of an improved 'Contact Us' form in RDA
 For those who don't know me, I'm Joel Ben. I work in the development team as a business analyst. So I'm sort of the person in the middle between the business and the developers and writing some of the specs for the devs. And I also wear the sort of project management hat in each of the releases. So I get the excellent role of doing these webinars and people have to sit and listen to me dribble on. What I'll mention is that I'll do the slides in this view. If I put it in the full PowerPoint presentation for you, it actually switches off each time I flip between the system and PowerPoint. So what I'll be talking about today is what's in the release 13, which we put out last Thursday. So these are the high level things that I'll go through. So we've got the ANS harvests the rewrite. So that's a complete rewrite. The new shorter slugs for Research Data Australia. The release of some new theme pages, which are really exciting in Research Data Australia. Data Source Settings page rewrite. Exporting collections, collection references from Research Data Australia. So changes to the awkward import wizard enhancements. And a new RDA feedback form to replace the contact dust form. So the first one I'll go through is the harvester rewrite. So for this release, we have completely rewritten the harvester from the ground up in Python. The existing harvester had been around for quite some time. It was a bit troublesome for us to add functionality and to debug when issues actually happened. So the new harvester that we've written is much simpler and it's more robust. Meaning we can debug and we can extend it further in the future with a more simpler modular design. It provides support for additional harvest product calls other than OII and GET. So there have been data providers that can't necessarily provide us with an OII endpoint. And they don't necessarily want to use the HTTP GET method. So we have instances of C-CAN, which data.gov.au and data.gov, New South Wales, et cetera, the state versions of data.gov use C-CAN. So as part of this release, we did some testing with downloading data using the harvester from a C-CAN instance. And that basically downloads records in the JSON format. And then we use a crosswalk to transfer those into RISC as before ingesting them into the registry. So the previous edits of the harvester did have support for crosswalks. But with the rewrite, we've obviously made it simpler and we've added some functionality to support different protocols. Actually getting the data before we do the crosswalks. It's still not a sort of self-serve service. If you have some different protocols that you'd like to use or different formats that you'd like to transform into RISC-S, the best way to do that is to get in contact with services at ANTS and we'll walk you through a process of how we can get that in place. The next item is improved reporting for data source administrators and also for system admins. So when I'll get into the registry, I'll show you that there's some feedback now when harvests are occurring and when they finish and things like that for the DSAs. And for system admins, we now have a full dashboard, which the CIS admins can look at to identify whether there's any issues with harvests. So in the past, harvests have died and they'd sit there for a week or so before anyone would actually pick up that there was an issue. So hopefully the new dashboard will assist them in finding those quicker. So I've sort of gone over the schema agnostic and that's the transforms and the crosswalks. And I'll go into that in a little bit more detail. And the last one is existing schedule. Harvest will continue as normal. So the rewrite happened. We did a migration for all these scheduled harvests that were existing production into the new harvester and they should have been running already or scheduled to run in whatever time frame that they've got scheduled. So I'll just flick over into the system. So this is a data.gov instance as I was talking about before. This is actually a C-CAN implementation where we're getting the data from. For those that have used the dashboard before, it's mostly the same. You'll see in the top left-hand side now we actually have a harvest status section. And that gives you a little bit of information about the status of the harvester, whether it's running, whether it's scheduled, where it's completed, or if it's stopped by error. And it'll give you sort of the next run. So if it's a scheduled harvest, it'll tell you when the next run is going to occur and the frequency, et cetera. The batch number is really about the batches that we're getting from the C-CAN instance. So if you're a C-CAN implementer, you'll actually provide us records in different batches. And we just have the ID there so that we can do some debugging. Other than that, the dashboard's pretty much the same. When you actually run a harvest, there's a little bit more information that takes place. Please ignore the errors here. They are actually valid errors, which gets returned from the C-CAN instance when it can't provide us a package. But the harvester does continue, so I'll just scroll down and click on import from harvester. So you can see the status has changed the scheduled, the URI that we're wanting to get the data, and the last run has just been updated. Hopefully the harvest will kick off any second. There may be some already running. The new harvester has been rewritten in a way that we can handle multiple harvests at a time. And we've set that at the moment to a maximum of three harvests occurring, just to see how the system responds with that level of, I guess, processing of the harvests. So you can see here the harvest has started. You can see a percentage complete and a progress bar for the actual harvest. So this is something new, which is going to be really handy for the larger data sources. Who have thousands and thousands upon the record, and they're not sure where the harvest process is up to, because it can take up to an hour for some of the bigger data sources. A thing to note on the percentage complete, with C-CAN, obviously, when we ask for the data from C-CAN, it gives us a list of all the records that it's going to return, and we can obviously do a pretty neat percentage off the count of those records. If you're an OAI provider, we have to do some guesswork because we can't get a list, a count of the records, a count of the records from OAI. So what we actually do is we have a look at the numbers in the registry of the data source that exists, and then we use that to do the progress bar. So there's a little bit, it's a guess, basically, and sometimes progress go up, I'll actually get up to 100%, and there'll still be some records to import, but it should be close in most cases. So that's the dashboard. So I'll jump into the edit settings page for this data source. So the other types have remained the same, but in the harvester settings, you'll see some harvest methods that are new. So we had previously OAI and the get harvester. We now show CSW and C-CAN harvest methods. Now, again, these aren't really a self-serve thing, and we're doing some more work to make this screen a bit more usable or user-friendly, because it's not a self-service thing. We actually want to filter out the options that aren't applicable to data sources. So again, in the provider type, which sort of marries up to the harvest methods. So if you're not using OAI or get, and you're using another harvest method that doesn't provide Roussys, you're going to have a crosswalk or something implemented to transform into the Roussys format that we accept in the registry. So you can see in the provider type drop-down, there's a whole heap of other options here, and these are basically stipulating the format that the data's coming to the registry in. So there's some here for geo-networks. There's OAI DC, so that's double and core out of OAI provider. And behind these provider types is actually crosswalks that transform into Roussys, which we accept in the registry. So again, if you do have a harvest method or a provider type that is different to what we support natively, just get in contact with services at ANZ and we can walk you through setting up the crosswalk. Now, if you have one in mind already, I can tell you that crosswalks that we support at the moment in XSLT 2.0, sorry, not 2.0. So if you did want to start looking at developing a crosswalk, that would be the way to go in XSLT 1.0. So for this release, we sort of ran out of time to do the filtering on this screen, but in the future release, possibly 13.1 or R14, the screen will actually only show you options that are applicable to your data source. So you probably only see OAI and get and provide a type of Roussys available in the drop downs until you've actually with yourself and ANZ, configured a crosswalk and a new hubs method if required for your data source in the back end. Okay. Now, I did do a little diagram up, but I think if I go into too much detail here, it will confuse people. So what I'll just say is that the existing, the previous Harvester was its own software application. The new Harvester is written as a module of the registry. So it is, it's tightly, I wouldn't say tightly, but it is coupled with the registry. So if someone picked up a registry software, they could do some extensions to either change the Harvester to whatever they needed or take it out completely, but it is more coupled than it was previously. You'll see that I've sort of split the two. So we have what we call the Harvester process and the importer process. So the Harvester goes and gets the data, hands it to the importer, and the importer actually imports it into the registry. And you'll notice that I have crosswalks in both. And that's to do with crosswalks that happen before it gets the importer and crosswalks that happen within the importer. So crosswalks that happen within the Harvester side of things are when somebody says that they're going to provide in the data source settings page, they'll say that they're going to provide RIVCS, but their endpoint may actually provide OEIDC. And that crosswalk that sits on the, must sit on the Harvester side so that the importer is actually handling RIVCS. Hopefully that wasn't too confusing, but I won't go into any more detail because it will get quite confusing for people. But if you do need more information, you can either email yourself or services that are answered and try and explain it in a little bit more detail. So any questions, Cary? There's just one question. Somebody's still got problems logging into ANSIS and admin. Can we possibly take that offline? Yeah, we will take that offline and I'll chase that up with services. And if you haven't logged a ticket with services, just drop them an email and services at ans.org.au. And that will actually generate a service ticket for you and we can track it that way, but I'll also follow it up after this webinar. Okay, so the next one I'll briefly go into, the Theme Pages. So we have had the functionality in Research Data Australia for a while to basically publish Theme Pages, which showcase data to obviously do with the theme. But a couple of weeks prior to, or maybe even a month prior to R13, we actually released eight new Theme Pages, which was quite exciting for ANS. There was some communication that went out, but I'm not sure how much it was published. So I thought I'd just put it in the R13 webinar to draw everyone's attention to it. So it's a quick image of it, but in Research Data Australia, in the top navigation menu, there is themes if you haven't seen it before. You click on that and you'll get each of the icons and tiles for the themes that are available. I'm not in production in this one. Excellent. Maybe just production. Excellent. And Spotlight Showing Theme, which is very good. That's probably production now. Excellent. Every webinar, there's always one thing. Interesting. Apologies all. I probably should have tested before I walked in here, but I assumed production should be okay. Anyway, this is the test environment, but you will see these little tiles, and you can click on those and it'll give you some information about the theme. And then a list of records that are associated with them. If you have records that you believe belong in a theme or you want to suggest a new theme, again, just hit Services at ans.org.au. And we can either instruct you on how you can add your records to a theme, or we can look at generating a new theme based on some of your content. Apologies for that. If it comes up, I'll flip over and just show you quickly if that loads. I'm not sure why it's not loading. Okay, the next one, I'll go through is the new shorter slugs. A slug is basically the human readable part of a URL. This URL I have up on the screen, it'll be a best-in based chemical biology, et cetera, up until the very end. This is the part of the URL that we call a slug. As part of some search engine optimization, for this release, we've actually shortened the slugs for our research that are Australia-Urban. We've also changed the slugs for our research that are Australia URLs. Hopefully these make them a little bit more user-friendly, but the main benefit really was around search engine optimization for Google and being, et cetera. So the idea is that the large number of words in our existing slugs were causing us some issues in getting indexed by some of the larger search sites. So for this release, what we've done is we've taken the title of the record, and then we've actually taken the first three words and the last two words, which may seem a little bit interesting, but we did have a lot of records where the first 10 words were exactly the same, and then the last word was a species or a study or something. So we actually had to take the last words to try and make them as unique as possible. They don't have to be unique, but we tried to get them as unique as possible. So there may be the case where you come across multiple records in production where the slug part is exactly the same, and I know there are a couple, but then after the slash, we actually have the registry object ID on the end to make it unique. Now, this isn't the record key. This is the ID that we assign a record when it gets ingested into the registry for our internal handling with research data show here in the registry. So existing URLs, so if you have the old URL style or if you use the view PressureMarkkey equals style to result records, they will still result. We do all the redirects from the old URLs to the new slugs. So there shouldn't be any problems there. The other benefit of having the ID on the end is that you can actually resolve to that record without the slug itself. So I'll just complete this into the browser and show you what I mean. So this is the record with the new slug. So we have five words and then the ID on the end. But if you, for some reason, only knew the ID of the record and you didn't know the slug or somebody has mistyped the characters within the slug, but we have the ID correct on the end, we can actually resolve to that record just with the ID. And that will help us as well when there are incorrect URLs that we try and resolve in research data Australia, but the ID on the end is correct. We can actually do a lookup for the ID or vice versa, we can lookup the slug part of the URL and try and resolve to a record instead of giving somebody a 404 or a soft 404 error in research data Australia. Okay, so I think that was pretty much it for slugs. So I'll just, theme pages look like they have, that's good. They're going really well. Oh, here we go. You go up in the system. So this is the theme pages in production. They got nice pretty pictures. We have nine all up. And to get into them, you can just click one of the images and that will load into the theme. So you get a little bit of information about the theme and what it covers. The themes pages themselves can be configured by administrators and back end to be slightly different and what that is display. So they'll all have an image, but the content might be a little bit different. So for this one, we have some feature data collections, some data initiatives, excuse me, listed on the page. And they've also populated some related themes. Data services and the contributing organizations to this theme. So the contributing organizations will be based off the collections that belong in the theme. And you can see there's just a link here to every single collection which is in the theme. If I click on it, it will actually take me to a search and provide you access to all those collections that are within the theme. And then you can use obviously the facets and everything to filter down and try and find something that you're looking for. So they're going to be really, really handy going forward, I think, in a nice addition to Research Data Australia. Okay. Okay, so this is just a brief one. The data source settings page, if you had some experience for the data source settings page in the past, every now and then when you logged in and went to the data source settings page, you would get a gray page or a blank gray page or sometimes you'd actually get an error. These were existing bugs in the existing framework, which were a little bit tricky to fix without changing the whole framework. So as part of this release, we have rewritten the whole data source settings page. It is much the same. There's really not a lot that has changed besides those Harvard settings that I showed you before. The switches that we used to have on and off were different pieces of functionality and now checkboxes. And we've also added an option for providing records to the Thompson Reuters data citation index. Now this option is not available to data sources, but it's available in the data source settings page. And it's not available to data source administrators because there has to be sort of an interaction and a process that takes place before data sources can provide their records to the data citation index. So that's sort of a consultation between the data source administrator and ANS. And once all that's happened and taken place and we're happy that the records are good to go to Thompson Reuters, we can actually tick this box and they'll be exposed for Thompson Reuters to harvest from us and put into the data source at the data citation index. But other than that, you really shouldn't notice any changes. All the same settings are on each of the three tabs that they were before. So there shouldn't be any dramas there if you find anything less. It should be okay. Okay, the next one. Exporting collection references from Research Data Australia. So we have supported exports from Research Data Australia for quite some time. I think it was 2009 when we first implemented coins, which is content objects in spans. And it was a way for us to invisibly hide content in a Research Data Australia page that then reference managers would be able to pick up that it existed and export information from Research Data Australia about a collection and so on. The issue with... Well, there's a couple of issues. The issues with the coins was that... So Tero and Mendeley, which were the main sort of reference managers that we were looking at supporting, they didn't have a concept of a data set. So collections or any other pages in Research Data Australia would actually get exported and still do get exported in a less than optimal way. And they don't get exported as a data set. Now, we used to... Well, we did support EndNote as well. But somewhere along the line, EndNote dropped their support for coins and moved towards their own sort of functionality on importing and exporting information. Now, for this release, we've looked at supporting EndNote as their sort of the primary reference manager, because it supports a reference type of data set, which enables us to export collections in quite a nice and richly described format. So what I'll go through is exporting a collection or any number of collections from Research Data Australia, and they get exported in the Research Information Systems format, which is a format that's not just supported by EndNote, so Tero, Mendeley, support at RefWorks also support it, and I think quite a number of support with the risk format. The issue, again, with those other reference management tools is they don't have the concept of a data set. None that I've come across yet have the concept of a data set except for EndNote. So primarily, we are sort of aiming at support for EndNote, but by all means, you can export into... So Tero or Mendeley with the rest download. And I'll show you some images in a second of what that looks like. The last thing to note is that in the data set type that EndNote support, they actually have a number of custom fields that we can use to store information that doesn't fit within the fields that EndNote have generated for the data set type. So we've actually used one of those fields to store the rights information about a collection, so that's obviously quite an important thing to go along with the collection. And there's a little bit of customization you can do to your EndNote so that the rights label appears against your exports from Research Data Australia. And I can just show you where you can do that later. So I might just flick over and just show you the images first. So this is exporting coins into Tero from a collection in Research Data Australia. And what you'll see is that it's exported as a web page, so it doesn't export as a data set. It does get a title. It has got the authors, which is good in the abstract. It lacks a lot of other information, which is important for a data set. And this is sort of a split screen. I've just pasted them together and on the tab, it has picked up the subjects that go along with the collection, which is not too bad. The next image is the RIF export to EndNote. So this is the Tero supporting RIS. And you can see it's a bit hard to see on the screen, which I'll zoom in quickly. That's going to see over there. Oh, no. A bit hard to see, but wrong one. There is a bit more information that is being pulled out from the RIS export. You can see this time it's exported as a document instead of a web page. We again get the authors. We get a translator, ARC, the Australian Research Council, which is actually the funder of the collection. So the exports, obviously, again, not ideal using RIS to Zetero. But we do get a little bit more information. So we get some notes about the collection. So that's from the description of type notes and I think related information of type notes as well. So if there's any stuff in there that will get captured. And again, the subjects get pulled out. So I think it's off switch over into the browser again. All I need to do is just do a search for a collection in RIS Australia or browse and find a collection. So I have a couple here that I was using for tests. So please excuse the test data that is in it. What you'll see now in research data Australia in the right-hand side column. So this is the right-hand side column over in the axis down the very bottom. We actually have an export button which allows us to export. So if I just click that, we get two options. Obviously, NNote has two formats. So they've got a desktop application and they also have NNote online, which is somewhat limited but is also really handy. So we have the two options because they export exactly the same information, but in a different way. So I'll use the export to NNote option to start with. So I've clicked it. My NNote library was already open. If it's not, it'll actually open it if you use Firefox. If you're using Chrome, etc., it'll actually download the file and then you have to click on it and it will open NNote for you. What you can see is that I have just imported this reference. You can see at the top here we have the type of data set, which is much better. We have the investigators, which obviously we can have multiple investigators if they are applicable to a collection. We have the year of the collection, the title, distributor, data collection, etc. We get obviously the correct funding agency. So ARC is now sitting as a funding agency, which is quite important. We get some spatial information, temporal information. The rights, as I said before, if you haven't configured NNote to display rights, this will display as custom five. I'll show you quickly after this where you can actually change that reference to display as rights, which is going to be helpful for some people. The other key words, the abstract, again, notes, URL to the record, which we didn't really get before in the other exports, and the date of access. So the date it was actually extracted into NNote. Okay, so why is Australian Research Council not sure? I'd have to look at the way it's actually listed in research data Australia. Good question. It may be an NNote thing or it could be the way we're exporting it. I'll drop that down and have a look at it if this isn't going to load, and we'll take that off the line. Yeah, not sure. I'll have a look at that one offline and keep moving. Hopefully it's just the NNote support for it. Okay, so where to go for a little bit of help? I'll just go back to the collection page down again with the button. I should have said that, sorry, just while I was on that page, the export button only shows for collections, so we're only supporting the export of datasets at this stage. So that's why it's not displaying on that page, which is an activity. Sorry, quick side note. Just next to the export button, there is a question mark to grab help for the export. Click on that. There is some online help. A little bit of information about why we're sort of supporting NNote, and again, it's just to do with the reference type support. Step by step of how to export, pretty straightforward. We also have how to configure your computer to open RISC files. So if you haven't used NNote before and you've just installed it, your computer probably won't associate the dot RISC extension on files with NNote to open directly or to open via a click. So there's just some instructions on how you can do that in both a Windows and a Mac. And then the last set of instructions is how you can actually configure that custom file field to display as rights in your NNote instance, which is really straightforward. It may be something you want to do if you use NNote desktop a lot. NNote online, you can't actually configure a lot and you can't configure the preferences on these fields. So it'll just display as custom file, but hopefully you will understand when you look at the information in that field that it is rights information. Okay, so that's pretty much it for exports. I think that's going to be really handy. There has been people asking to be able to export from Research to Australia. I know that another piece of functionality we're looking at is being able to export multiple records that are listed in our search results because there are obviously people doing does say reviews and things like that. So we will be looking at that in the future if that is something that's been to your mind about a request. Okay, so the Orca Import Wizard enhancements, if you've had experience with the Orca Import Wizard, the first interface that we did was sort of a quick sort of get something up effort. It worked and people are using it, but there are a few sort of usability issues that we wanted to address in the new version. So really the emphasis that we've put on the new version is around reviewing the collections that you got to import into your Orca profile. So there have been cases where people have come to the old import wizard, excuse me, and they have clicked import all without actually reviewing if they were actually associated or had some input into the collections. So what we've done is we've removed the import all. We've provided check boxes so that people are actually checking and looking at what they're actually going to import before just saying yep, all good. We've put in a little mini review and import workflow and some guidelines on the page just to, they're not long, they're just a couple of dot points to restrict people on sort of what they should be doing and when they should be importing clutches to their profile. The other little change that we did, they already imported data sets section. Previously if you imported records into Orca and then subsequently remove them from your Orca profile, we never actually updated the list of imported data sets at our end. So for this release, if you remove something from Orca, we actually remove it from our end as well so that they're synced and consistent. The last one there, citation metadata added to the search index. So previously if you're, there were a few collections where somebody's name was listed in the citation information or citation metadata of a collection but they weren't listed in a party or something like that but they weren't being returned in the Orca search. So we've actually indexed citation metadata so if your name does exist in the citation, we'll pull out those collections for you to import. So if you haven't used the import wizard, I've just logged into my Orca profile in production. Down the bottom here where this works, you can click link works and there's a number of options of where you can go and get works that you put into your Orca profile. We're obviously at the top probably because we start with a hang on a day and you can just click that and it'll fire you off into the Orca import wizard. You obviously have to give authorization to allow us to push information to your Orca profile. So just click authorize and it should log us into the import wizard. So the interface is pretty similar. I probably should have used test. In the suggested datasets, we will list any collections that we find that are directly related to your Orca ID in Research Data Australia or related to a party which has your surname. So there may be some false positives in that list but hopefully we get most of them right and you don't obviously have to import them all. It's best to review them beforehand. There's also the search that you can put under. So if I want to just find something. Just done a search for biology and again there are checkboxes against the records. I apologize I should have done this in tests where I had some suggested datasets and what happens is you have checkboxes in both the suggested datasets region and also in the search and you can actually select across. So I can select these two in the search for import and I can also select whatever is in the suggested datasets and then click the import button. So the import button only becomes active once you've actually got something selected. So I've got these two selected and it will tell me I've got two works to import. These are the guidelines I was talking about very brief but will hopefully eliminate some datasets from being imported to people's profiles that aren't relevant. And the section down here is the datasets already imported. So I want to say import these works from my production profile. That should get updated. So I click the button and I'll get this little mini workflow. It tells me how many I'm about to import. It tells me just to review them to make sure they're appropriate before continuing. The little minus icons next to which these allows me to remove items from import before I click the import button. Once I click import, it will go off and it will import them into give me a little congratulations. It should be imported into my Orca profile. There's a little note here just to review and set the appropriate visibility settings. So not everything that gets published to your Orca profile will be public and you should obviously decide what needs to be private and public in your Orca profile. Let me just refresh this page. None of the works it should have. This has got nothing to do obviously with my profile but I'll just use it as a test. And you can set the visibility here in your Orca profile and I can also remove it which I'll do in a second. So if I just refresh this page. There we go. You'll see against the one that I've already imported there's a little imported label. And you'll also see all the imported datasets over here in the right. Now if I go and delete this from Orca and say no it's not actually do with me. That should go. And then if I refresh page it should drop off. My datasets are already imported as well. So that's pretty much all the changes we did for the Orca interface and hopefully it's a little bit more user friendly. And we'll prevent some imports of collections. Okay. No questions? Okay. I guess the other thing tonight is we do have a video for the Orca. How do we import works into your Orca profile as well as a help. The information is still accurate. We'll still assist you in importing collections into your Orca profile but we are looking to update that in the near future to the new interface. But really it's pretty straightforward and you shouldn't have too many issues with importing. Okay. Okay the new RDA feedback form. So we had some feedback from a number of people and for a long time we've sort of known that the Contact Us page on RDA wasn't ideal. So we had some feedback where people couldn't actually find the Contact Us page and they had to go through other means to find it. So for this release we have updated the Contact Us form to a feedback form. It's available via the left hand side of Resource Data Australia on every single page and it's quite prominent so people shouldn't have a problem finding it. The new feedback form provides users with some predefined request types on what they can actually ask for or suggesting. And it's embedded in Resource Data Australia but it's actually a Dura form. So it's linked directly to Dura. It will create service test tickets automatically and then we can track your requests and things and push them through the appropriate workflows. And obviously we're hoping for a bit more user engagement in Resource Data Australia from the community now that they can actually contact us a lot easier. So again I'll just flick over. This is test, that's fine. So you can clearly see that there is a feedback tab on the left hand side. We've put it in the white section of the page, pretty much on every page so that it stands out. And no matter where I go this should be available to provide feedback. If I click the tab it opens a form for me to fill out. You'll note that there is a none option at the top and this is something that we will remove eventually but there was some issues with taking down Dura to actually remove it. So for this release we've just left it in but we've defaulted obviously to request helping the option. You just need to fill out a subject and a description and provide your name and email. And one of the good things about this feedback form is that you can actually upload a screenshot. If you've come across a bug or you've found it's something that you'd like changed you can actually annotate a diagram or something and actually upload it to your Dura issue and that will assist services. And whoever is looking at that issue to respond quickly and appropriately. So the issue types request help report an issue, suggest new functionality in Resource Data Australia. So we've got some good ideas, file means, and recommended request data. We've looked, been looking for some data in Resource Data Australia and you haven't found it. You can suggest some data that we may want to look at getting into Resource Data Australia and any general feedback you want to provide to ends. So hopefully that will be really useful for our end users. Time on 43. Okay. Come on. Okay. So that's pretty much everything. If you need more information, obviously the online services news page has been updated and you can also contact services at ends. So I've got the online services news page. I think it's open. So news and events on the left hand side of the ends with page, homepage and then online services news. And then there's some release notes for our 13 models in it, any non technical help that we can provide for our 13. We've also recently updated the online services homepage and we're in the process of updating the information within the individual sections of the online services. So hopefully that will help people find what they're looking for in a quicker fashion. And for those that haven't come across it, there's also the ends developer toolbox. So if anyone's out there that would like to reuse parts of ends code or even the whole registry, we have that available. And that's just the research data for the ends that all they use, the RDA URL slash developers. And there's also a link on Research Data Australia down the very bottom. Where am I? So there is a developers link down the bottom, which will also link you off to the developers toolbox. The last thing is just that you may have noticed that there was a longer downtime or longer unavailable for publishing in this release. So we went read only mode on the Wednesday, close of business five o'clock and had the release on the Thursday morning. And just to let you know the reason for that was we were doing some upgrades to the software on our production box as well. And we just needed to make sure that there was no records coming in while we were doing some work on the database. But other than that, that's pretty much it for Arthur. Thanks all. Bye. Cheers.
 For those who don't know me, I'm Joel Ben.  I work in the development team as a business analyst.  So I'm sort of the person in the middle between the business  and the developers and writing some of the specs for the devs.  And I also wear the sort of project management hat  in each of the releases.  So I get the excellent role of doing these webinars  and people have to sit and listen to me dribble on.  What I'll mention is that I'll do the slides in this view.  If I put it in the full PowerPoint presentation for you,  it actually switches off each time I flip between the system  and PowerPoint.  So what I'll be talking about today  is what's in the release 13, which we put out last Thursday.  So these are the high level things that I'll go through.  So we've got the ANS harvests the rewrite.  So that's a complete rewrite.  The new shorter slugs for Research Data Australia.  The release of some new theme pages,  which are really exciting in Research Data Australia.  Data Source Settings page rewrite.  Exporting collections, collection references  from Research Data Australia.  So changes to the awkward import wizard enhancements.  And a new RDA feedback form to replace the contact dust form.  So the first one I'll go through is the harvester rewrite.  So for this release, we have completely rewritten  the harvester from the ground up in Python.  The existing harvester had been around for quite some time.  It was a bit troublesome for us to add functionality  and to debug when issues actually happened.  So the new harvester that we've written is much simpler  and it's more robust.  Meaning we can debug and we can extend it further  in the future with a more simpler modular design.  It provides support for additional harvest  product calls other than OII and GET.  So there have been data providers that can't necessarily  provide us with an OII endpoint.  And they don't necessarily want to use the HTTP GET method.  So we have instances of C-CAN, which data.gov.au  and data.gov, New South Wales, et cetera, the state versions  of data.gov use C-CAN.  So as part of this release, we did some testing  with downloading data using the harvester  from a C-CAN instance.  And that basically downloads records in the JSON format.  And then we use a crosswalk to transfer those into RISC  as before ingesting them into the registry.  So the previous edits of the harvester  did have support for crosswalks.  But with the rewrite, we've obviously  made it simpler and we've added some functionality  to support different protocols.  Actually getting the data before we do the crosswalks.  It's still not a sort of self-serve service.  If you have some different protocols  that you'd like to use or different formats  that you'd like to transform into RISC-S,  the best way to do that is to get in contact with services  at ANTS and we'll walk you through a process of how  we can get that in place.  The next item is improved reporting  for data source administrators and also for system admins.  So when I'll get into the registry,  I'll show you that there's some feedback now when  harvests are occurring and when they finish and things  like that for the DSAs.  And for system admins, we now have a full dashboard,  which the CIS admins can look at to identify  whether there's any issues with harvests.  So in the past, harvests have died  and they'd sit there for a week or so before anyone would  actually pick up that there was an issue.  So hopefully the new dashboard will assist them  in finding those quicker.  So I've sort of gone over the schema agnostic  and that's the transforms and the crosswalks.  And I'll go into that in a little bit more detail.  And the last one is existing schedule.  Harvest will continue as normal.  So the rewrite happened.  We did a migration for all these scheduled harvests  that were existing production into the new harvester  and they should have been running already  or scheduled to run in whatever time frame  that they've got scheduled.  So I'll just flick over into the system.  So this is a data.gov instance as I was talking about before.  This is actually a C-CAN implementation  where we're getting the data from.  For those that have used the dashboard before,  it's mostly the same.  You'll see in the top left-hand side now  we actually have a harvest status section.  And that gives you a little bit of information  about the status of the harvester,  whether it's running, whether it's scheduled,  where it's completed, or if it's stopped by error.  And it'll give you sort of the next run.  So if it's a scheduled harvest,  it'll tell you when the next run is going to occur  and the frequency, et cetera.  The batch number is really about the batches  that we're getting from the C-CAN instance.  So if you're a C-CAN implementer,  you'll actually provide us records in different batches.  And we just have the ID there  so that we can do some debugging.  Other than that, the dashboard's pretty much the same.  When you actually run a harvest,  there's a little bit more information that takes place.  Please ignore the errors here.  They are actually valid errors,  which gets returned from the C-CAN instance  when it can't provide us a package.  But the harvester does continue,  so I'll just scroll down and click on import from harvester.  So you can see the status has changed the scheduled,  the URI that we're wanting to get the data,  and the last run has just been updated.  Hopefully the harvest will kick off any second.  There may be some already running.  The new harvester has been rewritten in a way  that we can handle multiple harvests at a time.  And we've set that at the moment  to a maximum of three harvests occurring,  just to see how the system responds with that level of,  I guess, processing of the harvests.  So you can see here the harvest has started.  You can see a percentage complete  and a progress bar for the actual harvest.  So this is something new,  which is going to be really handy for the larger data sources.  Who have thousands and thousands upon the record,  and they're not sure where the harvest process is up to,  because it can take up to an hour  for some of the bigger data sources.  A thing to note on the percentage complete,  with C-CAN, obviously,  when we ask for the data from C-CAN,  it gives us a list of all the records that it's going to return,  and we can obviously do a pretty neat percentage  off the count of those records.  If you're an OAI provider, we have to do some guesswork  because we can't get a list,  a count of the records,  a count of the records from OAI.  So what we actually do is we have a look at the numbers  in the registry of the data source that exists,  and then we use that to do the progress bar.  So there's a little bit, it's a guess, basically,  and sometimes progress go up,  I'll actually get up to 100%,  and there'll still be some records to import,  but it should be close in most cases.  So that's the dashboard.  So I'll jump into the edit settings page for this data source.  So the other types have remained the same,  but in the harvester settings,  you'll see some harvest methods that are new.  So we had previously OAI and the get harvester.  We now show CSW and C-CAN harvest methods.  Now, again, these aren't really a self-serve thing,  and we're doing some more work  to make this screen a bit more usable or user-friendly,  because it's not a self-service thing.  We actually want to filter out the options  that aren't applicable to data sources.  So again, in the provider type,  which sort of marries up to the harvest methods.  So if you're not using OAI or get,  and you're using another harvest method  that doesn't provide Roussys,  you're going to have a crosswalk  or something implemented to transform into the Roussys format  that we accept in the registry.  So you can see in the provider type drop-down,  there's a whole heap of other options here,  and these are basically stipulating the format  that the data's coming to the registry in.  So there's some here for geo-networks.  There's OAI DC, so that's double and core out of OAI provider.  And behind these provider types is actually crosswalks  that transform into Roussys,  which we accept in the registry.  So again, if you do have a harvest method  or a provider type that is different  to what we support natively,  just get in contact with services at ANZ  and we can walk you through setting up the crosswalk.  Now, if you have one in mind already,  I can tell you that crosswalks that we support at the moment  in XSLT 2.0, sorry, not 2.0.  So if you did want to start looking at developing a crosswalk,  that would be the way to go in XSLT 1.0.  So for this release,  we sort of ran out of time to do the filtering on this screen,  but in the future release, possibly 13.1 or R14,  the screen will actually only show you options  that are applicable to your data source.  So you probably only see OAI and get  and provide a type of Roussys available in the drop downs  until you've actually with yourself and ANZ,  configured a crosswalk and a new hubs method  if required for your data source in the back end.  Okay.  Now, I did do a little diagram up,  but I think if I go into too much detail here,  it will confuse people.  So what I'll just say is that the existing,  the previous Harvester was its own software application.  The new Harvester is written as a module of the registry.  So it is, it's tightly, I wouldn't say tightly,  but it is coupled with the registry.  So if someone picked up a registry software,  they could do some extensions to either change the Harvester  to whatever they needed or take it out completely,  but it is more coupled than it was previously.  You'll see that I've sort of split the two.  So we have what we call the Harvester process  and the importer process.  So the Harvester goes and gets the data,  hands it to the importer,  and the importer actually imports it into the registry.  And you'll notice that I have crosswalks in both.  And that's to do with crosswalks that happen  before it gets the importer and crosswalks that happen  within the importer.  So crosswalks that happen within the Harvester side of things  are when somebody says that they're going to provide  in the data source settings page,  they'll say that they're going to provide RIVCS,  but their endpoint may actually provide OEIDC.  And that crosswalk that sits on the,  must sit on the Harvester side  so that the importer is actually handling RIVCS.  Hopefully that wasn't too confusing,  but I won't go into any more detail  because it will get quite confusing for people.  But if you do need more information,  you can either email yourself or services that are answered  and try and explain it in a little bit more detail.  So any questions, Cary?  There's just one question.  Somebody's still got problems logging into ANSIS and admin.  Can we possibly take that offline?  Yeah, we will take that offline  and I'll chase that up with services.  And if you haven't logged a ticket with services,  just drop them an email and services at ans.org.au.  And that will actually generate a service ticket for you  and we can track it that way,  but I'll also follow it up after this webinar.  Okay, so the next one I'll briefly go into,  the Theme Pages.  So we have had the functionality in Research Data Australia  for a while to basically publish Theme Pages,  which showcase data to obviously do with the theme.  But a couple of weeks prior to,  or maybe even a month prior to R13,  we actually released eight new Theme Pages,  which was quite exciting for ANS.  There was some communication that went out,  but I'm not sure how much it was published.  So I thought I'd just put it in the R13 webinar  to draw everyone's attention to it.  So it's a quick image of it,  but in Research Data Australia,  in the top navigation menu,  there is themes if you haven't seen it before.  You click on that and you'll get each of the icons  and tiles for the themes that are available.  I'm not in production in this one.  Excellent.  Maybe just production.  Excellent.  And Spotlight Showing Theme, which is very good.  That's probably production now.  Excellent.  Every webinar, there's always one thing.  Interesting.  Apologies all.  I probably should have tested before I walked in here,  but I assumed production should be okay.  Anyway, this is the test environment,  but you will see these little tiles,  and you can click on those  and it'll give you some information about the theme.  And then a list of records that are associated with them.  If you have records that you believe belong in a theme  or you want to suggest a new theme,  again, just hit Services at ans.org.au.  And we can either instruct you  on how you can add your records to a theme,  or we can look at generating a new theme  based on some of your content.  Apologies for that.  If it comes up, I'll flip over and just show you quickly  if that loads.  I'm not sure why it's not loading.  Okay, the next one, I'll go through  is the new shorter slugs.  A slug is basically the human readable part of a URL.  This URL I have up on the screen,  it'll be a best-in based chemical biology, et cetera,  up until the very end.  This is the part of the URL that we call a slug.  As part of some search engine optimization,  for this release, we've actually shortened the slugs  for our research that are Australia-Urban.  We've also changed the slugs  for our research that are Australia URLs.  Hopefully these make them a little bit more user-friendly,  but the main benefit really was around  search engine optimization for Google and being, et cetera.  So the idea is that the large number of words  in our existing slugs were causing us some issues  in getting indexed by some of the larger search sites.  So for this release, what we've done  is we've taken the title of the record,  and then we've actually taken the first three words  and the last two words,  which may seem a little bit interesting,  but we did have a lot of records where the first 10 words  were exactly the same, and then the last word was a species  or a study or something.  So we actually had to take the last words  to try and make them as unique as possible.  They don't have to be unique,  but we tried to get them as unique as possible.  So there may be the case where you come across  multiple records in production  where the slug part is exactly the same,  and I know there are a couple,  but then after the slash,  we actually have the registry object ID  on the end to make it unique.  Now, this isn't the record key.  This is the ID that we assign a record  when it gets ingested into the registry  for our internal handling  with research data show here in the registry.  So existing URLs,  so if you have the old URL style  or if you use the view  PressureMarkkey equals style to result records,  they will still result.  We do all the redirects from the old URLs to the new slugs.  So there shouldn't be any problems there.  The other benefit of having the ID on the end  is that you can actually resolve to that record  without the slug itself.  So I'll just complete this into the browser  and show you what I mean.  So this is the record with the new slug.  So we have five words and then the ID on the end.  But if you, for some reason,  only knew the ID of the record  and you didn't know the slug  or somebody has mistyped the characters within the slug,  but we have the ID correct on the end,  we can actually resolve to that record just with the ID.  And that will help us as well  when there are incorrect URLs  that we try and resolve in research data Australia,  but the ID on the end is correct.  We can actually do a lookup for the ID  or vice versa, we can lookup the slug part of the URL  and try and resolve to a record  instead of giving somebody a 404  or a soft 404 error in research data Australia.  Okay, so I think that was pretty much it for slugs.  So I'll just, theme pages look like they have,  that's good.  They're going really well.  Oh, here we go.  You go up in the system.  So this is the theme pages in production.  They got nice pretty pictures.  We have nine all up.  And to get into them,  you can just click one of the images  and that will load into the theme.  So you get a little bit of information  about the theme and what it covers.  The themes pages themselves  can be configured by administrators  and back end to be slightly different  and what that is display.  So they'll all have an image,  but the content might be a little bit different.  So for this one, we have some feature data collections,  some data initiatives, excuse me,  listed on the page.  And they've also populated some related themes.  Data services and the contributing organizations  to this theme.  So the contributing organizations  will be based off the collections that belong in the theme.  And you can see there's just a link here  to every single collection which is in the theme.  If I click on it, it will actually take me to a search  and provide you access to all those collections  that are within the theme.  And then you can use obviously the facets  and everything to filter down  and try and find something that you're looking for.  So they're going to be really, really handy going forward,  I think, in a nice addition to Research Data Australia.  Okay.  Okay, so this is just a brief one.  The data source settings page,  if you had some experience  for the data source settings page in the past,  every now and then when you logged in  and went to the data source settings page,  you would get a gray page or a blank gray page  or sometimes you'd actually get an error.  These were existing bugs in the existing framework,  which were a little bit tricky to fix  without changing the whole framework.  So as part of this release,  we have rewritten the whole data source settings page.  It is much the same.  There's really not a lot that has changed  besides those Harvard settings that I showed you before.  The switches that we used to have on and off  were different pieces of functionality and now checkboxes.  And we've also added an option  for providing records to the Thompson Reuters data citation index.  Now this option is not available to data sources,  but it's available in the data source settings page.  And it's not available to data source administrators  because there has to be sort of an interaction  and a process that takes place before  data sources can provide their records  to the data citation index.  So that's sort of a consultation between the data source administrator  and ANS.  And once all that's happened and taken place  and we're happy that the records are good to go to Thompson Reuters,  we can actually tick this box and they'll be exposed  for Thompson Reuters to harvest from us  and put into the data source at the data citation index.  But other than that, you really shouldn't notice any changes.  All the same settings are on each of the three tabs  that they were before.  So there shouldn't be any dramas there  if you find anything less.  It should be okay.  Okay, the next one.  Exporting collection references from Research Data Australia.  So we have supported exports  from Research Data Australia for quite some time.  I think it was 2009 when we first implemented coins,  which is content objects in spans.  And it was a way for us to  invisibly hide content in a Research Data Australia page  that then reference managers would be able to pick up  that it existed and export information from Research Data Australia  about a collection and so on.  The issue with...  Well, there's a couple of issues.  The issues with the coins was that...  So Tero and Mendeley,  which were the main sort of reference managers  that we were looking at supporting,  they didn't have a concept of a data set.  So collections or any other pages in Research Data Australia  would actually get exported and still do get exported  in a less than optimal way.  And they don't get exported as a data set.  Now, we used to...  Well, we did support EndNote as well.  But somewhere along the line,  EndNote dropped their support for coins  and moved towards their own sort of functionality  on importing and exporting information.  Now, for this release,  we've looked at supporting EndNote  as their sort of the primary reference manager,  because it supports a reference type of data set,  which enables us to export collections in quite a nice  and richly described format.  So what I'll go through is exporting a collection  or any number of collections from Research Data Australia,  and they get exported in the Research Information Systems format,  which is a format that's not just supported by EndNote,  so Tero, Mendeley, support at RefWorks also support it,  and I think quite a number of support with the risk format.  The issue, again, with those other reference management tools  is they don't have the concept of a data set.  None that I've come across yet have the concept of a data set  except for EndNote.  So primarily, we are sort of aiming at support for EndNote,  but by all means, you can export into...  So Tero or Mendeley with the rest download.  And I'll show you some images in a second of what that looks like.  The last thing to note is that in the data set type that EndNote support,  they actually have a number of custom fields that we can use  to store information that doesn't fit within the fields that EndNote  have generated for the data set type.  So we've actually used one of those fields to store the rights  information about a collection,  so that's obviously quite an important thing to go along with the collection.  And there's a little bit of customization you can do to your EndNote  so that the rights label appears against your exports from Research Data Australia.  And I can just show you where you can do that later.  So I might just flick over and just show you the images first.  So this is exporting coins into Tero from a collection in Research Data Australia.  And what you'll see is that it's exported as a web page,  so it doesn't export as a data set.  It does get a title.  It has got the authors, which is good in the abstract.  It lacks a lot of other information, which is important for a data set.  And this is sort of a split screen.  I've just pasted them together and on the tab, it has picked up the subjects  that go along with the collection, which is not too bad.  The next image is the RIF export to EndNote.  So this is the Tero supporting RIS.  And you can see it's a bit hard to see on the screen, which I'll zoom in quickly.  That's going to see over there.  Oh, no.  A bit hard to see, but wrong one.  There is a bit more information that is being pulled out from the RIS export.  You can see this time it's exported as a document instead of a web page.  We again get the authors.  We get a translator, ARC, the Australian Research Council,  which is actually the funder of the collection.  So the exports, obviously, again, not ideal using RIS to Zetero.  But we do get a little bit more information.  So we get some notes about the collection.  So that's from the description of type notes and I think related information  of type notes as well.  So if there's any stuff in there that will get captured.  And again, the subjects get pulled out.  So I think it's off switch over into the browser again.  All I need to do is just do a search for a collection in RIS Australia  or browse and find a collection.  So I have a couple here that I was using for tests.  So please excuse the test data that is in it.  What you'll see now in research data Australia in the right-hand side column.  So this is the right-hand side column over in the axis down the very bottom.  We actually have an export button which allows us to export.  So if I just click that, we get two options.  Obviously, NNote has two formats.  So they've got a desktop application and they also have NNote online,  which is somewhat limited but is also really handy.  So we have the two options because they export exactly the same information,  but in a different way.  So I'll use the export to NNote option to start with.  So I've clicked it.  My NNote library was already open.  If it's not, it'll actually open it if you use Firefox.  If you're using Chrome, etc., it'll actually download the file  and then you have to click on it and it will open NNote for you.  What you can see is that I have just imported this reference.  You can see at the top here we have the type of data set, which is much better.  We have the investigators, which obviously we can have multiple investigators  if they are applicable to a collection.  We have the year of the collection, the title, distributor, data collection, etc.  We get obviously the correct funding agency.  So ARC is now sitting as a funding agency, which is quite important.  We get some spatial information, temporal information.  The rights, as I said before, if you haven't configured NNote to display rights,  this will display as custom five.  I'll show you quickly after this where you can actually change that reference  to display as rights, which is going to be helpful for some people.  The other key words, the abstract, again, notes, URL to the record,  which we didn't really get before in the other exports, and the date of access.  So the date it was actually extracted into NNote.  Okay, so why is Australian Research Council not sure?  I'd have to look at the way it's actually listed in research data Australia.  Good question. It may be an NNote thing or it could be the way we're exporting it.  I'll drop that down and have a look at it if this isn't going to load,  and we'll take that off the line.  Yeah, not sure. I'll have a look at that one offline and keep moving.  Hopefully it's just the NNote support for it.  Okay, so where to go for a little bit of help?  I'll just go back to the collection page down again with the button.  I should have said that, sorry, just while I was on that page,  the export button only shows for collections,  so we're only supporting the export of datasets at this stage.  So that's why it's not displaying on that page, which is an activity.  Sorry, quick side note.  Just next to the export button, there is a question mark to grab help for the export.  Click on that. There is some online help.  A little bit of information about why we're sort of supporting NNote,  and again, it's just to do with the reference type support.  Step by step of how to export, pretty straightforward.  We also have how to configure your computer to open RISC files.  So if you haven't used NNote before and you've just installed it,  your computer probably won't associate the dot RISC extension on files with NNote  to open directly or to open via a click.  So there's just some instructions on how you can do that in both a Windows and a Mac.  And then the last set of instructions is how you can actually configure that  custom file field to display as rights in your NNote instance,  which is really straightforward.  It may be something you want to do if you use NNote desktop a lot.  NNote online, you can't actually configure a lot  and you can't configure the preferences on these fields.  So it'll just display as custom file, but hopefully you will understand  when you look at the information in that field that it is rights information.  Okay, so that's pretty much it for exports.  I think that's going to be really handy.  There has been people asking to be able to export from Research  to Australia.  I know that another piece of functionality we're looking at is being able to export multiple  records that are listed in our search results because there are obviously people doing  does say reviews and things like that.  So we will be looking at that in the future if that is something that's  been to your mind about a request.  Okay, so the Orca Import Wizard enhancements,  if you've had experience with the Orca Import Wizard,  the first interface that we did was sort of a quick sort of get something up  effort.  It worked and people are using it, but there are a few sort of usability issues  that we wanted to address in the new version.  So really the emphasis that we've put on the new version is around reviewing the  collections that you got to import into your Orca profile.  So there have been cases where people have come to the old import wizard,  excuse me, and they have clicked import all without actually reviewing if they were  actually associated or had some input into the collections.  So what we've done is we've removed the import all.  We've provided check boxes so that people are actually checking and looking at what  they're actually going to import before just saying yep, all good.  We've put in a little mini review and import workflow and some guidelines on the  page just to, they're not long, they're just a couple of dot points to restrict people  on sort of what they should be doing and when they should be importing  clutches to their profile.  The other little change that we did, they already imported data sets section.  Previously if you imported records into Orca and then subsequently remove them from  your Orca profile, we never actually updated the list of imported data sets at our  end.  So for this release, if you remove something from Orca, we actually remove it from  our end as well so that they're synced and consistent.  The last one there, citation metadata added to the search index.  So previously if you're, there were a few collections where somebody's name was listed  in the citation information or citation metadata of a collection but they weren't  listed in a party or something like that but they weren't being returned in the  Orca search.  So we've actually indexed citation metadata so if your name does exist in the  citation, we'll pull out those collections for you to import.  So if you haven't used the import wizard, I've just logged into my Orca profile in  production.  Down the bottom here where this works, you can click link works and there's a number  of options of where you can go and get works that you put into your Orca profile.  We're obviously at the top probably because we start with a hang on a day and you can  just click that and it'll fire you off into the Orca import wizard.  You obviously have to give authorization to allow us to push information to your  Orca profile.  So just click authorize and it should log us into the import wizard.  So the interface is pretty similar.  I probably should have used test.  In the suggested datasets, we will list any collections that we find that are directly  related to your Orca ID in Research Data Australia or related to a party which has  your surname.  So there may be some false positives in that list but hopefully we get most of them right  and you don't obviously have to import them all.  It's best to review them beforehand.  There's also the search that you can put under.  So if I want to just find something.  Just done a search for biology and again there are checkboxes against the records.  I apologize I should have done this in tests where I had some suggested datasets and what  happens is you have checkboxes in both the suggested datasets region and also in the  search and you can actually select across.  So I can select these two in the search for import and I can also select whatever is in  the suggested datasets and then click the import button.  So the import button only becomes active once you've actually got something selected.  So I've got these two selected and it will tell me I've got two works to import.  These are the guidelines I was talking about very brief but will hopefully eliminate some  datasets from being imported to people's profiles that aren't relevant.  And the section down here is the datasets already imported.  So I want to say import these works from my production profile.  That should get updated.  So I click the button and I'll get this little mini workflow.  It tells me how many I'm about to import.  It tells me just to review them to make sure they're appropriate before continuing.  The little minus icons next to which these allows me to remove items from import  before I click the import button.  Once I click import, it will go off and it will import them into give me a little congratulations.  It should be imported into my Orca profile.  There's a little note here just to review and set the appropriate visibility settings.  So not everything that gets published to your Orca profile will be public and you should  obviously decide what needs to be private and public in your Orca profile.  Let me just refresh this page.  None of the works it should have.  This has got nothing to do obviously with my profile but I'll just use it as a test.  And you can set the visibility here in your Orca profile and I can also remove it which I'll do in a second.  So if I just refresh this page.  There we go.  You'll see against the one that I've already imported there's a little imported label.  And you'll also see all the imported datasets over here in the right.  Now if I go and delete this from Orca and say no it's not actually do with me.  That should go.  And then if I refresh page it should drop off.  My datasets are already imported as well.  So that's pretty much all the changes we did for the Orca interface and hopefully it's a little bit more user friendly.  And we'll prevent some imports of collections.  Okay.  No questions?  Okay.  I guess the other thing tonight is we do have a video for the Orca.  How do we import works into your Orca profile as well as a help.  The information is still accurate.  We'll still assist you in importing collections into your Orca profile but we are looking to update that in the near future to the new interface.  But really it's pretty straightforward and you shouldn't have too many issues with importing.  Okay.  Okay the new RDA feedback form.  So we had some feedback from a number of people and for a long time we've sort of known that the Contact Us page on RDA wasn't ideal.  So we had some feedback where people couldn't actually find the Contact Us page and they had to go through other means to find it.  So for this release we have updated the Contact Us form to a feedback form.  It's available via the left hand side of Resource Data Australia on every single page and it's quite prominent so people shouldn't have a problem finding it.  The new feedback form provides users with some predefined request types on what they can actually ask for or suggesting.  And it's embedded in Resource Data Australia but it's actually a Dura form.  So it's linked directly to Dura. It will create service test tickets automatically and then we can track your requests and things and push them through the appropriate workflows.  And obviously we're hoping for a bit more user engagement in Resource Data Australia from the community now that they can actually contact us a lot easier.  So again I'll just flick over.  This is test, that's fine. So you can clearly see that there is a feedback tab on the left hand side. We've put it in the white section of the page, pretty much on every page so that it stands out.  And no matter where I go this should be available to provide feedback.  If I click the tab it opens a form for me to fill out.  You'll note that there is a none option at the top and this is something that we will remove eventually but there was some issues with taking down Dura to actually remove it.  So for this release we've just left it in but we've defaulted obviously to request helping the option.  You just need to fill out a subject and a description and provide your name and email.  And one of the good things about this feedback form is that you can actually upload a screenshot.  If you've come across a bug or you've found it's something that you'd like changed you can actually annotate a diagram or something and actually upload it to your Dura issue and that will assist services.  And whoever is looking at that issue to respond quickly and appropriately.  So the issue types request help report an issue, suggest new functionality in Resource Data Australia.  So we've got some good ideas, file means, and recommended request data.  We've looked, been looking for some data in Resource Data Australia and you haven't found it.  You can suggest some data that we may want to look at getting into Resource Data Australia and any general feedback you want to provide to ends.  So hopefully that will be really useful for our end users.  Time on 43.  Okay.  Come on.  Okay. So that's pretty much everything.  If you need more information, obviously the online services news page has been updated and you can also contact services at ends.  So I've got the online services news page.  I think it's open.  So news and events on the left hand side of the ends with page, homepage and then online services news.  And then there's some release notes for our 13 models in it, any non technical help that we can provide for our 13.  We've also recently updated the online services homepage and we're in the process of updating the information within the individual sections of the online services.  So hopefully that will help people find what they're looking for in a quicker fashion.  And for those that haven't come across it, there's also the ends developer toolbox.  So if anyone's out there that would like to reuse parts of ends code or even the whole registry, we have that available.  And that's just the research data for the ends that all they use, the RDA URL slash developers.  And there's also a link on Research Data Australia down the very bottom.  Where am I?  So there is a developers link down the bottom, which will also link you off to the developers toolbox.  The last thing is just that you may have noticed that there was a longer downtime or longer unavailable for publishing in this release.  So we went read only mode on the Wednesday, close of business five o'clock and had the release on the Thursday morning.  And just to let you know the reason for that was we were doing some upgrades to the software on our production box as well.  And we just needed to make sure that there was no records coming in while we were doing some work on the database.  But other than that, that's pretty much it for Arthur.  Thanks all. Bye. Cheers.
Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_0_6143.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_6144_7139.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_7140_8423.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_8424_8471.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_8472_11099.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_11100_12371.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_12372_12659.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_12660_19031.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_19032_19235.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_19236_20123.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_20124_24683.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_24684_26231.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_26232_26339.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_26340_27323.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_27324_30383.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_30384_37691.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_37692_37991.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_37992_40751.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_40752_40895.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_40896_40967.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_40968_41099.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_41100_41171.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_41172_41567.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_41568_41615.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_41616_41819.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_41820_42119.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_42120_45095.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_45096_48107.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_48108_52559.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_52560_53459.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_53460_54251.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_54252_54791.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_54792_56963.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_56964_58991.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_58992_59063.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_59064_59531.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_59532_59819.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_59820_60407.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_60408_61019.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_61020_61355.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_61356_61907.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_61908_61955.png Release_13_-_Research_Data_Australia_-_a_Closer_look__July_2014_wCIqGVcmDck_61956_61992.png