{"action":"created","issue":{"url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/1166","repository_url":"https://api.github.com/repos/ManifoldScholar/manifold","labels_url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/1166/labels{/name}","comments_url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/1166/comments","events_url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/1166/events","html_url":"https://github.com/ManifoldScholar/manifold/issues/1166","id":339041833,"node_id":"MDU6SXNzdWUzMzkwNDE4MzM=","number":1166,"title":"Ambiguous Collection DOI Assignment","user":{"login":"tsmyre","id":25825222,"node_id":"MDQ6VXNlcjI1ODI1MjIy","avatar_url":"https://avatars1.githubusercontent.com/u/25825222?v=4","gravatar_id":"","url":"https://api.github.com/users/tsmyre","html_url":"https://github.com/tsmyre","followers_url":"https://api.github.com/users/tsmyre/followers","following_url":"https://api.github.com/users/tsmyre/following{/other_user}","gists_url":"https://api.github.com/users/tsmyre/gists{/gist_id}","starred_url":"https://api.github.com/users/tsmyre/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tsmyre/subscriptions","organizations_url":"https://api.github.com/users/tsmyre/orgs","repos_url":"https://api.github.com/users/tsmyre/repos","events_url":"https://api.github.com/users/tsmyre/events{/privacy}","received_events_url":"https://api.github.com/users/tsmyre/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-06T19:01:12Z","updated_at":"2018-07-09T20:24:08Z","closed_at":null,"author_association":"NONE","body":"When a DOI is entered into the `Resources DOI` field (under Project/Metadata/Identity), that DOI, in addition to being associated with the entire library of resources, also gets associated with each resource collection associated within that project, which is a bit misleading as the metadata tied to that number is specific to *all* the project resources and not just a subset of them (see [this project](https://demo.manifoldapp.org/project/google-document-sample) for an example).\r\n\r\nIf we want individual collections to have their own DOIs—and I'm not advocating for this—then there should be a separate field that could take a number specific to that particular collection.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/comments/403608327","html_url":"https://github.com/ManifoldScholar/manifold/issues/1166#issuecomment-403608327","issue_url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/1166","id":403608327,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMzYwODMyNw==","user":{"login":"zdavis","id":255909,"node_id":"MDQ6VXNlcjI1NTkwOQ==","avatar_url":"https://avatars3.githubusercontent.com/u/255909?v=4","gravatar_id":"","url":"https://api.github.com/users/zdavis","html_url":"https://github.com/zdavis","followers_url":"https://api.github.com/users/zdavis/followers","following_url":"https://api.github.com/users/zdavis/following{/other_user}","gists_url":"https://api.github.com/users/zdavis/gists{/gist_id}","starred_url":"https://api.github.com/users/zdavis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zdavis/subscriptions","organizations_url":"https://api.github.com/users/zdavis/orgs","repos_url":"https://api.github.com/users/zdavis/repos","events_url":"https://api.github.com/users/zdavis/events{/privacy}","received_events_url":"https://api.github.com/users/zdavis/received_events","type":"User","site_admin":false},"created_at":"2018-07-09T20:24:08Z","updated_at":"2018-07-09T20:24:08Z","author_association":"MEMBER","body":"I guess we need a decision on this to proceed. Should we in fact allow a DOI to be entered for each collection? If so, that's fine. Whether we do that or not, it sounds like we should not show the resources DOI on the collection view."}}
{"actor":{"display_login":"zdavis"}}