DOI minting stories (ANU) - 7 May 2013

Video thumbnail (Frame 0) Video thumbnail (Frame 1252) Video thumbnail (Frame 2439) Video thumbnail (Frame 2752) Video thumbnail (Frame 7853) Video thumbnail (Frame 9491) Video thumbnail (Frame 11428)
Video in TIB AV-Portal: DOI minting stories (ANU) - 7 May 2013

Formal Metadata

DOI minting stories (ANU) - 7 May 2013
Title of Series
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.
Release Date

Content Metadata

Subject Area
This webinar recording examines the DOI minting journey taken by ANU. Doug Moncur and Rahul Kanna from ANU discussed: - what are DOIs and how do they relate to data citation? - why did ANU decide to mint DOIs - the process of deciding policy decisions (eg granularity, versions, what did/didn't get a DOI) - technical considerations in minting DOIs - sticking points and solutions - future plans for data citation and DOIs Further resources on Data Citation and DOIs: - What are DOIs? - What is the relationship between Data Citation and DOIs? - ANDS CiteMyData DOI service
Beat (acoustics) Observational study Personal digital assistant Real number Series (mathematics)
Goodness of fit Data management Presentation of a group Personal digital assistant Software developer Multiplication sign Division (mathematics)
Point (geometry) Context awareness Game controller Identifiability Code Real number Multiplication sign Virtual machine Motion capture Set (mathematics) Digital object identifier Metadata Number Neuroinformatik Data management Mechanism design Website Computing platform Information Building Weight Projective plane Generic programming Bit Motion capture Software maintenance Mechanism design Category of being Word Message passing Process (computing) Software repository Website Quicksort Automation
Point (geometry) Presentation of a group Service (economics) Computer file System administrator Set (mathematics) Login Metadata Number Revision control Formal verification Finitary relation Energy level Information Office suite Traffic reporting Physical system Dependent and independent variables Information Moment (mathematics) System administrator Metadata Mereology Complete metric space Digital object identifier Quicksort Physical system Row (database)
Meta element Source code Implementation Inheritance (object-oriented programming) Touchscreen Open source Source code Java applet Client (computing) Disk read-and-write head Graphical user interface Hypermedia Implementation Summierbarkeit Exception handling Library (computing)
welcome everybody it's Jerry rider beating from an I'm sitting in for Karen visit today who's unfortunately unwell but it's my pleasure to welcome you all to the webinar today and particularly to welcome Doug Raul and Dave who are going to be presenting with us this morning so today's session is as the title suggests in our data citation series it's the second in our data citation series and we have 4 in the series all together this one is going to be a really interesting session because it's some real case studies from the Australian National University and the Australian
Antarctic division about their journeys
if you like in implementing do eyes and data citation at their institutions we'll start off with the with the presentation from Doug Mahnke who's the repository manager at a and you then he'll hand over to his colleague Rahul whose assistance developer day in you to talk about their experiences then we'll hand over to Dave Connell down in Hobart at the Australian Antarctic division to talk about the experiences at a ad and then we can come back to some question time after that good that's good ok why
should we meet meant to put dui's programmatically a little context is helpful there we go we all had a number
of data capture projects and what we were actually doing in them was we were building a generic solution in other words rather than building individual tailored solution for each project we were building a solution that would actually could be adapted to provide a generic data capture platform and this basically a bit like sort of having automated self deposit by machines so in other words the machine provides some information which is a metadata uploads the data set and it goes into the workflow this is essentially the same solution as we used for our ceiling the commons and for our data repository but where people come along and deposit data it's all the same basic code the code is based around Fedora Commons Rahul wrote the actual self deposit could for machines it's noosa teal and because we're actually thinking basically about automated data capture we're really trying to automate as much as we can so all the way through we need to make things as automatic this actually is quite beneficial when we talk to human beings actually adding in doubt and depositing data themselves because people absolutely hate entering metadata I've worked to a number of such projects and i can tell you professional people professional sort of data maintenance people hate doing meta data scientists and researchers really hate doing it you just simply won't do it if you could avoid it so the whole point is to make as much as possible humanize it make it as simple as we can get it's really got to be simple it's really got to be easy pre-filled feeds all the rest of it and this also works very well for automated deposit because it's the same thing you know computers are very good at generating lots of data but they actually like doing the structured manner so what we're doing is making things as simple as possible the other great thing was at among our data capture projects we had people like astronomy genomics and so on but actually of a culture of making data available for substantiation of research which is nice way of seeing the Elector of the data available in support of the research papers and they had this real demand for persistent identifiers mechanism ah now they sort of do a number of persistent identifiers mechanisms out there I'm sure we've all played with handled net and so on in the time but you know we needed to make things simple and straightforward such as easy now remember what I was seeing about humanizing the whole process because we had control of the work through we could make it look as something that just happens which means people could actually go and request a digital object identifier and do the whole basic process without sort of you knew anything if you have to go to special website stick their fingers in the ER dance three times around the fire they simply won't do it so just hate doing that sort of thing so what I'm now going to do having spread the thing of it told you the message making things easy is I'm now going to hand over to a halt hi
everyone I'm Rahul I may be taking over the presentation from here as Doug mentioned you're trying to make the system of requesting do is as simple as possible so what we've done is once a record gets created a number of people have a look at it do a review of the information of the metadata in the record and all a user has to do is click on a button that says me do I the system does all the background processes all the checks the verification gets the DUI from the service updates the record it's as simple as that of course we have logs for all the requests and responses for reporting and auditing purposes so that's sort of the technical aspect of how we implement it the solution to make it as simple as possible our solution
can further expanded it's not perfect we have a long way to go to accommodate all user requirements one of them is the ability to version data sets the issue with versioning is that the dui's are minted at the collection level not at the inn at the other files within the collection level so if a user comes to us and says I'd like I've got an updated data set and I'd like to maintain ooh do I for it the entire collection needs to be duplicated the data are the old data as well as the new data needs to be uploaded to the new collection a new do I needs to be minted but this again while inconvenient is meets the requirements of minting do is making sure the do is point to the complete data set and also for the moment we have restricted the ability to meet DUI is only to system administrator's we do have the capability of allowing researchers and research offices to meet the device by by themselves moving on
just giving an example of what the screen looks like it's all a matter of simply clicking mint DUI a button on the right side which means do I to a collection and our implementation is open source we're using open source libraries as well the source code is available on key you