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

Provide default required metadata in IIIF manifest for newly uploaded media #6001

Closed
5 of 6 tasks
elynema opened this issue Aug 21, 2024 · 5 comments
Closed
5 of 6 tasks
Assignees

Comments

@elynema
Copy link
Contributor

elynema commented Aug 21, 2024

Description

When a file is uploaded into Avalon from the web, and the user tries to preview the page before adding any descriptive metadata, Ramp gives an error:

image.png

This error is due to Ramp was missing manifest.label which I'm guessing is Title in the manifest's metadata which wasn't in the manifest. The labels in the structure were also null.

Prior to 7.8, when a media file had been uploaded, but no metadata added, the preview page would have a default title and date displaying. These default values did not populate into the Resource Description section when editing the item.

image.png

Questions

  • Should users be able to upload multiple files before creating a title/date? Even pre 7.8 release on Archivo does not seem to allow this.

Done Looks Like

  • the IIIF manifest generated by Avalon for a media item without a title and/or date should provide a default auto-generated value
  • For title, the value should be the media item identifier (fedora NOID)
  • For date, the default value should be "Date not provided"
  • These default values should not be populated into the metadata for the item in Avalon
  • Section files should display with a label of the filename, which should be stored (or the fedora id-prepended to the filename if that is the value already stored)
@masaball
Copy link
Contributor

masaball commented Sep 11, 2024

As long as a user has not moved past the file upload screen they can upload multiple files. The validations on the media object are only activated after the file upload step has been "completed", so when the user has hit the "Continue" button and moved to the resource description page.

We could potentially expand that so users can always attach more files but that would take some thought on how to do the rework and should be its own ticket if we want to look into it.

@elynema
Copy link
Contributor Author

elynema commented Nov 7, 2024

@masaball I see one potential tweak here. After uploading a single item, there is a section with a blank title. After uploading 2 items, the file names populate the sections. Is it possible to populate the section title when the first item is uploaded?

image.png

image.png

@joncameron
Copy link
Contributor

I still see an empty label for the first section of a new blank item on avalon-dev (https://avalon-dev.dlib.indiana.edu/media_objects/z316q162x):
Screenshot 2024-11-12 at 4 08 25 PM
@masaball could you take a look?

@masaball
Copy link
Contributor

masaball commented Nov 12, 2024

The fallback is to use the MediaObject title, which blank new item lacks... Could add a secondary fallback to use the media object or master file id?

@joncameron
Copy link
Contributor

ID would work, but ideally I'd like to have the fallback be the filename of the media for the section.

I've created #6109 for adding the original filename as a separate masterfile property, and added a todo for adding that value to manifest generation when section label isn't present. I think this issue can be closed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants