tator
tator copied to clipboard
Height / Width attributes on media objects are confusing
Media level height/width attributes are confusing when both archival and streaming versions of the media file are present at multiple resolutions.
- Some convention, other than 'first uploaded resolution file' might be easier for the end user.
- Highest resolution available (1)
- Highest streaming resolution available (2)
- Some care has to be given as those attributes are used in a lot of places. Likely under assumption (2) or (1) as by practice one or both tend to be true.
- Some thought can be given to whether the width/height are populated on POST/PATCH/etc. or dynamically calculated on GET.
- Depending on that decision point, retroactive modification of previously stored entities will need patching.