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

Add MP3 File Format at an acceptable/readable format to Figgy. #6645

Open
1 of 5 tasks
kelea99 opened this issue Mar 5, 2025 · 0 comments
Open
1 of 5 tasks

Add MP3 File Format at an acceptable/readable format to Figgy. #6645

kelea99 opened this issue Mar 5, 2025 · 0 comments

Comments

@kelea99
Copy link
Contributor

kelea99 commented Mar 5, 2025

Summary (Product Owner)

Requested twice this week by users in SC and EAL for their sound recordings (one from George Blood). Folks are wanting to use an MP3 as the access file in figgy. @tventimi most recently for 2 spoken-word mp3 collections. It would be helpful to have the option to add this format to figgy as well.

User Story (Product Owner, when applicable)

As a [persona], I want to [describe intent], so that [explain the big problem you are trying to solve and its benefit]

As a figgy ingester working with sound files from vendors, I would like to have the option to ingest an MP3 file as the primary access file to figgy so that i do not have to convert files already in hand from MP3 to WAV.

Impact (Product Owner)

Please include hard deadlines, if the exhibit is part of an event, the issue is stopping work, etc.
There is no hard deadline, but in speaking with DLS this sounds like a relatively light life, code-wise.

Priority recommendation (Product Owner)

  • asap
  • within the next 3 weeks
  • PO will prioritize

Sudden Priority Justification (Product Owner)

Required if "asap" or "within the next 3 weeks" is checked. Add "Sudden Priority" and "dls-work-cycle" labels
users would be able to ingest materials that they already have in hand, versus converting to WAV if users need immediate access.

Implementation Notes

To be filled out by DLS.

Acceptance Criteria

To be filled out by DLS.Some requirements to consider, including:

  • The UI implemented for this issue meets accessibility requirements
  • New functionality is documented

First Step

To be filled out by DLS.

Expected behavior (Product Owner)

Actual behavior (Product Owner)

Steps to reproduce behavior (Product Owner)

Screenshots (Product Owner)

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

No branches or pull requests

1 participant