August 29, 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

• Ann McShane
• Minnie Rangel
• Seth Shaw
• Rachel Tillay 🌠
• Paul Pound
• Mark Jordan
• Jared Whiklo
• Natkeeran
• Rosie LeFaive
• Danny Lamb
• Marcus Barnes

Agenda

1. Controlled Access Terms PRs:
   1. Adds schema config
   • This will be merged.
   1. Remove config from module
   • Once 4 is merged, 6 will be re-exported, and merged.
2. Create and populate a MARC Relators vocabulary
   • Now that we have a field (Controlled Access Terms PRs above), Seth will be working on this today and tomorrow.
   • Will "Type of Resource" be used in place of our content models. Rosie mentioned MIG has looked at this. The MARC resource terms list is the closest to this and should match up 99% of the time to someone's type of resource. Mime Types are going to be more attached to the object, where types of resource are slightly more about the conceptual form of the object.
   • This is separate from what Jared is doing.
   • Will we still need the a place where we describe content model? Perhaps we need a way to control the type of fields you see, regardless of the mime file types. Examples: citations vs books.
   • We will still need some additional way to say, for example, that some PDFs are books and some are pages of books? And that some audio-nonmusical recordings are interviews and some are field recordings?
   • Do we want to create a vocabulary to retain the content model information from 7 that may impact which viewers display, access control, and model should be used in CLAW?
   • Jared's initial question: Should the core list of terms be expanded? No. We will need to expand the list as we go.
3. Support additional RDF types based on a configurable field
   • Pat is working on this.
   • Somewhere in this Drupal/Islandora swamp. Exporting this and then trying to import it failed when Rosie tried to create fields...is this related?
   • Danny: No. This is related to deep, arcane, undocumented aspects of Drupal.
   • Rosie/Danny discussion: This will be easier to export/import as a feature instead...there's a UI for it going forward that Nat has written up: https://github.com/Islandora-CLAW/CLAW/blob/master/docs/islandora/drupal-bundle-configurations.md
4. Can we close Create an 'Agent' content type ?
   • Yes.
   • There's still some play on making this a vocabulary instead of a content type.
   • Instead of creating an "agent" content type, this has expanded to fit many types of things.
   • Yesterday we decided to use "agents" as taxonomy terms instead of content types to allow for hierarchy in a different way, and because taxonomy terms allow there to be a separation between bibliographic entities and authority entities for searching and conceptual understanding.
   • Treating agents and subjects as taxonomy terms has the downside of making this less useful for Linked Data projects where names will need to be nodes.
   • Discussions will continue.
5. Add more granular fields for taxonomy terms, specific question about making external URIs
   • Will this information want to persist in your repository with an external URI?
   • Will we want someone to be able to export your Fedora and upgrade your Drupal without migrating your content?
   • Rosie: What is the problem we're trying to decide? Did my questions cause this?
   • Real question: For each of these taxonomy terms, do you want to have an external URI to the taxonomy term in Fedora that is associated with the taxonomy term that could persist?
   • At this point, the answer appears to be no.
   • Ongoing conversation will continue
6. ... (feel free to add agenda items)

Minutes