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

Store Original Filename for Section in a Separate Field #6109

Open
4 tasks
joncameron opened this issue Nov 11, 2024 · 2 comments
Open
4 tasks

Store Original Filename for Section in a Separate Field #6109

joncameron opened this issue Nov 11, 2024 · 2 comments

Comments

@joncameron
Copy link
Contributor

joncameron commented Nov 11, 2024

Description

If a section title is manually entered then we use that for section name on the item page; otherwise the file location is used. file_location is stored as the full path or URI to the location of the source media file. To get a better decoupling between these and avoid having to do extra string parsing, we should store original filename in a separate field.

Done Looks Like

  • original_filename added to masterfile properties
  • original_filename contains just the filename of the source media
  • set original_filename as the section label default when generating the IIIF manifest for the item
  • backfill as needed (as rake task or script to populate the field)
@joncameron
Copy link
Contributor Author

joncameron commented Nov 20, 2024

Should this default label value populated by the original_filename field be indexed into the record for ease of searching?

Section label is being added to the "all text" solr field; this value could be added to that. If the filename isn't displayed anywhere, do we want it searchable?

What do we want to display on the Manage Files page? How to present file name, section label, and filename+fedora ID?

@joncameron Create a new issue for presentation of filenames on the Manage Files page.

@joncameron
Copy link
Contributor Author

See #5521 as well.

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

1 participant