 In this session, we are going to talk about persistent identifiers, which is one of my favorite topics as a PIDs nerd for at least the last 10 years in the data space. We're going to talk you through what they are and the identifiers services that we offer through ARDC and how you can leverage them in your projects. And then we are going to hand to Melroy to talk through the AAF single sign-on. So, just starting with an acknowledgement of country. So, we acknowledge the Australians on whose traditional lands we meet and pay our respect to the elders past and present. So, I'm in Brisbane. So, this is the Turbull and the Edinburgh Pids. So, persistent identifiers. I'm going to tell you what the requirements are for the ARDC project co-investments. So, we've already had the way that the ARDC encourages our projects to produce fair data outputs. And for these reasons, because we are such strong fair evangelists, and it is part of our interest guidelines as well, that it's a condition of ARDC investment that the project outputs must have appropriate persistent identifiers, because Pids are one of the backbone pieces in fair. So, there are two, we have a policy guidelines that you can access for the projects on the website there. So, there's a link down the bottom. So, this is around the metadata describing the outputs that you produce should use the Pids, persistent identifiers, referring to project activity and project inputs. And there are a range of examples there from funding to samples, instrumentation and if there are exceptions, then you just need to document those. So, we have a suite of Pids services that we offer through ARDC and in collaboration with the AAF-led Australian Orchid Consortium, they're the backbone of enabling fair research outputs via Pids in Australia. So, through our data and services portfolio, we provide to the sector DOIs, digital object identifiers, and through the ARDC service, you can mint DOIs for research data, software, grade literature, and also for research instruments. We also have RAIDS, the research activity identifier, that's an identifier for research projects. And Siobhan will explain that later in the piece and how that's different to grants. We have IDSN, it's all just collected during the course of research. We have a Perl service which has research grants, mainly for the ARC and NHMRC and provides a landing page for those through the Research Data Australia portal. And we also have a Handle service, and that's for data that isn't yet at the stage where it's being published and requires the DOIs. And Handles are also used in RAIDS as well. So, these Pids are captured and displayed in our Research Data Australia service where they're also harvested by international partners. So, it's part of exposing Australian research data to the world. So, just backtracking a little bit into what is a Persistent Identifier. And just adding thanks to PID up a loser is an happens every year the whole international PID community generally is involved in. And we helped contribute to this development of a slide around Pids 101 since the portion of that debt. So, what is a Persistent Identifier? First of all, it's persistent. That is, it's going to be around for a long time. We can't really say forever. I don't think anyone can say forever, but for a long time. And that's a promise that the organisation makes to keep it alive and the PID provider as well. And it's also unique. So, many people can have the same name. So, there may be many John Smiths. And a Persistent Identifier is a unique ID that would be used to identify one of those John Smiths. And if you take the Persistent Identifier example, if you assign a John Smith an orchid, then that orchid will link that John Smith with the works that he produces, regardless of the ways in which his name is referenced in the articles that he produces. So, Jay Smith or whatever, it links it all that way. So, there are a number of PIDs in research. So, we have PIDs for people for the researchers and contributors. And some of those are PIDs that you can use are ISIs, but the main one that's being used in Australia is orchids. Also, there are PIDs for BASES, which are research organisations. And the PIDs that you can use for that are GRID and RAW, slightly different types of organisation registries. But I can talk through that later if people are interested in that. We also have PIDs for things. So, research for inputs, grants and so forth. And days through crossref and data site, who are registration agencies for digital object identifiers, you have to send rates and a whole lot more. So, this is an interesting slide because it shows so if you look at that original sentence in the middle there, a persistent identifier is a long lasting reference to a digital resource. Well, it's actually a reference to a resource because it can reference physical things. There's metadata collected in the course of minting a PID so that you can tell more about who is minting it, what it's about. It has a machine readability aspect. There's a lot of policies and guarantees around PIDs to make sure that when you do mint them, they do last. And there's provenance information around a persistent identifier that's collected as well in the metadata. So, what can PIDs do and why are they important? Well, first of all, they help disambiguate. So, I gave that example before of John Smith. But you can see as well in this orchid example that it collects the name variations for, in this case, Robin Gasler. And it gives her that the PID there is the orchid identifier at the top. And down below you can see she's got other IDs that are collected on the orchid record. In this case, the researcher ID. So, they help to disambiguate and link a researcher to their works. They also support linking. So, you want to be very sure in scholarly communications that you're citing the right material. So, something like a digital object identifier. You can be sure that the reference that you're looking for is that thing that has that DOI and not a whole lot of other things that look very similar. And they also support linking between articles and data as well through those DOIs. They collect metadata and they enable interoperability between different systems. So, they could be systems that operate within a university or external systems, say, different publisher systems that can exchange information. They also help make research fair, the findable, accessible, interoperable, reusable, which we've gone through in quite a lot of detail. And there's a lot of references to PIDs and collecting metadata that are important in making research outputs fair. They also support a trustworthy research infrastructure. So, they help us track things from grants through to publication through the research cycle. And be able to say that that thing, that grant is related to that publication, is related to that data set and so forth. And that helps to build trust in the system right from the start. So, a number of PIDs that you collect together can be used to form what we call a PID graph. And that this is a very, we want to be able to make more of this type of thing. And I have to say that Melroy is the expert in PID graphs here. So, if you have any questions around that, he is the one to ask. But you can see that if all of these different things, authors, publications, data sets, institutions have persistent identifiers, and those identifiers describe the relationships between those things, then you can start to do some very rich querying. So, you could start to say, I'm an institution, give me this particular grant, give me all the articles that were produced from that grant, all the data, all the authors that were associated with that. And so, you can start to see a wide network of co-authors and relationships between those objects. So, this is something that is, there's a version of this available in research data abstractions. So, you'll be able to see it on some of the records. But there's a number of PID graphs in production across all these different things. But it shows you the potential of what we can do as we assign them across the system. So, PIDs are part of national infrastructure. So, we have the national research infrastructure that's about creating naturally significant assets, facilities and services that support leading research. And PIDs are a core component of this national infrastructure key to a world-level research infrastructure. So, we think that by PIDs, the PIDs are a foundation for and for attracting a great impact, which you can see in that graph. And by precise importance of research, the PIDs contribute to research. Well, anything scientific concepts, systems, and efficiency, PIDs are just different to the PID projects. So, we want to explore our policy a bit further. But just to cap off on that, price a high value on the use of PIDs in research. And we offer PIDs services to the Australian research sector to facilitate their uptake. For example, research data, if instruments aren't made literature, or the research data, we take these to data sites so that your organisations can use that service to mint those DOIs. Part of the strategy to optimise sustainable longevity and global acceptance, our PID services are offered in partnership with international PIDs. So, as far as I mentioned, the election is that better? I'll sit a bit quite up. Yeah, it's your connection. Could you maybe turn off your video? I don't know. I don't think I can do that without stopping the share. Just a second. Is that better? No. Yeah, it is. It is better? Yep. Okay. Well, I hope you heard that one. Okay. So, just to recap a little bit about PID services, which is offered in collaboration with international PID providers, data sites that we have, actually looking at what PIDs we do in our services suite, looking at the attributes of good PID systems and their technical architecture, government structures they have around them, and also the community uptake of those, as well as cost effectiveness and sustainability. And just to mention that the AIC as well is very, very active in the international community. We serve on a number of boards internationally, committees and projects and initiatives, which help contribute to the adoption. And I will now hand Joel to talk about which PIDs you get from us and how you get them. Thanks, Natasha. So, which PIDs can you get from AIC and how do you get them? So, as Natasha has already mentioned, AIC offers a suite of identifier services through its partnerships with international PID providers. So, we have DOI, IDCEN, Handle and RAID. So, DOI enables the creation of system identifiers for data associated workflows, software models and grade literature. And AIC actually provides access to data site services directly. So, through our consortium membership model, we provide users access to the data site interfaces and APIs directly. We also have an IGSN service. So, this is system identifiers for physical samples and specimens. And originally IGSN was very much focused on the Earth Sciences domain, our discipline, and it has been brought out to any sort of research physical samples and specimens. The Handle service is more of a general purpose system identifier. It can pretty much be associated with any sort of research entity. And it's generally used where another identifier such as the DOI is not appropriate or usable in those instances. The RAID services, and Natasha has already mentioned, is all about research projects and being able to provide some linkage to research projects and provenance, et cetera. And Sheform will go into that in a little bit more detail. Now, each of the services, they cover a different use case in the research ecosystem and they have their own governance models, as Natasha sort of alluded to. They support the creation, obviously, of persistent and globally unique identifiers, and they're free for use by Australian researchers and research organisations and institutions. So, as Natasha said, the ADC is currently covering costs to be members of those international persistent identifier organisations, and then we enable the access to the services through those memberships. Next slide, please. Now, in terms of interacting with the services, as obviously a number of ways, the easiest way, I guess, is through our web interfaces. So, all of the services have web interfaces and they enable the creation and management of persistent identifiers through a browser. They're primarily used to create smaller numbers of records, identifiers, so you possibly wouldn't want this if you were creating thousands of DOIs or handles, et cetera, but they do allow you to get up to speed pretty quickly. And the interfaces, they assist in creating rich metadata records, and they do this in a number of ways. So, a lot of the forms that we have, they'll have in-context help for each of the fields, so that you'd be able to see what's sort of expected in those metadata fields, you'd be able to see the vocabularies, and we also have widgets in some of the forms that we have. So, the example on the right, there is an ORCID widget, and that, when you're filling out an IGSN metadata form, it allows you to look up a researcher through their surname or first name and surname, and I'll actually pull back the ORCID information and pre-populate the fields for you. And we also have things which allow you to link to grants in Research Data Australia and map widgets that allow you to find some spatial regions when you're filling out the forms. So, that obviously assists you in creating really nice rich records that are obviously good to share and provides that fair principles within your metadata. Another advantage of the forms is that there's no technical skills or expertise required, so if you can use a browser, you can pretty much log into the service and get up to speed pretty quickly in using the service. You also don't need to understand the underlying metadata, so a lot of the services, you obviously got a metadata component that is associated with the system identifier and using the interfaces, you don't actually need to understand the metadata schema at all. Next slide, please. Thank you. The other way to interact with the services is through APIs, so all services contain APIs. It's a mix of sort of remote procedural and REST APIs, and they allow you obviously to integrate with your applications, platforms and services to automate the creation and management of identifiers. And obviously, this is probably the most efficient way to get large numbers of identifiers to sort of integrate them within your workflows and processes in your software. But there is obviously that while they're not overly complicated, the APIs, there is obviously some expertise, technical expertise that's going to be required within your projects or development team to integrate those APIs. But as always, ADC is here to help, and we have a pretty good technical team on board that can assist you with any of the things that pop up as you start to sort of tinker with the services. Next slide. So in terms of sort of exploring service and testing and doing integration testing, et cetera, we have Sandbox sort of demonstration environments for all of our services. So we can easily set you up with some test credentials where you can keep the ties, have a look around, see what's involved in creating identifiers, and actually mint some test identifiers for each of the services. And yeah, as I said, just sort of see what's involved in using the services. You'll have access to both the web UI and APIs in those environments. So it's pretty much like production service. You can use it for your integration testing. And there's obviously really, there's a lot of documentation and stuff to help you get up to speed with that. And again, ADC technical sport is available wherever it's needed. Next slide. In terms of obtaining a service account, so what I've got here is sort of a general procedure to obtain a production account. If you are looking just to use the test service, you can talk to any of the ADC contacts or email the services desk, and we can set you up a test account pretty easily. But in terms of production account, normally how it works is that the applicant would discuss or the client would discuss their sort of interest in using the service with one of the contact points at ADC, whether that's the services team and engagement officer or your project contact at ADC. And then generally, there's a service policy statement around each of the services that just outlines sort of what you can expect from ADC in terms of the service delivery and what your what our expectations of you are in using the service. And then there's obviously usually a participation agreement to use the production service that you sign and then sent through the services team. And then they'll set you up an account and send you through the details and point you off to the documentation, etc. So pretty, pretty straightforward procedure for each of our services. Next slide. Thank you. Service documentation. So under documentation.adcedu.au, we have pretty much all the documentation except the rate in our services. We will be incorporating rate very shortly. Our rate has its own pages of documentation, which shall point you to or point you to at the end of the session. But in each of these sort of sections, you'll find information about what the service does, what's involved in using the service, how they get an account, and I'll actually go down in sort of the technical details on each of the API endpoints, how you use them and what's necessary to provide in each of those API calls. Next slide. And I'll hand over to Siobhan now. Thanks very much, Joel and thanks Natasha as well. So I'm going to take you on a fairly rapid unpacking of raids and the ARDC investment identifier. So when your project is given the stamp to go ahead, you'll be given two persistent identifiers, an investment identifier and a raid. So first of those is the ARDC investment identifier. You'll be allocated it. It's a DOI. We minted at ARDC through the Crossref DOI registry on your behalf and it will be passed on to you by your project liaison or manager. And that identifier will resolve to the project page of the ARDC website. So next page, please. Next one, please. Grand. So why do we want you to have access to use this identifier? The main reason for yourselves is attribution. All of the ARDC investments require you to attribute the investment in your talks and materials, so posters, websites brochures and any publications. And we'd like you to use this DOI to do that attribution. That means it's always going to have a permanent place that people can find it and very useful for other tracking activities as well. And we'll move on to the next page, please. Thank you. So the second of the identifiers that you'll be given for your project is a raid. So raid is a unique identifier for projects. It acts as an envelope with a metadata manifest that collects other persistent identifiers that your project will encounter during the course of its activities. I want to be really clear that it's not for grants. It's for a project which we view as an activity. Research project is an activity. It takes place over a period of time. It's got set bounds or scope. It's resourced by researchers and support staff and it uses and produces data and it may also interact with other institutions and organisations. So it's not a grant. A grant is awarded to a project to do the research activity. Next page, please. And just how does raid work? Raid has two parts, an identifier and the metadata envelope, as I mentioned. The identifier uses the ARDC handle service that Joel went through briefly. The handle is a number that you could probably think of as being an address in an envelope or on a fold of something similar. We've got a nice picture of it here that kind of looks how it looks in my head. And it's made up of other identifiers that represent project activities and describe the relationship between them. So in that metadata envelope, we have grants and investments, organisations and institutions, collaborators, that's those people that resourced the project. Tools and services, that could include cloud services, or it could be instrumentation. Also data and publications. And the very first identifier that will go into your raid is the ARDC investment identifier. So that cross-ref DLI will automatically be added to your raid. Next page, please. Next page, please. Yeah, there we go. And what are the benefits of using raid? So raid is used to establish data provenance. You can also use it for auditing, collecting metrics on facilities and instrument use. It can be used as well for tying in grant access authorization and for reflecting the roles of individuals in the research process, which is something that Melroy will go through and in a little bit more depth. So the benefits of using the radar that it can really help create a timeline of the interactions of your project. It can help you get insights into investments and activities, things like cooperation, can help make those pedographs really nice and rich. It can help to develop better strategic intelligence on the outcomes for each of the investments. It can generate better evidence and understanding of impact and its impact of funding, as well as impact of staffing, as well as the impact of the research itself. It can save time on administration and reporting, particularly if you can automate those systems. And it can provide better tools for analysis and decision support. Next page, please. How do you update a raid? So if a raid is something that has other persistent identifiers listed in its metadata manifest, how do you update it? Well, once you've been given a raid, the ownership of that raid is transferred to your project, to your organization, and you'll be able to update and add identifiers to it using either the raid web interface or by integrating it with a platform of your choosing via the raid API. And if you have questions about that, AIDC can assist you in finding the best way to use it for your project, so looking at your workflows, et cetera, and also just how to do that integration. So next one, please. And last but not least, here's the contact point and further information. All of these services are on our websites, and there's much more information than documentation and in the particular Identify Services website. Thank you very much, and I think