-
Notifications
You must be signed in to change notification settings - Fork 70
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
AuthZ for Preservation: Ensure no one person has write access to all copies. #414
Comments
It would be helpful to flesh this out a lot more. Please expand on the level, and what layers of the stack, looking specifically at the gap between Fedora and CLAW where this would be required. |
I'm sorry. I know nothing about standards for digital preservation. I tried to include a disclaimer that this is not necessarily CLAW related, but likely has more to do with the implementation of good backup policies and strategic content duplication. My goal in including this was to bring the use cases that were brought forward in the discussion group to the appropriate venue. Please close this ticket if this is unacceptable. |
@rosiel what discussion group? |
So no admin user, then? Or just block admin user from having admin privileges, thus rendering it not admin? |
From here: https://groups.google.com/forum/#!topic/islandora/YGBMUU4OSM8 As mentioned it was "a challenging food for thought" requirement. We've always managed one single copy of an archival object, maybe this points out a use case where multiple would be worthwhile? |
I think this would be an excellent opportunity for the group to articulate where they would like to see the functionality for the management of multiple copies of an archival object to reside; Drupal, Fedora, somewhere else? |
Maybe I'm missing something, but this seems like a staffing/practice problem? Without two systems administrators, how would software solve this problem? |
A "a challenging, food for thought-type requirement" from Brad, as worded in The NDSA Levels of Digital Preservation, Level 4:
Source: Page 3, Table 1, Row 2 (File Fixity and Data Integrity), Level 4 definition:
http://www.digitalpreservation.gov/documents/NDSA_Levels_Archiving_2013.pdf
This is a "use case" that might involve other system aspects, such as the backups and (possibly) where else an object has been duplicated.
The text was updated successfully, but these errors were encountered: