-
Notifications
You must be signed in to change notification settings - Fork 4
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
Ability to embargo an object until a specific date (with auto-release) #44
Comments
do you think we could use https://www.drupal.org/project/scheduler? it provides helpful hooks that i think we might be able to advantage of? |
Add a field on the media for Embargo Date. Add a filter on the EVA view for OSD, PDFjs, etc that is less than today. |
Bryan Brown brought up some good points about what if an embargo is added later and someone already had the link to the file. I think we should tie embargoing in more with Drupal's notion of published/unpublished to accommodate that. We may need an additional module like https://www.drupal.org/project/scheduler or https://www.drupal.org/project/scheduled_publish to facilitate that. I tested scheduled_publish and it works with workflow to be able to add a date/time for content to move from one workflow state to another so I prototyped a concept where there is an Embargo workflow with two states Embargoed or Published and it is attached to all media types with a scheduled publish field on those media types that would allow embargo dates to be set. They would be "released" via cron. This would allow the node to still be accessible but not the media. It may require development of an additional view for display selected data about unpublished/embargoed objects. |
we could also look at the work done here: https://github.com/fsulib/embargoes |
Question about full text searching and embargoes - do you want embargoed items to be full text searchable (with text snippet previews)?
The text was updated successfully, but these errors were encountered: