Page Comparison

How to connect: https://psu.zoom.us/j/613720745 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)

...

1. Samvera Dev Congress, Winter 2020 (Solar Vortex) report out (tamsin woo)
   1. Developer congress last week in San Diego
   2. Some work on refactoring Jobs to support; tickets open for this
   3. Question about written summary; we think one went out via emails–will confirm.
   4. Are there issue tags or project boards?
      1. issues are under-organized across hyrax in general, owing in part to lack of PO
      2. we are mainly using the `Wings` tag for wings adapter tickets, and trying to encourage treating valkyrie support as normal hyrax development
2. Hyrax Publisher (`Dry::Events`) (tamsin woo )
   1. Need community feedback on event publishing.
      1. Working on normalizing callback/event publishing strategy strategy with Dry::Events
      2. it's desirable to plan and document this strategy very clearly, so we're soliciting early feedback.
   2. Thinking about two community virtual sessions:
      1. Dive Into Hyrax Pub/Sub
      2. Events design session
   3. Folks supported this plan, tamsin woo to schedule.
3. Hydra-Head 11 and Rails 6/Blacklight 7 (Chris Colvard (Deactivated))
   1. There is a Hyrax release blocker issue that depends on a change in HH that will require a major release
   2. We also need to add Rails 6 support but this requires a newer BL and blacklight-access_controls which I believe will require a major release.
   3. Release 11 now and follow up with 12 later? OR try to get 11 released with Rails 6/BL 7 support?
      1. There is work in Hydra Head already that fixes an issue with permissions https://github.com/samvera/hydra-head/pull/501
      2. There is also a need to add support for newer versions of blacklight; is it a good idea to try to bundle these changes and reduce the number of major releases.
4. FileSet and FileMetadata in Hyrax with valkyrie (Lynette Raylewith Trey Pendragon)

   1. Two approaches for saving filesets and metadata objects for files.

      1. First is to store ids in FileSets, Hyrax does this now

      2. Second is to nest FileMetadata objects; Figgy does this

      3. Figgy had this design conversation early on, there are multiple factors

         1. Simplifies query and access

         2. Delete FileSet deletes all FileMetadata instead of having to find them and delete each

         3. In Figgy FileSets have optimistic locking; that seems important for running parallel characterization jobs, for example

      4. Question about impact on access to FileMetadata, do i need to have all FileMetadata objects in hand to change one?

         1. Yes.
         2. This isn't an issue with postgres, where access is one query.
         3. However, this is likely a problem for Wings where we'd have to query the file metadata nodes individually

   2. Next steps: Continue discussion in slack; maybe schedule a call.

      
      

      Hyrax now:  attribute :file_ids, Valkyrie::Types::Array.of(Valkyrie::Types::ID) # id for FileMetadata resources

      Figgy: attribute :file_metadata, Valkyrie::Types::Set.of(FileMetadata.optional)