-
Notifications
You must be signed in to change notification settings - Fork 0
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
restrict usage encumbrances #208
Comments
Will there be a new process for deleting catalog records then? Currently we assign the restrict usage encumbrance and then we can delete those records in the encumbrance. |
Mask record encumbrance isn't going anywhere and I would think is more appropriate anyway (as much as deleting a GUID can ever be 'appropriate'!!). If that's somehow problematic we could retain a no-action value, but the current one is clearly being used for what permits have become and that should be discouraged as much as possible. |
Unused and removed: |
Converted to permits: |
Help us understand your request (check below):
Describe what you're trying to do
Restrict usage encumbrances should not exist; permits are the proper place for all usage-guiding documentation. I'll move whatever's left under the encumbrance, which will hopefully be nothing, to permits/data loans in a couple weeks.
HELP!
The text was updated successfully, but these errors were encountered: