2024-08-12 Avalon User Roundtable Meeting
Meeting Time
Monday, August 12 at 1 PM Eastern
Attendees
Jon Cameron (Indiana University)
Emily Lynema (Indiana University)
Kee-Young Moon (UMD)
John Merritt - U of Louisville Libraries (Systems)
Zoom Link
https://iu.zoom.us/j/84620830059?pwd=bWo3R081M3BtaytFMjZnS0FzQkd2dz09
Agenda/Notes
Avalon 7.8 Release
https://github.com/avalonmediasystem/avalon/releases/tag/v7.8
Transcript text is searched in the index.
IIIF content search supports search within the Transcript component
By default, no limit on file size for web file upload
Basic configuration for download of derivatives
Can specify language for transcripts, as well as captions
Timestamp in Solr index now only updated when the descriptive metadata is changed - IU uses this to harvest updated records through the Atom feed for updating in an external system
Bibliographic ID used to import metadata to record being saved to the Avalon record
API support to upload / edit / delete supplemental files (captions, transcripts, other supplemental files)
Batch ingest can support upload of captions, transcripts, and other supplemental files
Questions
UMD: glad to see that hasCaption and hasTranscript facet is limited to collection staff.
UMD: results for speech-to-text? They are evaluating Whisper and AWS Transcribe as well.
ai4lam speech to text working group: Charter: https://docs.google.com/document/d/1MZr0JfylHmkcBK9K-J7A4KKw-f_SyrwqW4T1AMqoWfk/edit#heading=h.j6j2bxd2c0zj
UMD: what metadata is being searched in the big search box?
all descriptive metadata, structural metadata, and transcripts
Should Date continue to be a required metadata field?
currently require Title and Date by default
no particular feedback from UMD / Louisville yet about Publication Date. Might be using this as date the item is published in Avalon.
Next month:
discuss use cases for batch editing of records in Avalon
summation of survey
Future agenda items?
Potential conversation around upgrade process for institutions that have been using Avalon for awhile (how to handle code customizations, etc.)