Skip to content
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

expand the EmbargoManager interface to handle releasing embargos #4305

Merged
merged 3 commits into from
May 12, 2020

Conversation

no-reply
Copy link
Contributor

@no-reply no-reply commented May 7, 2020

for Valkyrie models, we provide Hyrax::EmbargoManager to make the embargo
lifecycle easy to work with. to date, this has only supported applying
embargoes. this adds the ability to release an embargo after its period has expired.

a concept of 'enforcement' is added, represented by #enforced?. this addresses
the issue of embargoes which are not current (their period is past) but have not
yet been released.

the terminology used by the EmbargoManager is documented.

see also: samvera/hydra-head#511.

@samvera/hyrax-code-reviewers

tom johnson added 2 commits May 7, 2020 16:10
for Valkyrie models, we provide `Hyrax::EmbargoManager` to make the embargo
lifecycle easy to work with. to date, this has only supported applying
embargoes. this adds the ability to release an embargo after its period has expired.

a concept of 'enforcement' is added, represented by `#enforced?`. this addresses
the issue of embargoes which are not current (their period is past) but have not
yet been released.

the terminology used by the `EmbargoManager` is documented.

see also: samvera/hydra-head#511.
`LeaseManager` is substantially similar to `EmbargoManager`, and got in without
tests, with the idea that a refactor might quickly take place. it didn't and at
this point it needs a test harness if that's ever going to happen.

in the meanwhile. there are features we want to add to cover the remainder of
the lifecycle.
@no-reply no-reply force-pushed the embargo-manager-expansion branch from dd75bf7 to a43faee Compare May 7, 2020 23:10
@no-reply no-reply force-pushed the embargo-manager-expansion branch from 146743a to 4e868ba Compare May 7, 2020 23:46
Copy link
Contributor

@bkeese bkeese left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@no-reply no-reply merged commit 8d8210e into master May 12, 2020
@no-reply no-reply deleted the embargo-manager-expansion branch May 13, 2020 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants