August 15, 2018

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join. Here is the info:

• Time: 1:00pm Eastern Daylight Time US (UTC-4)
• Zoom link: https://zoom.us/j/203396828
• IRC:
  • Join the #islandora chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #islandora on irc.freenode.net

Attendees

• Daniel Lamb
• Melissa Anez 🌟
• Ann McShane
• Andrija Sagic
• Jared Whiklo
• Jonathan Green
• Marcus Barnes
• Mark Jordan
• Natkeeran
• Paul Pound
• Rosie LeFaive
• Yamil Suarez
• Bethany Seeger

Agenda

1. Sprint Next Week
   1. Sign up sheet: https://docs.google.com/spreadsheets/d/1s5GCs9zrJsXevOulyRehpC-wdn4ShOVvEeaHDN_A2eo/edit#gid=2121481344
2. Sprint Planning Meeting tomorrow: https://docs.google.com/document/d/1MrdiukTePa6iRg0yknF9DnM1rI_sHZ_Qz_yS8xmAsAo/edit#
   1. Using taxonomy terms vs. content types for things like places and subjects.
3. I promise I'm done: https://github.com/Islandora-CLAW/islandora/pull/92 and family
4. ... (feel free to add agenda items)

Minutes

Sprint Is actually Friday, not tomorrow. 2:00PM Atlantic time. Will look at the work Seth Shaw has already done Also looking for more ways to link out to other entities.

Taxonomy versus content types: Taxonomy can be used for more than just categories. Context, access control, rendering viewers. Attributes of the node. From a librarian perspective, anything that is traditionally under authority control makes sense as a taxonomy term, anything that is an item in a collection would make sense as objects/nodes. When are creating/authorizing a finite list (which can grow), those should be taxonomies. Everything should have URIs. Main destination is that taxonomies are hierarchical out of the box, but otherwise content type isn't that different. This is a Drupal 8 versus Drupal 7 thing. They are more alike now. Needs some experimentation to see how Solr treats them.

Taxonomy terms are captured in Fedora. Full graph is in the triplestore, not necessarily via the RDF. Hierarchical geographic modelling is hard. Can be done with 7.x Islandora (MODS!), but putting places into a firm hierarchy is messy and chasing moving targets. Maybe we don't make a hierarchy? Just geo terms. We might import one, but it would be huge. Migrate is a good tool for importing terms from authority sources, and we can cache things locally and use URIs to refer out.

PR 92 is done. Fix for core block placement is piled onto Flysystem stuff. Once merged, the pattern can be repeated for other things.

Other: MIG is still working on a MODS to RDF mapping. They will be involved throughout the sprint.