You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Documentation is needed for using MP3 files as source derivatives for the creation of new objects in an Avalon instance. Avalon generally assumes that files will be handled through its processing pipeline, but this effort is to provide support for cases in which pre-existing derivative files need to be used and served as the media assets for media objects in Avalon.
Documentation adapted to generic documentation applicable to Docker installs added to the Avalon wiki
Notes
Requirements
A way to create or update objects with the API
Derivative file locations are supplied with the API request to create the item
Copying derivative files into the correct location
Derivatives are stored in the appropriate directory for being served
Object is created via API request with derivative paths passed in for
Fields Supplied to New Objects
metadata (bib import from service)
media file paths (derivatives in Amazon S3 cloud storage, with S3 file paths)
technical metadata (mime type, width/height etc.)
is this available from the vendor?
is it uniform across all of the derivatives and can be applied the same for each object?
if not, it could be filled out via an ffprobe run
Technical Metadata values
derivativeFile: s3 path
bitrate
codec
mime type
quality (always set to "high" for single derivative items)
file size
We should tell them to create things in the S3 bucket in the structure that Avalon expects.
They can create a bucket in S3 with this structure:
avalon-demo-derivatives/UUID/quality-high/derivative_file.mp3
Description
Documentation is needed for using MP3 files as source derivatives for the creation of new objects in an Avalon instance. Avalon generally assumes that files will be handled through its processing pipeline, but this effort is to provide support for cases in which pre-existing derivative files need to be used and served as the media assets for media objects in Avalon.
Done Looks Like
Notes
Requirements
Fields Supplied to New Objects
Technical Metadata values
We should tell them to create things in the S3 bucket in the structure that Avalon expects.
They can create a bucket in S3 with this structure:
avalon-demo-derivatives/UUID/quality-high/derivative_file.mp3
Example object in Demo:
https://demo.avalonmediasystem.org/media_objects/t148fh39z
Example Request
POST https://demo.avalonmediasystem.org/media_objects.json
The text was updated successfully, but these errors were encountered: