-
Notifications
You must be signed in to change notification settings - Fork 71
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
Use Case - Support for capturing licensing and deposit agreements #1013
Comments
@MarcusBarnes excellent use case. I'd like to add that we need a way to control access to these sorts of documents. Perhaps #823 is relevant here, since these documents would likely be tagged with "License Agreement" or similar tags from the Media Use vocabulary (although https://pcdm.org/2015/05/12/use doesn't have a term for this). Not sure what a suitable vocabulary for identifying licenses and other administrative documents is, but one must exist. |
Thanks @mjordan for the feedback. It's likely that we'll need to split this into separate use-cases, one for license agreements and one for deposit agreements, but I wanted to get a conversation going so that others can chime in with their specific needs. |
For the record, I installed and enabled the Permissions by Term module and its submodule Permissions by Entity (which is needed to provide access control by term to Media) and they appear to work as expected. By configuring specific taxonomy terms, I was able to restrict access to authenticated users to the node, media (using direct URL to media) and the media's file (using direct URL to file). I'll post this over at #823 as well. |
Possibly useful properties: |
We are looking to have a deposit agreement that each user would need to agree to one time before adding an item. I don't think that would be solved by the Permissions by Term module. |
@elizoller you're right, that's more of a workflow issue, not a simple access restriction issue. |
@elizoller I think the easiest way to do that would be to revoke the permissions to create content for new users, and only give it to them once they've made the agreement. You could pretty quickly whip up a webform and give it a handler that adds permissions/roles to the user that submits the agreement. |
thanks @dannylamb |
The text was updated successfully, but these errors were encountered: