PiDs Short bites #1 - DOIs to support citation of grey literature - 24 May 2017

Video in TIB AV-Portal: PiDs Short bites #1 - DOIs to support citation of grey literature - 24 May 2017

Formal Metadata

PiDs Short bites #1 - DOIs to support citation of grey literature - 24 May 2017
Title of Series
CC Attribution 4.0 International:
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.
Release Date

Content Metadata

Subject Area
This webinar begins with a brief introduction on the use of persistent identifiers in research followed by an outline of how UNSW has approached supporting discovery and citation of grey literature. #1: DOIs to support citation of grey literature 1 ) UNSW service for DOIs to support citation of grey literature Dr Daniel Bangert, Senior Data Librarian, Library Repository Services, UNSW Library At UNSW, grey literature materials are often important parts of the scholarly record which can contribute to research impact, and thus there is a need to make them discoverable and citable. After investigating various options, UNSW implemented a service to assign persistent identifiers in the form of DOIs to grey literature held in UNSW Library repositories. A set of conditions was developed to determine eligibility for a DOI and govern their assignment. Accompanying workflows were put in place to enable DOI requests from UNSW researchers and also meet the needs of researchers or administrators that produce grey literature on a regular and ongoing basis. 2 ) PIDs for research Natasha Simons, Senior Data Management Specialist, ANDS Natasha will provide a quick overview of PiDs for research and this webinar series, and then give an overview of the ANDS Guide to Persistent Identifiers
Web page Context awareness Service (economics) Identifiability Persistent identifier Link (knot theory) Hyperlink Metadata Number Web 2.0 Uniform resource locator Repository (publishing) Software framework Information Series (mathematics) System identification Error message Library (computing) Address space Descriptive statistics Sanitary sewer Service (economics) Link (knot theory) Information Sampling (statistics) Physicalism Digital signal Open set Uniform resource locator Sample (statistics) Event horizon Repository (publishing) Series (mathematics) Radio-frequency identification Geometry Library (computing)
Mobile app Presentation of a group Identifiability Persistent identifier Virtual machine Materialization (paranormal) Numbering scheme Metadata Latent heat Different (Kate Ryan album) Intrusion detection system Software Series (mathematics) Data structure Extension (kinesiology) Area Source code Touchscreen Theory of relativity Information Digital signal Virtual machine Type theory Time evolution Object (grammar)
Service (economics) Identifiability Link (knot theory) Information Series (mathematics) Electronic program guide Website Digital object identifier Series (mathematics) Digital object identifier
Presentation of a group Group action System administrator Disk read-and-write head Type theory Computer configuration Core dump Repository (publishing) Videoconferencing Descriptive statistics Physical system Link (knot theory) Touchscreen Digitizing Web page Staff (military) Digital signal Instance (computer science) Landing page Category of being Arithmetic mean Process (computing) Permanent Telecommunication Cycle (graph theory) Embargo Web page Point (geometry) Slide rule Momentum Persistent identifier Disintegration Characteristic polynomial Digital object identifier Number Element (mathematics) Goodness of fit Term (mathematics) Profil (magazine) Intrusion detection system Business model Authorization Traffic reporting Embargo Data type Scaling (geometry) Information Quantum state Faculty (division) Uniform resource locator Word Explosion Software Personal digital assistant Universe (mathematics) Resolvent formalism Library (computing) INTEGRAL State of matter Set (mathematics) Function (mathematics) Image registration Mereology Web 2.0 Mathematics Series (mathematics) Library (computing) Presentation of a group Service (economics) Student's t-test Term (mathematics) Digital object identifier Flow separation Connected space User profile Type theory Computer configuration Repository (publishing) Self-organization MiniDisc Website Condition number Right angle Authorization Procedural programming Physical system Row (database) Server (computing) MUD Identifiability Service (economics) Link (knot theory) Observational study Virtual machine Web browser Plastikkarte Staff (military) Metadata Hypothesis Power (physics) Wave packet Uniqueness quantification Integrated development environment Summierbarkeit Condition number User interface Execution unit Projective plane Planning Object (grammar) Videoconferencing Electronic visual display
Revision control Service (economics) Information management Observational study Service (economics) Type theory Videoconferencing Login Digital object identifier Library (computing)
Service (economics) Observational study Link (knot theory) Information MIDI Digital object identifier Staff (military) Faculty (division) Metadata Repository (publishing) Cuboid Information Library (computing)
Frame problem Message passing Link (knot theory) Permanent Information Digital object identifier Demoscene Embargo Faculty (division) Metadata Hypothesis Condition number
Frame problem Service (economics) Observational study Service (economics) System administrator Electronic mailing list Mass Student's t-test Group action Digital object identifier Library (computing) Physical system
Information management Service (economics) Information System administrator Digital object identifier Digital object identifier Faculty (division) Metadata Hypothesis Inclusion map Message passing Computer configuration Electronic visual display Physical system
Execution unit Service (economics) Functional (mathematics) Observational study View (database) Web page Usability Volume (thermodynamics) Student's t-test Mereology Digital object identifier Faculty (division) Formal language Process (computing) Hypermedia Internetworking Repository (publishing) Series (mathematics) Library (computing)
Service (economics) Information management Dependent and independent variables Observational study Link (knot theory) Lemma (mathematics) Cloud computing Maxima and minima ACID Digital object identifier Staff (military) Metadata Process (computing) Computer configuration Permanent Repository (publishing) Computer worm Procedural programming Library (computing) Embargo Row (database)
Point (geometry) Slide rule Trail Presentation of a group Identifiability Service (economics) Link (knot theory) Disintegration Digital object identifier Function (mathematics) Mereology Event horizon Metadata Hypothesis Usability Number Term (mathematics) Different (Kate Ryan album) Personal digital assistant Videoconferencing Computing platform Condition number Physical system Presentation of a group Service (economics) Video tracking Code Usability Bit Instance (computer science) Digital object identifier Type theory Process (computing) Software Repository (publishing) Personal digital assistant Computing platform Condition number Electronic visual display Videoconferencing Row (database)
Presentation of a group Oval
hello everyone and welcome to today's webinar so today's webinar is the first
on a series looking at persistent identifiers that we called peds the short peds short bytes webinar series the first one today is on do is to support citation of grey literature the second one is on identifying and link linking samples physical samples with data using the International geo sample number and the third one is on linking data and publications and that's on the scallops international initiative so today's webinar is on vo is to support citation of grey literature I'm Natasha Simon commands and I'm going to start with a brief introduction on persistent identifiers and I've been going to hand over to my excellent colleague dr. Daniel banget from is the senior data librarian library repository services at the University of New South Wales okay first of all what's the problem that persistent identifiers are trying to address I'm sure everyone will be familiar with this particular problem when you click on a web link that takes you either to a 404 page not found error like this one or it takes you to content that's not actually related to the link that you clicked and both of these things usually happen because the web resource is being moved to another location and you have the old link the page not found error is frustrating and in the context of research it's disastrous because it means that a scholarly resource which may be cited cannot be found verified potentially cited again and so forth and this is the problem which persistent identifiers are trying to address so persistent identifier is simply a long lasting reference to a digital resource even if the resource moves location on the web the persistent identifier is there to make sure the link always resolved so our pet is used as a citation link in scholarly literature it will always resolve to information about the resource either a descriptive metadata page the resource itself for information about the removal of the resource from the web pits are key to facilitating the discovery of scholarly resources and play a key role in linking scholarly resources for example publications and data as well as tracking the impact of these resources but it's important to note that peeps do not guarantee a link will never be broken but what they do is create a framework which helps to guarantee it so pips have evolved quite a lot over
the last 20 or so years this slides taken from jonathan claps presentation at the four webinar last week and he notes that now we have identified four people as well we want to know what persistence means and how long app it will last metadata has grown so there is a lot more value in retrieving the metadata as much as retrieving the object itself and that object may no longer be digital because did you can refer to digital information on a physical object which is a big growth area and we're looking at that in the IDs in webinar coming up and last but not least we want our machines to be able to interpret pigs so in this webinar series we hope to explore more of these topics in more detail what kids
applied to research data is a very good question there are many different types of persistent identifiers that apply to research data I put on the screen some common examples that and actively promotes or provide the service for such as handles for identifying data DOI citing data and related materials or orchids for people identifiers and really so many d'amore and all of these persistent identifier schemes differ in some way for example they might have a different purpose some apply generally to all scholarly resource types for my discipline specific and the underlying technology difference between persistent identifiers as does the governance structure for example some non-profit some are company driven and metadata is collected some require more metadata than others and also in the extent of use so kids vary in their uptake if
you'd like to know more about persistent identifiers there is a pig guide on the ant website and there's a lot of information about our DOI and handle service as well there's also this short likes webinar series and I highly recommend this or webinar series on peebs the first one happened as a general introductory one and that's been recorded and they are making the recording available by the end of this week and then there are another two coming up on that series so if you'd like to register you can click on those links so I'd like to finish now and hand over to my colleague dr. Daniel Bennett
okay Thank You Natasha thank you for
joining this webinar thanks Natasha shows the invite today I'll be talking through the service that we implemented at UNSW library to support the citation of grey literature held in our repositories today this is based on a presentation that I gave late last year for the core research repositories community days and that presentation the slides in video can be found at the link on your screen I'm going to briefly cover a digital object identifiers and say a few words about what they are then take you through the environmental scan that we did to design our service and then some of the details of the UNSW DIY service including the conditions around DIY assignment the workflows that we're following and integration with orchid identifiers and a few words in conclusion a DIY a digital object identifier is a type of pet that is optimized for scholarly resources importantly it's the identifier that is digital and the object can be digital or physical do is are assigned to an object by the publisher or a long-term custodian and the persistence of that identifier and the resource is managed by the organization and its policies there are a few facets to a DOI we can start with the DOI name itself which is an alphanumeric string and that can be converted to a URL by adding a deal y resolver like DOI dot org when that URL is entered into a browser it takes you to a landing page with human readable metadata about resource about the object so basic information about the resource is required to mentor TOI and that metadata is both human and machine readable so why are they always important there merged as a relatively simple but powerful piece of technical infrastructure in improving scholarly communication they make it easier for outputs to be discovered and used by others and to be cited and measured for impact a useful way to think about deal wise is as a trusted identifier which is a term introduced a few years ago by a project called Odin the orchid and data sight interoperability network that's the predecessor project - for that Natasha mentioned at the beginning this term captures a set of characteristics that trusted identifies a unique so they're unique on a global scale they resolve as HTTP URI is persistently their descriptive so they come with metadata that describe their most relevant properties for instance there's a mandatory set of metadata elements like creators title publisher publication year resource type and then you can add recommended or optional elements like alternate identified subjects fades rights information description and so on and lastly trusted identifiers are governed so they're issued and managed by an organization that has a sustainable business model and it's managed by that body which is usually a publisher or custodian you can read more about trusted identifiers at the link below when we were looking at designing a service the impetus for this came from requests from academics most commonly they had Ray literature like a series of reports that they wanted to assign deal wise to and we were also able to implement something based on the and site wide data service in April last year 2016 that was extended to account for grey literature so we were looking at at the possibilities of implementing something here at UNSW in preparation from for an options paper we looked at grey literature and DOI assignment in several repositories with the institutional disciplinary or national we also looked at options for registration agencies the resource types that we would cover a few things that we found that might be useful were a project conducted in the UK called unlocking thesis data it's a disc funded project and led by the universities of East London and Southampton as well as ethos the national thesis service at the British Library and they have a number of reports and case studies where they outline options for the workflow to assign DIYs to theses another idea that we eventually incorporated into our own service was from the University of Southampton and they have a role called a trusted partner and that allows certain staff academics or faculty administrators to authorize their own DIYs or the deal wise of a research group and I'll come back to that idea later in the presentation so in the latter half of last year we presented an options paper to the library and went ahead with a pilot which involved a manual workflow for a certain resource type reports to start with and we had workflows for both library staff and trusted partners to mint do is we then moved on to implement a web tool which I'll show you later and at the link on
your screen you can look at the do is minted by that service I think now we have about three hundred thirty deal wise minted for grey literature it was important at the outset to think about the conditions around the my assignment and the first one is that the resources deposited in a UNSW library repository our institutional repository called us works holds a large amount of the grey literature created by UNSW staff and resources in the repository are managed in accordance with the UN s works digital preservation policy so for that repository we have governance we have preservation procedures in place and we're then able to sign the DA and then potentially if the resources move or the repository moves we can make sure those vos continue to resolve the second one is that it's an illegible resource type it needs to be within a certain set of grey literature that we've defined there should be no existing DOI for the service as that defeats the purpose of a unique identifier there should be no existing DOI request and it needs to meet the mandatory metadata requirements set by the end service which links to data sites so in the user interface as you'll see later the requester is given these set of conditions which they need to agree to before they submit so they need to agree that they're an author or creator of the resource or have authorization from and also to request to DIY the resource doesn't already have a deal why they don't plan to mint a DOI using a different service the resource is unpublished or published by UNSW a repository is a library repository is the primary publication point for this resource meaning that when people resolve the deal why they'll be taken to the repository page the landing page the resource is not subject to a permanent embargo and the resource is not likely to change significantly that's just flagging that major changes like anything that would be part of a citation shouldn't be changed and that would require a new deal why this is the the workflow that we're following so for all users we allow them to request a DOI they go into the tool they select their repository where the resources most commonly are uns works they search for their record I selected the system checks if there's a deal why Christine already or if there's an existing request it also checks if the mandatory metadata is already held by the system if not they need to enter or confirm the metadata and then submit a request the second part of this is for a DIY service administrator which is currently library staff they go back in and review the the request that has been submitted they check that it meets the conditions that we've already outlined if it does that's approved it goes to the an service Minster the DIY and comes back and emails a requester with the DIY the administrator then updates the metadata and then that information is sent back into the repository and is displayed on the repository page for the trusted partners so these are faculty administrators or researchers that we allow to mint deal wise directly and that needs to be approved by a relevant authority like the head of school or associate dean and we give those people training and access to the tools they need so they follow a very similar process except that instead of requesting they're able to mint the deal why directly so they select their record they meant do the administration and the cycle is complete back to the UN s works page the institutional repository if you then resolve the DOI it takes you to that landing page and the DOI itself is displayed in the record details as part of the metadata about the publication we are also aiming where possible to include orchid IDs so identifies for researchers and contributors to research outputs to be included in DOI metadata the way we do that at UNSW is through our research output system users can link their orchid profile within that system that orchid ID is then pushed to the repository state to deposit full-text then they can go back into the DOI servers select that record submit a request and that DOI gets put back into the research output system there is then an update so both the DOI and the orchid go into the repository and both of those the organ ID and the wire can be exposed by external harvesters like trove and aggregators as well as through the orchid profile because of the connection or good and data site that can be easily claimed through data site and added to the to the users orchid profile so I
have a short video here which I'll take you through this is showing an early release so this is the version that was available at the end of last year there have been some minor modifications since then but it gives you a sense of what the service looks like and how those workflows actually look in practice so
there's a login screen that uses the usual credentials so we'll start with
the request to do live workflow here the
repository can be selected and there's a search box to pull in the information from the repository so the user selects
the record and they're given a preview
of the metadata so what we show here is
the mandatory metadata for assigning a TOI and if any of that is missing they're given the opportunity to edit they see those conditions for requesting and they submit the request there's a
confirmation message and they also have
a list of their requests and they can see the status whether that's pending or whether the DIY has been minted or
declined the next step is for the DIY
service administrator to log into the
system they have access to a tab called
review where I can see the pending requests they can then review each
request and the metadata based on that information they can eat a decline or mint if they choose to decline there's an option to send a personalized message and to follow up with the requester if they mint then that request goes to the AM service and comes back with the DOI
and then this is emailed back to the requester so they're given the DOI immediately the administrator then updates the metadata in the system you
can see that the DOI is active immediately and that's the end of that
process and the last part to show you is
the mint function for the trusted
partners and this just means that for people have high volumes of publication square literature that they need to assign to your lives or an ongoing series that
they are given the option of actually doing that directly and having
responsibility for the whole process the procedure is much the same they can
search for the record they select the
record review the metadata and then they
complete the minting process immediately okay that's a Ruppert repetition of
before so I'll just skip through the
rest of this okay so in conclusion the UNSW do is service was designed to meet existing and future use cases so it's flexible and scalable with future cases in mind a priority for us was ease of use so we're reusing metadata where possible so anything that we hold in the repository that we need for the DOI metadata we use that we use that metadata which is reviewed it integrates with existing workflows for instance with the research output system with the repository itself and it connects with other kids and platforms like orchids there are conditions set around it so we ensure that the identifier is governed correctly that the resources remain persistent and that the link can continue to be resolved and be a sizable enduring part of the scholarly record so that's handled by preservation policies by the reviewing process and the ability to track our DIY requests okay thank you very much there are a couple of links at the end of the slide there to both the slides and video if you're interested in the software itself we've made the code available and both of those of course have DIYs to access thank you very much Jeff Daniel that was that was a brilliant presentation so I suppose what your presentation shows is that there's quite a bit of thinking involved in assigning DIYs to grow it shot in terms of what the eyes either what they should be assigned to and how it should be done can you just tell us how you got that thinking process started at UNSW so primarily it was based around the infrastructure we already have in place and the policies that already governed our repository material so we knew there were conditions about what was in the repository and what we could govern so that was a starting point then we wanted to cater for the greatest use cases and make the most impact so we wanted to start with resource types that were requested by the community then in negotiating the actual conditions that was partly based on the Ann's guidelines so making sure they actually fit in with what Anne's requires the agreement that we have with Ann's and also what data cite considers best practice and from there it was basically a process of just testing those and whether that could be worked into the existing workflows and implemented efficiently okay thanks Daniel there's a couple of questions here a question from Gillian Eliot is what happens to the handle associated with the thesis used in this example so the handle will still resolve and can be used as it usually would the way we've implemented the do is is by resolving to the handle so there are a number of different ways to do that but for us it's best if the resolving URL for the DOI is the handle itself that ensures that if we ever migrate the handles would be migrated as well and therefore the deal wise okay thank you question from Julie Gardner is are you able to determine how often these DOI has been cited I believe there is some event tracking or data around events being implemented by agencies like CrossRef and data cite one way to do it is we also have Auto metric implemented at the institution so mentions that include the DOI can be tracked so that's one advantage and then through data sight itself I think that would be the best way to have a look at what kinds of events happening with particular DIYs okay thanks very much well those are our the end of our question I'd like to thank
Stan you're very much for his presentation today thank you all bye