Hi Mick,



I would not recommend you create a local DOI where the content is actually on GitHub unless you are able to make sure Glasgow has a copy you can point back to at a later date (for the scenario you mention where the copy on GitHub could get removed). This is also risky for the fact that you need to make sure you're pointing to the right version, fork etc and taking new copies of any new releases created - it looks like GitHub and Zenodo manage this versioning by automatic archiving and allocation of a new DOI for new releases. You could watch the repository to look out for new releases to trigger you to do this manually, but if you get more than a handful of researchers doing this I suspect it will become unmanageable.



Aside from this I'm afraid it probably wont fall within the authority you need to mint DOIs for content (unless the DOI was actually for a copy you had taken and were storing, rather than for the Github-held files).



If they did create the DOI through Github by sending the code to be archived by Zenodo, as long as the researcher lets you know the DOI they get, you can use DataCite search to extract the metadata for that Zenodo DOI which you could then put into your registry - e.g.  http://search.datacite.org/ui#ui?&q=10.5281%252FZENODO.10503 the results can be retrieved in XML, CSV, JSON and OAIPMH - see the links in the footer of this search results page.



Thanks, Rachael.





Rachael Kotarski

Data Services and Content Lead

The British Library, 96 Euston Road, London NW1 2DB

[log in to unmask]

http://bl.uk/datasets  |  http://datacite.org







-----Original Message-----

From: Research Data Management discussion list [mailto:[log in to unmask]] On Behalf Of Michael Eadie

Sent: 15 June 2015 10:52

To: [log in to unmask]

Subject: Minting a DOI through GitHub



Hi all



I was wondering if anyone has come across DOI minting through GitHub.



https://guides.github.com/activities/citable-code/



We have had contact from a researcher who is planning to use this.



My initial thought is that it would be better for us to mint the DOI locally by creating an entry in our registry which provides link to the code in GitHub.  Although there are obvious draw-backs to this, for example if the researcher deletes the code repository in future.



Would anyone have a different approach?



Cheers,

Mick



--

Mick Eadie

Research Data Management Officer

University of Glasgow



Tel: +44 (0) 141 330 6294



http://researchdata.gla.ac.uk | www.glasgow.ac.uk/services/datamanagement/





******************************************************************************************************************

Experience the British Library online at www.bl.uk<http://www.bl.uk/>

The British Library’s latest Annual Report and Accounts : www.bl.uk/aboutus/annrep/index.html<http://www.bl.uk/aboutus/annrep/index.html>

Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook<http://www.bl.uk/adoptabook>

The Library's St Pancras site is WiFi - enabled

*****************************************************************************************************************

The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the [log in to unmask]<mailto:[log in to unmask]> : The contents of this e-mail must not be disclosed or copied without the sender's consent.

The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author.

*****************************************************************************************************************

Think before you print