Open bryjbrown opened 8 years ago
Yes, I like the metadata approach, which would put the metadata in authorative control. I assume it would take the form of a date-encoded field.
MODS date-encoded field -> pcdmrights:rightsOverrideExpiration? MODS accessCondition field -> pcdmrights:rightsOverride?
I envision mapping the embargo date from for example, a Proquest ETD to MODS. The system would respect the metadata's specified embargo date.
From the Oct 14th user call of use cases:
So this bumping a super old issue but @bryjbrown did indeed make an embargoes module that lives at https://www.drupal.org/project/embargoes and was also captured within https://github.com/Islandora/documentation/issues/1161?
We (dgi) have a fork of this as well that we've been adding features to and maintaining: https://github.com/discoverygarden/embargoes.
@jordandukart, it was my understanding from Bryan that the module needs refactoring to use content entities instead of config entities. There was also an issue where embargoed items could be leaked through views. Has dgi been able to address either of those?
Can't speak to the content entity refactoring. However, that issue does indeed need to get addressed 💣 .
Another aspect to embargo notification to consider: notification to content owner/depositor in addition to notification to repository administrator when an embargo is set, changed, or lifted -- preferably with an option to send a warning that embargo will be lifted ahead of that date. (From Islandora 8 IR Delta doc
Glossary Used
Embargo Types
Examples:
Remarks: