{"action":"created","issue":{"url":"https://api.github.com/repos/codemeta/codemeta/issues/167","repository_url":"https://api.github.com/repos/codemeta/codemeta","labels_url":"https://api.github.com/repos/codemeta/codemeta/issues/167/labels{/name}","comments_url":"https://api.github.com/repos/codemeta/codemeta/issues/167/comments","events_url":"https://api.github.com/repos/codemeta/codemeta/issues/167/events","html_url":"https://github.com/codemeta/codemeta/issues/167","id":268729803,"number":167,"title":"When using codemeta.json files, we need to give guidance on race conditions","user":{"login":"npch","id":1507151,"avatar_url":"https://avatars1.githubusercontent.com/u/1507151?v=4","gravatar_id":"","url":"https://api.github.com/users/npch","html_url":"https://github.com/npch","followers_url":"https://api.github.com/users/npch/followers","following_url":"https://api.github.com/users/npch/following{/other_user}","gists_url":"https://api.github.com/users/npch/gists{/gist_id}","starred_url":"https://api.github.com/users/npch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/npch/subscriptions","organizations_url":"https://api.github.com/users/npch/orgs","repos_url":"https://api.github.com/users/npch/repos","events_url":"https://api.github.com/users/npch/events{/privacy}","received_events_url":"https://api.github.com/users/npch/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-10-26T11:49:50Z","updated_at":"2017-10-30T16:46:40Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"If we consider the use case that codemeta.json files are used to represent metadata about a piece of scientific software, and that they reside in the root of the code repository, there are potential problems caused by the fact it is both describing the repository and part of the repository.\r\n\r\nThese include:\r\n- what is the dateModified? Conceptually, this should be the date of the last commit on the source code, however in updating the codemeta.json, you are also modifying the repository.\r\n- in generating a DOI for the software, if you cannot \"pre-reserve\" a DOI automatically, then the DOI included in the codemeta.json file will be out of sync.\r\n\r\nNoted at FORCE2017 Hackathon."},"comment":{"url":"https://api.github.com/repos/codemeta/codemeta/issues/comments/340507393","html_url":"https://github.com/codemeta/codemeta/issues/167#issuecomment-340507393","issue_url":"https://api.github.com/repos/codemeta/codemeta/issues/167","id":340507393,"user":{"login":"cboettig","id":222586,"avatar_url":"https://avatars3.githubusercontent.com/u/222586?v=4","gravatar_id":"","url":"https://api.github.com/users/cboettig","html_url":"https://github.com/cboettig","followers_url":"https://api.github.com/users/cboettig/followers","following_url":"https://api.github.com/users/cboettig/following{/other_user}","gists_url":"https://api.github.com/users/cboettig/gists{/gist_id}","starred_url":"https://api.github.com/users/cboettig/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cboettig/subscriptions","organizations_url":"https://api.github.com/users/cboettig/orgs","repos_url":"https://api.github.com/users/cboettig/repos","events_url":"https://api.github.com/users/cboettig/events{/privacy}","received_events_url":"https://api.github.com/users/cboettig/received_events","type":"User","site_admin":false},"created_at":"2017-10-30T16:46:40Z","updated_at":"2017-10-30T16:46:40Z","author_association":"OWNER","body":"@lnielsen Very nice; I should have realized I had to start a new upload to see the 'reserve doi' button.  It would be great to have this button appear when a user activates as GitHub repo in the Zenodo interface prior to creating a release, so that they can update the necessary metadata files in the usual order as you suggest without having to do a manual upload.  (Though I guess there will still be plenty of cases where a user forgets to update the DOI in the package metadata file before creating a new release; it's not clear to me how best to handle those inevitable conflicts).  \r\n\r\nIs the \"Reserve DOI\" option available from the API?  That would facilitate a scripted upload locally that could automate the dance of reserving DOI, adding to metadata, etc; either uploading directly to Zenodo or by tagging as a release in GitHub. "}}
{"actor":{"display_login":"cboettig"}}