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

Require certain fields on file upload #1129

Open
BobJonkman opened this issue Dec 9, 2020 · 2 comments
Open

Require certain fields on file upload #1129

BobJonkman opened this issue Dec 9, 2020 · 2 comments
Labels
is: feature-request status: pinned This issue or pull request won't stale

Comments

@BobJonkman
Copy link

Is your feature request related to a problem? Please describe.

When uploading a music track (Track Type=MUS) we require the "Title", "Artist", and "Genre" fields to be filled in. When uploading a pre-recorded show (Track Type=PRS) we also require "Album" for the show name, but don't need "Genre". There are similar requirements for other track types, eg. Interview, StationID, PSA, &c.

Describe the solution you'd like

To achieve this, I would like that before a file is uploaded, rthe "Track Type" selector must be selected (ie. no Track Type pre-selected), so that uploaders must choose Track Type every time they upload a new set of files. In settings, there would be a UI to associate required ID3 attributes for each Track Type (maybe a full table of checkboxes for Track Type by ID3 attribute, maybe a Track Type selector which shows a list of ID3 attributes with a checkbox for each). After a set of files is uploaded, if the required ID3 attributes are missing from an uploaded file it gets displayed in the usual track edit window with an error message and the appropriate missing ID3 field highlighted.

Describe alternatives you've considered

Right now we're depending on training and documentation to achieve this. But our stations is all volunteer, and compliance is low, leaving it to the Digital Librarian (me!) to go back and fix all the uploaded tracks.

Additional context
Add any other context or screenshots about the feature request here.

@stale
Copy link

stale bot commented Jun 11, 2021

This issue has been automatically marked as stale because it has not had activity in the last 5 months. It will be closed if no activity occurs in the next month.
Please chat to us on discourse or ask for help on our chat if you have any questions or need further support with getting this issue resolved.
You may also label an issue as pinned if you would like to make sure that it does not get closed by this bot.

@stale stale bot added the status: stalled This issue or pull request is stalled label Jun 11, 2021
@stale
Copy link

stale bot commented Jul 21, 2021

This issue has been automatically closed after is was marked as stale and did not receive any further inputs.
Feel free to let us know on discourse or ask for help on our chat if you feel this issue should not have been closed.
Thank you for your contributions.

@stale stale bot closed this as completed Jul 21, 2021
@jooola jooola reopened this Mar 3, 2022
@stale stale bot removed the status: stalled This issue or pull request is stalled label Mar 3, 2022
@jooola jooola added the status: pinned This issue or pull request won't stale label Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is: feature-request status: pinned This issue or pull request won't stale
Projects
None yet
Development

No branches or pull requests

2 participants