Page Comparison

• Tom - handed primary faciltator duties to Julie Allinson - punting a draft of a charter - Doodle poll and then make it happen
  • WGBH talking to us about their use of Batch ingest -
  • Carrick is on the Batch work for Hyrax -
• Hyrax Batch Import WG
  • May want to have MBK jump in - better understanding of use cases and state of the art
  • Could be about 4 versions of the State of the Art

 Becasue of AV type that Avalon cares about - Indiana and NU worked on AV worktype for Hyrax. Get worktype tied to player. IIIF Manifest generation. Metadata connected.

Dealing with multipart fields. Store all of the multivalued/ multipart fields as a JSON blob in one statement. Other thing with the worktype - our descriptive metadata isn't tied to media. Does a betteer job than generic metadata.

Reviewing generic worktype - push some of our opinion of metadata into Hyrax core via Generic worktype.

Happening in Metadata IG sponsoring a session for those interested - hash out what's there, what should be there. Descriptive for generic work. Offering use cases. Some of what we like in media we're seeing fi we can push to Generic.

Part of the Permission and Analysis WG - PAWG. Question of whether "owner" role currently in Hyrax - what is an owner? What's special about that role? Permissions - list of actiosn assigned to roles - make sure list of actions is complete per role. Discussion was all about - are we covering what people think of when they think of an owner.

Different perspectives from people with different backgrounds. Conclusion: We do cover everything in the Matrix of actions. Everything can be configured if we do a configurable permissions module.

Whomever creates a work is an Owner - an immutable role. PAWG is leaning toward a work should have a primary contact. A descriptive field for Primary contact. Who is the creator. Those are just descriptive fields.

Our ongoing work on AVALON 7 has been to get IIIF 3.0 support in our Hyrax app. Play AV w/ structure within a file. Rolling things back to Hyrax core. Would like Tom's feedback - 2.1 and 3 are here and coming. Don't want it internal to Avalon for too long. Making IIIF viewer configurable (assumed Universal Viewer right now) - Hyrax app content negotiation - presentation 2 and 3 manifests.

Tom - while spec is still in draft - look at what's in our code - prototype - analysis in Hyrax to make it easier to maintain on our end. Get IIIF 3 support while spec is still in draft. Treat as a prototype - simple actions taken on application side. If we have something we can demo now - we should start now on that. Doing work on IIF stuff up front, we have a workshop planned for Samvera Connect about demoing how to enable IIIF video and rich video playback in any Hyrax app.

AI: Write a straightforward story for Hyrax about how to implement IIIF in Hyrax.