Zoom link: https://us02web.zoom.us/j/968367412

Host key can be found in the description of the TAG Slack channel.

Attending:

• Seth Shaw
• Willow Gillingham
• Rosie Le Faive
• Amy Blau
• Isabella Nikolaidis

Islandora Events

• Documentation Sprint June 20 - 29

Action Items

Meeting Minutes

• Amy joining as ICC liaison

• Documentation sprint June 20 - 29

  • Focused on Sandbox

• Rosie: From tech call - speaking of Drupal versions, Drupal 10 - there's not context module for that yet.

• Seth: They've had compatibility checkers in the past

  • There will be some depreciated function calls we'll need to replace with the new ones
  • Even 9 has deprecations that need to get cleaned up

• Willow: utility function for remaking all thumbnails

• Willow: Merging configurations and having something that was maybe updated on the site UI but then the updated module comes along, and its configuration overwrites what you had changed

  • no way to merge these 2 configs and have it be happy all the time? or is there?
  • Rosie: you have to manually go through and note what you want to keep and remake your changes unless there's way to do that programmatically
  • Seth: Both with islandora core and islandora default modules. If someone adds a new feature to something it doesn't necessarily make sense to write an update hook for it. Depends on the case - what is config that is going to have to be universal from site to site? Versus things people own on their own - content types, defaults.
  • Rosie's scoping document https://docs.google.com/document/d/1i4QGs6A5-hPiaGaq83g2QgHA0N3yuBkirP4l0x1V7Kg/edit#
  • We should be able to allow these sort of contributions

• Amy: +1 on a view that shows if various kinds of derivatives are missing! Thumbnails, OCR, etc. I want that!

• Rosie: Have a clearer versioning plan for islandora defaults / breaking up defaults

• We shouldn't be using semantic versioning to imply you can upgrade without breaking

• Seth: How much of defaults is configs or defaults?

• Seth: Defaults technically has no code except the one hook that is not necessary anymore (bc we use the jsonLD config).

• Rosie: Mirador needs to be refactored because it has code in the islandora defaults submodule.

• Seth: With Mirador, we could bring the code into core islandora and it would become a config module again.

• Rosie: Or we could make a Drupal module that's a formatter and anyone could use it?

  • field formatter for image fields

• Rosie: Creating a view is fine, but adding the view to islandora defaults is tricky

• Want to allow even people without a lot of experience to create PRs on islandora defaults

• Seth: A lower barrier to entry could be - here's the web interface for exporting your config. Download your copy and paste view export into the github web ui as a new branch/new file.

• Amy: A view that would show missing derivatives would be super helpful for those migrating

  • Amy to submit feature request
  • It's less important there be a view, it can be a script. Simply needs to be a process by which to figure out which are missing.
  • Seth has a script for this, runs in the back-end.

• Willow: Continuous integration and delivery

  • Is this something every institution is concerned with? It's a manual process for most, likely.
  • Github actions and GitLabs

• If you committed to branch, would reroll, rebuild the containers, and otherwise roll back -

  • You can do this in github actions or gitlab

• Rosie: Alexander commented that his PRs on the playbook aren't getting a lot of attention so is there ways to get more attention on the playbook? and ISLE?

  • condition of ISLE
  • Seth: Our developer pool has shrunk of late, and even those still around, their available hours for islandora stuff has decreased
    • Less energy for deployment

• Vendors are using their own versions of deployment

• Rosie: For things on islandora defaults - maybe getting rid of the requirement that individuals from diff institutions need to review, since developer pool is small - taking this to Tech Call