January 15, 2020

Time/Place

This meeting is held in Zoom. Anyone is welcome to join. Here is the info:

• Time: 1:00pm Eastern Standard Time US (UTC-5)
• Zoom link: https://zoom.us/j/203396828

Attendees

• Alan Stanley
• Gavin Morris
• Donald Moses
• Willow Gillingham
• Danny Bernstein
• Seth Shaw
• Alex O'Neill
• Betany Seeger
• Brandon Wiegel
• Chris Kellen
• Debbie Flitner
• Cary Gordon
• Mark Jordan 🌟
• Jared Whiklo
• Noella MacIntyre
• Tammy Wolf
• Eli Zoller

Agenda

1. Testing Sprint
   1. Sign up sheet
   2. Test cases
2. Two Camps for 2020:
   1. Fedora / Islandora Camp @ ASU
   2. Islandora Camp PEI
3. Two upcoming webinars!
   1. Jan 21 - Islandora 8 at UNLV
   2. Feb 4 - Paged and Complex Content in Islandora 8
4. How to handle new complex metadata fields (ie. identifier with type or other fields requiring subfields) - Carried over from last week.
5. Proposed Changes to Content Modeling
6. Issue Roundup
   1. https://github.com/Islandora/documentation/issues/1395
   2. https://github.com/Islandora/documentation/issues/1396
   3. https://github.com/Islandora/documentation/issues/1398
7. Feel free to add agenda items...

Notes

Testing sprint

Sign up!

Camps

• ASU camp is filling up quickly, so if you're interested, register soon.
• PEI is beautiful and has excellent seafood, and you can't swing a lobster without hitting an Islandora community member.

Webinars

UNLV webinar will feature their ArchiveSpace integration, among other things. Paged content webinar will also demo "all the new stuff". More user oriented than developer oriented.

How to handle new complex metadata fields (ie. identifier with type or other fields requiring subfields):

There appears to be interest in how we can handle complex (with attributes, hierarchical, multipart, etc.) metadata elements. The Slack thread is the best place to chime in if you're intrested. Seth pointed out that complex fields pose some challenges for mapping to RDF and in indexing/search.

Proposed Changes to Content Modeling

• Remove requirements on the Model field
  • Important to keep in mind that this proposal is about loosening defaults, not major structural changes to what we have now.
  • The implications of these changes need to be incorporated into our documentation. As Danny says it's a grey area that we need to make less grey.
• Loosen requirements on the External URI field
  • Not proposing to get rid of the External URI field on terms.
  • Proposing that we also support Linked Authority Link fields in the same way.
  • Some discussion of deployment workflows (dev -> staging -> prod). There are lots of resources in the Drupal world on this but we should document it in terms of how Islandora-specific defaults, etc. might be impact it and how it related to the playbook.
• Use file mime type in favor of the Display Hints field to control viewers
  • Does not preclude what people already do.
  • Rosie: "This would be a change to how Islandora Defaults makes decisions [about which viewer to use]; we are not adding or removing functionality."
  • Mark had some difficulty articulating his position (which turned out to be what Danny is proposing in the document), but everyone is used to that.
• Make Collections and Pages separate content types from Repository Item in islandora_defaults
  • Quite a bit of discussion about adding more content types, in effect multiple 'default' content models that are less bloated than Islandora Defaults and more specific to content models.
• Allow Media to Hold More than One Type of File
  • Did not get to.
• Allow Multiple Original Files for One “Item”
  • Did not get to.

Issue roundup

• Did not get to.