...
We are focusing on digitized VHS (fairly low-resolution source material)
It’s okay to use “public derivatives” – where it’s on public S3 buckets where even if our app isn’t pointing at it, if someone knew the URL they could download it directly, for instance even if it’s not “published”. (the URLs are non-obvious though). Everything in this phase is intended to be public available, if it’s unpublished it’s just in process.
...
All hagley videos: https://digital.hagley.org/islandora/search/%2A%3A%2A?f%5B0%5D=mods_typeOfResource_ms%3A%22moving%20image%22
A 30-minute example (they may not have longer videos?) https://digital.hagley.org/RexKaiserTape2-1?solr_nav%5Bid%5D=a9f4d270738648345247&solr_nav%5Bpage%5D=0&solr_nav%5Boffset%5D=17
like the basic design (just video at the top, metadata at the bottom)
Hagley has a field for information about the digitized file (“digitization note”); we should have somewhere to put this metadata
Institutions with video content on YouTube/Vimeo
University of Westminster Archiveshttps://www.youtube.com/channel/UCz_r1WjEUNIEY7RqegSSQWQ
decision made mostly so they can reach a wider audience, copyright not a factor (but will be for an upcoming project, for which they may move way from YouTube)
London Screen Archive https://www.youtube.com/user/LondonsScreenArchive/featured
Current VHS digitization workflow:
...