New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling DOIs for restricted records #178
Handling DOIs for restricted records #178
Comments
I think we want embargoed records to have published DOIs. Embargoed record metadata is public so there is no risk in sending metadata to DataCite. For our common embargo use case (files under review for a publication) you need the DOI to be registered so editors and reviewers can see that the DOI works. For records where access is "restricted", I think there is very limited risk in having a reserved DOI. Reserved DOIs don't show up in any public system and aren't even in the handle system. I guess it depends on your level of concern about restricting access to the metadata, since you are putting information on another system. But the access levels do match between The only state change I think we have to worry about is:
|
@tmorrell I see your point about embargoed, thanks. In terms of |
Add this test:
Among others, just not in the test suite at the moment... |
This issue was automatically marked as stale. |
People who want a DOI should be aware that the metadata is always public (even CC0?), so if you want your metadata to be hidden, don't get a DOI. |
This issue was automatically marked as stale. |
Going the other way round:
Said that... I'm sure I didn't thought through all corner cases. Additional notes:
|
This issue was automatically marked as stale. |
1 similar comment
This issue was automatically marked as stale. |
We don't want fully restricted records to register a DOI. If it is only a reserved DOI which is not findable it might be ok. |
Discussion from the coffee break at the InvenioRDM workshop with Werner, Nico, Martin, Karolina and Christoph. Proposed solution:
State changes:
|
Can someone shortly explain:
|
+1 on @chriz-uniba comments. Apart from that the rest of the approach seems good and we would like to see that happen at NU. We are willing to lend a hand. |
Datacite identify three states for registered metadata: publish | Triggers a state move from draft or registered to findable to Move from published to restricted we can use the "hide" state this will make metadata no longer available and findable via the Public API but they will stay viewable by members! |
* closes inveniosoftware/product-rdm#178 Co-authored-by: jrcastro2 <jrcastro9515@gmail.com>
* closes inveniosoftware/product-rdm#178 Co-authored-by: jrcastro2 <jrcastro9515@gmail.com>
* closes inveniosoftware/product-rdm#178 Co-authored-by: jrcastro2 <jrcastro9515@gmail.com>
* closes inveniosoftware/product-rdm#178 Co-authored-by: jrcastro2 <jrcastro9515@gmail.com>
* closes inveniosoftware/product-rdm#178 Co-authored-by: jrcastro2 <jrcastro9515@gmail.com>
* closes inveniosoftware/product-rdm#178 Co-authored-by: jrcastro2 <jrcastro9515@gmail.com>
A record might get a DOI reserved when creating a draft. However, then the access rules might change. The use cases are the following:
embargoed
.embargoed
. Can this happen, the record access cannot changed, when published?restricted
Related issues:
The text was updated successfully, but these errors were encountered: