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

Use Case: Prevent/manage orphaned media and files #1940

Open
rosiel opened this issue Oct 22, 2021 · 0 comments
Open

Use Case: Prevent/manage orphaned media and files #1940

rosiel opened this issue Oct 22, 2021 · 0 comments
Labels
Type: use case proposes a new feature or function for the software using user-first language.

Comments

@rosiel
Copy link
Member

rosiel commented Oct 22, 2021

Title (Goal) The title or goal of your use case
Primary Actor Collection Manager
Scope content management, metadata
Story As a collection manager, I need to understand if there are cases if/when media and metadata can be disconnected, and media orphaned, and I need safeguards to ensure this does not happen, or to clean up if it does happen.

Source: ICG Report:
"The disconnection between metadata records and associated media/files is very confusing from a UI/UX perspective. The connection between metadata node and media is only apparent when looking at the “Media of” field in the media’s metadata. There are separate lists for metadata nodes, media, and files. It seems like there is potential for the connection between metadata and media to get entirely broken if a metadata record is deleted, in which case media would be orphaned and easy to lose track of in the system. It’s not clear what the difference between the media and files lists are."

"Upload of digital content (media) is disconnected from the metadata webform. You must fill out and save the metadata form, then navigate to the Media tab to upload a file and select its “media use” to dictate derivative and display behaviors. We recommend incorporating the media upload into the webform to create a better connection between metadata and digital content and to ensure that metadata and media do not accidentally get orphaned from one another."

Related Tickets:

@amyrb amyrb added the Type: use case proposes a new feature or function for the software using user-first language. label Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: use case proposes a new feature or function for the software using user-first language.
Projects
Development

No branches or pull requests

2 participants