2018-09-26 Hyrax Pals Meeting notes

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
10 min

Avalon 7 Development

By Connect - Avalon should be a workable gem that can allow media to play in Hyrax (last Ryan checked)

  • basic ingestion pipeline
  • Transcoding of streaming derivatives
  • Batch ingest in collaboration with WGBH, using NU's Donut as a model.
  • IIIF player integratrion
  • User study and UI/UX work
  • Docker and Local Install instructions
  • Structural Metadata Editor (avalon 6)


Maria (ha ha - Maria, you have to do this if I write it here)
  • Not a lot in the Avalon bundle repository - lot of work preparing for Avalon WS.
  • Two components/ plug-ins
    • SUpport for IIIF 3.0- chooose which viewer you want for a worktype
    • Plugin to use active encode thru Hydra derivatives - choice of encoding backends other than local FFMPEG. API to active encode.
      Use active encode if you configure Hyrax to do so. Using some external service to generate derivatives that don't live in your file system. Storing/ label file URL for derivatives - just doing as metadata rather than Fedora 4 or 5 method.
    • Attaching technical metadata to each derivative coming out fo active encode
    • Future work - dash for encodes so you can see output of filter
  • Batch Ingest with WGBH - mostly conceptual at this point - earnest post-Connect
    • Model that "read from batch" into batch items, can be read from a hash of attributes. Background job comes and pulls it out of db and does some work.
    • Dash from Donut - shows progress of batch "ingest" not egress
 

 Hyrax WG Update

Hyrax WG needs

 Tom

 Wrapped up 3rd sprint. Outstanding accessibility issues wrapped up. Bogged down by build processes. Feeling is that in re: to accessibility sprints where tickets were small - build was costing time. Effort put into switching to Circle CI. Document in draft for COnnect about Circle CI and GitLAB CICB offering and paying those services to support Hyrax builds. Cost - $3-5k/annual. Would make that back in terms of dev commits. Hopeful for a streamlined build.

Lost LaRita at end of Sprint 3 due to staffing issues. A bit short handed.

Starting a sprint next week - continue sprint cycles through holidays - working meetings at Connect, truncated/ interrupted sprint starting next week. Connect - get traction on Valkyrie stuff. Josh Gumm has been working on this behind the scenes - good input on WG Valkyrie work.

At Connect - Josh's work will be an entry point to conversation. Coming out of Connect with solid footing around what to do next and deploy WG against the problem of Valkyrizing Hyrax. Jess H has time in middle of day Wednesday for meeting.

With bulk of accessibility work done - at Partner - what's next for accessibility? Now is a good chance to come back and figure out longterm Accessibility requirements.


Permission WG final outputMaria

PAWG wrapped up - deliverables mostly use cases collected and document that summarizes the use cases and levels at which things happen. This WG wound up with only Larita as a dev. At connect - Jeremy will present where we are at Partners - entice other institutions to help with next phase of permissions. Goal: Technical design and architecture; prototype done. At IU - involved with next phase - need to find someone in community to chair the next phase group.

Permissions within Samvera as a point of interest. Known painpoint in Hyrax.

Check in with Emory and Princeton.


SIGAHR meeting at ConnectSteve

Steve's been putting together a tentative meeting schedule and posted the skeleton version of it in the SIGAHR Slack channel. Basic idea for the session—talk about where things are on the roadmap, talk about happening/impending work, including Avalon and how that fits in the roadmap, and then what it means to work on the roadmap for the coming year.

Mixed in—conversation about Valkyrie, and talking about the line of thought regarding core code cleanup vs focusing on feature development. What do we want Hyrax to do, as an endpoint? How do we get to that? Do we move to the modularization model?

Starting to think about what's next for the Hyrax roadmap. And folks on this call should be involved in this discussion. Input and comments are welcome on the agenda document. It would probably be best for an Avalon/Hyrax meetup to take place after the SIGAHR meeting.

We could meet up on Friday possibly. Early is better since some are leaving on afternoon flights.

Action items

  •