{"action":"created","issue":{"url":"https://api.github.com/repos/programminghistorian/jekyll/issues/64","repository_url":"https://api.github.com/repos/programminghistorian/jekyll","labels_url":"https://api.github.com/repos/programminghistorian/jekyll/issues/64/labels{/name}","comments_url":"https://api.github.com/repos/programminghistorian/jekyll/issues/64/comments","events_url":"https://api.github.com/repos/programminghistorian/jekyll/issues/64/events","html_url":"https://github.com/programminghistorian/jekyll/issues/64","id":52005737,"number":64,"title":"Look into getting DOI for Programming Historian releases","user":{"login":"wcaleb","id":1126864,"avatar_url":"https://avatars.githubusercontent.com/u/1126864?v=3","gravatar_id":"","url":"https://api.github.com/users/wcaleb","html_url":"https://github.com/wcaleb","followers_url":"https://api.github.com/users/wcaleb/followers","following_url":"https://api.github.com/users/wcaleb/following{/other_user}","gists_url":"https://api.github.com/users/wcaleb/gists{/gist_id}","starred_url":"https://api.github.com/users/wcaleb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wcaleb/subscriptions","organizations_url":"https://api.github.com/users/wcaleb/orgs","repos_url":"https://api.github.com/users/wcaleb/repos","events_url":"https://api.github.com/users/wcaleb/events{/privacy}","received_events_url":"https://api.github.com/users/wcaleb/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":19,"created_at":"2014-12-15T16:19:08Z","updated_at":"2016-12-10T11:51:16Z","closed_at":null,"body":"https://guides.github.com/activities/citable-code/\n"},"comment":{"url":"https://api.github.com/repos/programminghistorian/jekyll/issues/comments/266202693","html_url":"https://github.com/programminghistorian/jekyll/issues/64#issuecomment-266202693","issue_url":"https://api.github.com/repos/programminghistorian/jekyll/issues/64","id":266202693,"user":{"login":"acrymble","id":646647,"avatar_url":"https://avatars.githubusercontent.com/u/646647?v=3","gravatar_id":"","url":"https://api.github.com/users/acrymble","html_url":"https://github.com/acrymble","followers_url":"https://api.github.com/users/acrymble/followers","following_url":"https://api.github.com/users/acrymble/following{/other_user}","gists_url":"https://api.github.com/users/acrymble/gists{/gist_id}","starred_url":"https://api.github.com/users/acrymble/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/acrymble/subscriptions","organizations_url":"https://api.github.com/users/acrymble/orgs","repos_url":"https://api.github.com/users/acrymble/repos","events_url":"https://api.github.com/users/acrymble/events{/privacy}","received_events_url":"https://api.github.com/users/acrymble/received_events","type":"User","site_admin":false},"created_at":"2016-12-10T11:51:16Z","updated_at":"2016-12-10T11:51:16Z","body":"I attended an event on Persistent Identifiers yesterday at the British Library put on by the THOR project (https://project-thor.eu/). I spoke to Adam Farquhar (head of BL digital scholarship) about our needs, and he's provided some advice on DOIs for our lessons.\r\n\r\nIn particular he suggested we use an existing service (Figshare, Zenodo) to create and maintain the DOIs, and that each lesson and each subsequent version (after any updates at all) should have its own unique DOI.\r\n\r\nMimi Keshani from Figshare was at the event so I've approached her about whether or not Figshare can provide us with a zero-maintenance solution that would automatically mint new DOIs each time any file in our https://github.com/programminghistorian/jekyll/tree/gh-pages/lessons directory was updated, and to automatically hook that DOI back to our site. I'll report back when I hear from her."}}
{"actor":{"display_login":"acrymble"}}