-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Request - Make it easier to retrieve media #8519
Comments
Before we get into the technical details (ie Dusty) please articulate or give examples of what you are trying to do? Why do you need to do this? what are you ultimately trying to accomplish? (I'm just saving Dusty the effort of asking the question too!) Does "easier to retrieve media" mean download the media files too? And in what context? I will guarantee once we make it easy for anyone to download all your audio files then we will also get complaints about piracy. both your requests are interconnected (probably) and both cant be addressed without the context. This might be better to be a discussion before any technical considerations. so let me know how you want to proceed. Maybe the media committee should meet to discuss |
Yes, the media committee needs to discuss but with @dustymc as we've already met and discussed some of this and need technical discussion of what's possible or not.
Example: Search 'Media Label Value' contains 'MVZ' and 'Created by agent' contains 'groth' - there are 2,277 media files.
The media metadata that get downloaded are all mushed into one column and impossible to interpret/parse. We need the data downloaded in separate columns, comparable to the media bulkloader. Example: Here's what a couple of records look like in the download (search Catalog Records for 'MVZ:Bird' and media = 'audio' and agent contains 'groth': One one media file for a record: More than one media file for a record: Here's another example where there are multiple images for a record: @ebraker has some good examples too. That is very difficult to interpret or parse, even for Arctos operators who know the media metadata fields, and impossible for a public user interested in our media. And it gets worse the more media files you have linked to a record. We need a better way of downloading and displaying the metadata. Downloading the actual media is a separate issue, let's first figure out a way to better download our media metadata. |
ok so really this is about parsing the JSON into friendly tables. (again wasnt clear from the request!) Have you already discussed what the desired table should look like? |
It's about that plus not having the 500 record limit. We discussed having it look like the media bulkloader, but are open to suggestions. |
Yes, to echo Carla, the request is two-parted:
|
Describe what you're trying to do
This issue is extracted from a broader one with an overall goal of making it easier to retrieve media and metadata from Arctos. Two specific requests based on discussions last month in the Media Committee:
Let's plan to discuss this at the next meeting when @dustymc can attend.
The text was updated successfully, but these errors were encountered: