Read only mode

[elynema]

Description

For large production sites (like IU) to migrate to 8.0 requires a Fedora 4 to Fedora 6 data migration. We anticipate that will take several days at IU, and we do not currently have a straightforward process to perform a delta update of records updated/created/deleted in the production system during the migration process.

It would be useful to have a "read only" mode we could enable in Avalon where users could access materials, but not make changes.

Actions that should be unavailable include:

• edit item (including structure, supplemental files, access/discovery, etc)
• publish / unpublish item
• create item
• delete item
• create collection
• delete collection
• edit collection metadata
• edit item access at the collection level
• create thumbnail/poster
• selected items actions: merge, move, update access control, publish / unpublish, delete

This feature can be scoped to apply to Fedora data and actions, and not things that rely on the database.

The custom "Read only administrator" configuration in the MDPI Internal Content Access Avalon instance can be used to provide a base for this functionality.

Done Looks Like

• flesh out list of actions that should be unavailable
• investigate difficulty in setting this up as a feature in the codebase
• read-only mode should hide action/edit buttons and show a relevant splash message if feasible

[elynema]

What about actions that don't impact Fedora, just the Avalon database?

• create / edit timeline
• create / edit playlist
• check out / return CDL items
• select / unselect items

[cjcolvar]

I think end-user actions like those should still be enabled since they only write to the database. Same for manage groups / users.

Maybe this is an "Administrative read-only" as opposed to a "Sitewide read-only" which would also include actions that involve the database.