December 9, 2020

Time/Place

This meeting is held virtually via Zoom, with an open channel for chatter on Slack. Anyone is welcome to join. Here is the info:

• Time: 1:00pm Eastern Standard Time US (UTC-5)
• Zoom link: https://zoom.us/j/97345581392
• Join us on the Slack Islandora 8 Channel https://islandora.slack.com/archives/CM5PPAV28

Attendees

• Danny Lamb
• Melissa Anez
• Willow Gillingham
• Kristina Spurgin
• Melissa Anez
• Debbie Flitner ⭐ 💪
• Eli Zoller
• Alan Stanley
• Jordan Dukart
• Mark Jordan
• Seth Shaw
• Bryan Brown
• Natkeeran
• Daniel Aitken
• Hertzel Armengol
• Alexander O'Neill
• Rosie Le Faive
• Adam Vessey

Agenda

1. Open Meeting still coming up next week on Tuesday
2. Drupal 9 Sprint Update: https://github.com/orgs/Islandora/projects/3
   1. hook_post_action, libraries, and carapace can't come along for the ride
   2. We can get rid of drupal-project!
3. Issue Roundup
   1. https://github.com/Islandora/documentation/issues/1728
   2. https://github.com/Islandora/documentation/issues/1736
   3. https://github.com/Islandora/documentation/issues/1481
4. PR Roundup
   1. Feel free to add any PRs you would like to see addressed
5. Feel free to add agenda items...

Minutes

1. Open Meeting next Tuesday
   1. Anyone can drop in and ask questions.
   2. Mark Jordan will do a demo of Islandora Workbench.
   3. ASU will demo their Islandora 8 sites.
   4. Dec 15th, 10:00 AM - 2:00 PM Eastern
2. Drupal 9 Sprint Update
   1. Danny has set up a github project to organize the sprint and illustrate progress.
   2. End goal is that the installer gives you Drupal 9 Islandora.
   3. Audit results - some modules will need to be removed
      1. So far nothing is a total blocker
      2. Hook_post_action - for multi-file media stuff, already have code that duplicates this that we can edit.
      3. Libraries - not used as much in D8 and there is no D9 version.
         1. We were using for OpenSeadragon but have set that to pull from a CDN so we no longer need this.
         2. Mirador and some others are probably already using a CDN or can be switched.
      4. Jordan and Nate found some code that will duplicate libraries functionality if something can't use a CDN - https://www.drupal.org/node/3099614
      5. Carapace - Base theme (Adaptive Theme) isn’t going to D9. Many elements are in core now such as column wrangling, layout builder, etc.
         1. ICC is going to have discuss this and make a decision on Bartik vs Olivero vs custom.
         2. Most people don't use the default theme for anything other than a quick demo so we should probably not spend a ton of time on a custom theme.
      6. We can get rid of drupal-project - we were using this to pin down a Drupal core version
         1. Now we can just use drupal-recommended-project and specify a version number. We can set that to auto-grab the version we want in the playbook or Docker config.
         2. Need to update Travis scripts and then we can get rid of drupal-project.
   4. Should be able to build a D9 Islandora (still needs work but will build). Need to change stability to dev in composer.json to complete build.
3. Shoutout to DGI and ASU for people helping with this sprint.
4. Issue Roundup
   1. https://github.com/Islandora/documentation/issues/1728
      1. Person would like some conditional form elements baked into the form
      2. There is a module that add conditional fields.
      3. Might also be another issue about letting people pick conditional fields and/or changing labels - maybe duplicating some functionality that was in I7. Issue 1659.
      4. This also helps with content modeling and UX. - Different fields per taxonomy (e.g.) to add a URI or string or whatever if desired.
   2. https://github.com/Islandora/documentation/issues/1736
      1. Can offload some documentation by linking out to Drupal and github documentation where it’s useful rather than duplicating or rewriting the same thing.
      2. Try to make sure documentation examples are relevant to Islandora behavior (e.g. Paragraph example of a slideshow when it's more useful to us for field grouping).
      3. Add to DIG agenda for further discussion.
   3. https://github.com/Islandora/documentation/issues/1481
      1. When you create media via REST interface, you get a large number of errors.
      2. These errors seem to be due to a transaction we created in a custom media controller.
      3. Drupal has a media controller now so maybe we can use that one rather than a custom controller.
         1. Would that resolve these issues?
         2. Refactoring effort?
      4. Expecting different things coming back from microservices, need some additional parameters to be passed. Might be able to add some config to make it more general.
      5. Mark suggests he make the change in Workbench to use the Drupal controller and keep the existing customized code in Islandora since there are so many things that depend on it. (Update: here's the Workbench issue to do this.)
         1. Nat will help
      6. There are basically 3 use cases for creating derivatives - if we formalize these then we can create code for each rather than having 1 chunk do everything
5. PR Roundup - some PRs are happening due to the sprint but no one has anything in particular they want to push.
6. How are we handling getting new features for islandora_defaults into an existing site.
   1. Rosie has a doc PR to document new features / create a change log.
      1. Please give Rosie examples of good change logs if you can.
   2. In which case, there’s a lot of things in islandora_defaults that probably should be separate modules so you don’t have to have it installed to use e.g Mirador.
   3. Split out foundation code that most users need, separate section that has the stuff in it where you can make choices per your site needs.
   4. Documentation for each kind of feature/workflow - here is what to expect, here is where you get the module, here is how to set up the config.
   5. Return of solution packs - code goes into the pack and the config moves to documentation.