 Okay, welcome everybody. Our presenter today is Joel Ben, one of our Ann's employees, who will be going through the latest release from Research Data Australia, so Release 11. Have a good evening. Excellent. Thank you again. Welcome everybody, thanks for coming along. Today's presentation is going through Release 11, we put out last month. It's going to be quite a short presentation just because a lot of the stuff that was in the release behind the scenes and also for Ann's staff. So the first thing I'll go through is the RIVCS changes that happen once a year. So these are structural changes to the RIVCS schema. As some of you will know, we have a RIVCS advisory board. Proposals that come in basically get logged with the RIV, the RAB, the RIVCS advisory board. And then once a year they'll approve certain changes that will implement towards the end of the year, which we did in November. So I'll just go through it. There are only minor changes to the schema as part of it for this year. So on the Ann's website under technical resources you'll see the RIVCS schema menu item. So the documentation here has been updated for RIVCS 1.5, which is the latest version. So all the schema guidelines, the overview documents and things have all been updated. I'll just jump into the guidelines, just to give you a quick visual of what's actually changed in the schema itself. So if I scroll down to the diagram, just zoom in. Hopefully everyone can see that. Okay. So what's actually changed in the schema for this year has been the related info element itself. So the related info element is used to relate to things that obviously relate to the collections or party services activities that you're providing. So as part of this release, what we've done is we've added the relation element as a sub-element related info. Some of you will be aware that the relation element is an existing element and it has been in related object for quite some time now. So the enhancements to related info give us two things. The first one is we can now provide richer relationships between related info existing object types. So those are websites, publications, metadata, data reuse, and data quality. So we can now describe the relationships between a collection and those entities itself. And then the other aspect is what has changed in this release is you can actually use related info to relate to collections, parties, and services via an identifier. In the past, we've had people that wanted to relate to classes or collections in other people's data sources, but they didn't necessarily know what the key would be. But they knew what, say, the DOI or the handle or a unique identifier for that collection would be. So this basically allows us to relate to another collection via an identifier or another publication via its identifier and also describe the rich relation between the two. So that's really the only structural change for this release. Oh, sorry. The other thing that has changed is the identifier has been changed from just a single entry to multiple entries being allowed. So you may have a DOI, a handle, and a URL for a collection that you can actually describe in here. The other changes that were taking place were all in the vocabs for RIFCS. So they were vocabs to support the changes in the related info. So in the related info types now, there's obviously collection party services and activities. And obviously we've also added some relations to describe richer relationships between collections and publications. So we can now do things like is cited by all supplements. So if I just go back into the RIFCS page and I'll open up the controlled vocabs, scroll down and you'll see there's now a section for collection relation type for publications. And this is obviously only for use with related information. And when you're entering a collection record and you're relating it to a publication, you now have these relationships available. There were some changes to the identifier's vocabulary as well just to support those richer relationships. We now have the NHMRC identifier so we can relate to activity records or grants that are under activity records on the NHMRC. In the related information type, as I said, there's now activity collection party and service, which are existing classes in RIFCS. And again, the related information identifier types were basically added. Existing ones from the normal identifier type vocabulary and also extra ones to support richer relationships between the objects. So what I'll do now is I'll just jump over into the registry itself. So just in the demonstration environment to start with, and I'll just show you a quick example in the registry screens of how these changes have been implemented. So if I just add a new record, I might zoom in a little bit just so it's a bit easier to see. I'll just quickly add a collection but just go into the related info tab there. You'll see, well, if you've known this tab previously, you'll notice that the changes there is an add relation button and an add identifier button where previously there was just the field for add identifier because we can now, obviously, add multiple identifiers for a related object. If I click on the add relation, we'll obviously have the relation types that are available in all vocabs. If you are using these screens, please note that there is a 16 item limit in the lists. So if the item that you're looking for isn't displayed, it's most likely that it's pushed down to the bottom of the list and isn't being displayed. So you can actually type the relationship that you're looking for and it will filter the list for you. So as you can see here, this is a new one for the relationship between a collection and a publication. Another thing to note on the screen is we've implemented the ORCID widget in this tab as well as the related objects tab, which we did in the previous release. So if I start to put in an ORCID identifier, I can actually... I'm not showing... There was me for two seconds. So I'm just switching environments to see if I'm working here as a better example. Okay. Sorry about that. A little bit of a hiccup in the other environment. So you'll see when I start to enter an ORCID identifier, I actually get some options here so I can look up an ORCID. So if I know the ORCID identifier itself, I can just enter it straight away and hit look up and that'll actually resolve the ORCID identifier to the person. Or I can actually use a search which searches ORCID directly. So I'll just do a quick search called surname black. It'll give me a number of results and when I select an item, it'll actually retrieve the information from ORCID itself. So this is going to be really useful going forward if users or data providers don't actually want to provide party records for researchers. They can actually link directly via the related info to ORCID objects and we'll actually do some display stuff in RDA which I'll show you in a second. Here's the question. So just to answer your question, I'll just ask if there is a list of available relationship types which has changed for this release and that is on the vocab page. So through RIVCS, technical resources, RIVCS schema and then if you go into control vocabularies, they're all structured with their headings for the different vocab items, I guess. So the related information type is here and the related identifier types are here. So yeah, it is. It's not ideal in the screens at the moment and there is a change control in the backlog to actually fix those lists to make them a bit more user-friendly and display everything or at least a scrollable list inside the dropdown itself. The only other thing to note was just a slight vocab change for description. You can actually now describe the lineage to do with the collection itself and that's really the only other vocab change that has been put in. So going through the display stuff for RIVCS, I'll just jump over into RDA. So this example here, excuse my dummy data. There's a bit of rubbish in there. This is an example of where I've used the related information changes to relate to nearly all objects that you can relate to through related info. So you'll see over on the left-hand side there's a few pages in RDA. Previously, what we had there for related info was literally just a heading that said more information and we were just dumping the entered information underneath that title itself. As part of this release, we've actually recognised the different subtypes in related info. So you can see I've got a couple of related publications here where the DOI will actually link off to the publication itself or wherever the DOI results I should say and the notes about the related info itself. Underneath that, I have related websites, re-use information, data quality information and additional metadata. The thing to note with the related info, if you have used the related info to relate to what we class as a registry class or a collection, a service, an activity or a party, and you've at least given that relationship a title. So if I just flip back into the screen here. So if you've at least given that related object a title, it will actually display in the connections box on the right-hand side. So this, my activity record which I've entered is a related information activity where I've actually provided an identifier, provided a title and I have the relationships filled out and you'll see that there's two relationships here. So at the top we have this activity contains and also describes the collection which probably isn't the correct use of the vocabulary. But you can obviously have multiple relationships for those. So that's for activities, parties, services and collections. If they have a title, they will display in the connections box. If they don't have a title, but you've provided an identifier which exists in another object within the registry, we'll actually go and fetch that relationship for you and display it in the connections box. So hopefully this is all making sense. If not, feel free to ask questions. So here's one where I have use-related info. It might be easier if I just show you the data in the background. It might make a bit more sense. So this is just looking in the registry at the same object. You can see that I've use-related info. The type is an activity. I've given it a title. I've also given it an identifier. Now this identifier exists in an activity record which exists in a Research Sider Australia. I'll go to the right page. So what we do is we go and pull back the relationship to that object in RIVCS or in RDR, I should say, and we display it like any other relationship that would be provided in the related object element in RIVCS itself. So you get the link to the record and the brief description or the first description that we can find for that object. Now you're probably wondering why there is multiple objects there when I just had the one-related info. And this is because it's dummy data where each of these objects actually contain the identifier that I linked to. So you'll see here the R that I was linking to via this collection is contained in all those activities. And that's fine. And that's something that may happen if you're using, let's say, you're entering a collection and you relate to a party record and you provide, say, an NLA identifier. We have multiple records with that NLA identifier. They'll all show up in the Connections box. And that's not a bad thing because people will be able to link through and then find the collections that are mapped to each of those party records in Research Data Australia. Another question. Who are the backlinks from the activity display pointing to the collection? Good question. Yes, the internal and external links that you can set up in your data source account also work backwards or forwards as they do for a related object. So I'm in the activity now. And I should have a link back to the collection that I was just in, which is use related info to do the relationship. And as I said, the internal and external settings in your data source account will take into account the related info relationships as well, just like it has in the past for related object. Okay. The other one that I did skip over is awkward identifier. And if you have used the related info to link to an awkward ID. So in this example, it's not a fantastic one because my awkward profile is pretty limited. But again, in the background, I'll show you the data behind this one. In related info, I've said it's a type of party. I've given it a title, which isn't necessarily required for an awkward because we do some special processing. I've then done a lookup for an awkward ID, which is my own, provided a relationship and just a little bit of a note for display. So what we do in Research Sider Australia is when you actually click on the link for an awkward party, which is shown in the connections box, we go and retrieve the information back about that awkward object itself. So if I had some descriptions about myself in here, which he would show, and there's also obviously a link to view the awkward profile in awkward itself. So I think that's going to be a really useful feature going forward. We've had a lot of, I guess, issues in the past with party records being provided by different institutions for the same person. And if we start using unique identifiers and known identifiers for party records, we'll end up with, I think, a better mesh of relationships between collections and works, I guess, entities themselves. Okay, so that's pretty much it for the formal RIVCS changes. If there's no other questions, I'll move on to the next piece, which is experimental changes to the RIVCS, well, outside of the RIVCS schema, but it's acceptable to import and actually add these elements into your records. Now, this is a trial project that's being managed out of Ann's Melbourne office, so if you do want any information on it or you want to participate in it, do just drop services at Ann's an email, and they'll put you on to the right people. So what it is, it's experimental of support and display for links to data and the tools that can be used to work with that data itself. So in the past, you have been able to provide links directly to data via the location element in RIVCS, but you couldn't really richly describe the object or the file itself through that location element. So as a trial, what has been proposed is this structure that you can probably see on the screen now. You'll note that there is XRIF. There's probably not many of you who understand or know of XRIF unless you've been through the developer toolbox. Just a quick intro to XRIF. Basically when your records are ingested as RIVCS into the registry, we actually convert them into XRIF which we use for the display and research that are Australia. And XRIF, what we do in the conversion is actually we do things like we resolve subject codes, we go and find the relationships to the objects in your data source and we pull back literals and things for those objects which makes our job easier at display time in research data Australia. So in the registry, if you're a super user so someone in hands, there's actually an option to show XRIF data itself. So this is sort of enriched RIVCS that we use in research data Australia just to make our lives easier to display relationships literals for subjects. And it also enhances the search. So if we didn't do this the conversion or the resolving related object, when you did a search for a, let's say a researcher you wouldn't actually find the collections that researcher is related to by doing this the researcher actually shows up as a related object in the XRIF itself which is indexed for research data Australia. So it was a very speedy intro to XRIF but basically the new annotation stuff which is the trial is part of the XRIF extension to RIVCS. So what you can actually do is describe digital assets underneath the XRIF annotations element. So as you can see here we have digital assets so you can describe multiple digital assets. So for a collection that you've provided you may have different files, so zip files you may have in different formats things like that. You can obviously, you can point to the URL for the file itself. So this is a directly accessible and public link to some data. You can describe the title for the data and then have the file name itself which may be different to the title or the title is probably better for display and research data of Australia. You can describe the file size which is helpful for people who are going to download it maybe over a dial-up connection or something quite slow. Any notes about the data, so how to reuse the data, how to maybe some access or what tools are supporting the data itself. Now the last block down the bottom is the tool side of the data itself. So this is where people can describe the services or the tools that can be used with the data itself. So the first element in Supported By is the key. So that is allowing users to point to registry objects or services in the registry with specific key which can be used with the data itself. The one that's probably going to get more traction is the URL itself. So there a URL pointing to a tool that is hosted online somewhere where the data itself is automatically loaded for the user when they click on that URL or they can actually load the data somehow to the tool that's located at URL. You can also provide a title and a logo for that service itself and I'll show you how these are used in research data of Australia. So this is an example where the annotations has been used in the XRIF. As I said, you can provide this via a harvest, via the import option in the data and in the dashboard and I'll also just show you quickly that you can actually provide this in the registry object screens as well. Now as I said though it is a trial so if you want to participate you just need to email services at ans.org.au and they'll put you in touch with the Melbourne office who can assist you with any queries and talk you through supplying this information. So in research data of Australia, the first thing you'll notice is there is now data heading over in the right hand column and this will provide links to all the URLs that you provided for the data in the annotations block. So if I click this, this will obviously take me to the publicly accessible data which is just an XML that I uploaded on Dropbox itself. I'll also just give you the little format which will be helpful if there's multiple versions or multiple formats I should say of the data itself. And then when I said down the bottom there was obviously for the services or tools that can access the data you can provide an image and this is the image here. You can also have obviously images for the data if it makes sense and also the title for the service or the tools itself and for this one I've just provided a URL which is an external entity which I just found a visualisation for some I think it's FlickrData itself. So you know once this gets traction I think if it gets formalised in RooFCS it's going to be a great tool going forward to just provide that direct access to data web for it's a little bit I guess obscure of how to access the data itself sometimes where you just have a URL under access whereas this we can actually point to tools and describe the data in a ritual way. So that was the experimental and trial support for annotations and digital assets. For anybody that's interested in the data citation index there were some changes in release 11. Anyone who's participating you probably know about those already and if you want any information on the data citation index exports to Thomson Reuters again just email services at ANZ and they can put you in touch with other people. The other side note that I can't really show you at the moment in release 11 we re-implemented the Twitter feed that comes out of Research Data Australia. So in our 10 a lot of you will know and it will have noticed that we basically re-wrote Research Data Australia and the Orca Registry and as part of doing so we sort of dropped off the Twitter feed that comes from Research Data Australia. So as part of our 11 we re-implemented and on a weekly basis we basically provided a digest of any collections that have come through with specific ANZ FOI codes so if you are following you'll see on a weekly basis it will come through and say something like 23 collections were added under Earth Sciences or something similar. So that's been re-implemented for anybody that's interested. It's like my data users there were obviously some changes in our 11 nothing that can really be seen visual if you are a Site My Data user there is now support for authentication with the service via a shared token so in the past Site My Data users would actually have to register IP addresses which they then authenticate with so that the call or the mint request coming from a machine actually had to match the IP address that we had registered for the account. As part of the release we've implemented shared tokens so each account will be given a shared token which is just a unique 10 digit string that you can actually pass instead of the IP address of the machine and it will authenticate those users or machines. The other slight change to the Site My Data service we've had people in the past request obviously being able to admit production and test DOIs at the same time or in parallel which was quite difficult via a single account so as part of this release we've implemented a procedure where we're giving people two separate accounts one test account and one production account and that just means that they can run those two in parallel so they have a production system running and then if they're making any changes to their system they can obviously test that in parallel through their test account and again if you have any queries and you haven't been given a shared token and you want one contact services and we'll be able to sort that out pretty quickly Last but not least some people may have noticed that the Topics menu has disappeared from the topic of research started in Australia it's been rebranded Themes it basically is part of R11 we've implemented some functionality in the Orca registry at this point in time for and staff to be able to stand up pages or theme pages quite quickly which if I just click on any of these in order the staff can obviously provide some descriptions quite easily they can upload images which can be used in an image gallery and then obviously there's some search results that can be related to specific themes and this is going to be I think really useful going forward because we obviously don't have to wait for releases to put new content into research data in Australia and we can really highlight specific I guess collections and data sets in research data Australia going forward that's pretty much it for everything that's external as part of R11 as I said there's a lot in the background for and staff and also just to enhance and and speed things up in the registry and research data as part of R11 as I said there is there's ample help via obviously services itself on the ANS website itself under the news and events there's ANS services news so there's just a little block about what was implemented in service release 11 and anybody that's in the registry itself industry just on the dashboard in the registry you'll also find information about what went out in the previous release and any older releases itself we are having one more service release for this year which will go out next week but because there's been a really short timeframe between R11 and what is going to be 11.1 it's really only minor bug fixes that we've had in the in assistant for some time just to clear up before the end of the year there'll be announcement going out probably tomorrow about that release okay well that was quick and easy but yeah if you have any questions drop a line or an email to services at ANS and we'll get back to you as soon as possible thanks all for attending