March 14, 2018

Time/Place

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

• Time: 9:00am Eastern Daylight Time US (UTC-4)
• Dial-in Number: (641) 715-3570
  • Participant Code: 304589#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• 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

• Seth Shaw
• Jared Whiklo
• Danny Lamb
• Rosie LeFaive
• Bryan Brown
• Natkeeran
• Yamil Suarez
• Bethany Seeger
• Mark Jordan

Agenda

1. LAKESuperior
2. Drupal version is pinned down in claw-playbook via https://github.com/Islandora-CLAW/drupal-project
3. New API-X service to resolve Drupal URIs into Fedora URIs
   1. https://github.com/Islandora-CLAW/Crayfish/pull/44
   2. https://github.com/Islandora-CLAW/Crayfish-Commons/pull/16
4. Another header for REST: https://github.com/Islandora-CLAW/islandora/pull/81
5. Removing some cruft: https://github.com/Islandora-CLAW/islandora/pull/79
6. OOM errors in Travis build: https://travis-ci.org/Islandora-CLAW/islandora_image/jobs/353390309
7. Controlled vocabularies via Drupal taxonomies
   • https://en.wikipedia.org/wiki/Controlled_vocabulary
   • https://www.coar-repositories.org/activities/repository-interoperability/coar-vocabularies/
   • How can we add the external URIs for vocabs/terms to taxonomies without breaking their internal URIs?
   • Can we map taxonomy/term URIs into RDF on export?
8. CLAW REST Ingester
9. ... (feel free to add agenda items)

Minutes

1. LAKESuperior -

• Danny - LAKESuperior is a python implementation of Fedora. We can test it against. It would be beneficial to support as many Fedora implementations as possible.
• Jared - My feeling is that it may not follow the specifications tightly.
• Danny - Lack authentication, thus may not be ready yet.

2. Managed Drupal version

• Jared - The purpose of the drupal project is to pin down the drupal version.

3a. New API-X service to resolve Drupal URIs into Fedora URIs

• Danny - This service will provide a means to add or replace Fedora URS to the Fedora rdf resources. This helps keep the structure and integrity of a resource fully within Fedora.
• Jared - Our API-X is currently not installing properly out of the box. There might be something missing related to loading service. The particular service is an extension to API-X framework.
• Jared - We can use this service to update fedora repository after sync is completed. I am not sure how this might work.

3b. ContentType/Object - Media - File relation

• Jared - Sub collection in Fedora is not a LDP container. Instead, it has membership to parent collection. Thus, if a parent collections gets deleted, it does not delete the sub collection. There are pros and cons to this setup.
• Jared - Noted that files are being synced, not media bundles. Currently there is a hasFile in object, which is pointing to File. But, we are missing the media relation information in the file resource.
• Rosie - The object of the hasFile, should it point to the binary or to the resource describing the binary.
• Jared - File is a binary, which has Technical metadata rdf resource about the binary.
• Danny - In Drupal, you cannot add file headers to files. Makes it harder to navigate, because you cannot go to file and get the media.
• Bethany - If I add a binary object to Drupal, does it store it in Drupal and Feodra?
• Danny - Currently, it creates a duplicate. It stores in the file system and a copy to Fedora. This is where we need to have cleaver way to handle this. [https://www.drupal.org/project/flysystem](File system API) can help us here. Fedora can be used to put in files.
• Bethany - What about external content in current Fedora (3.x)?
• Danny - We are not 100% doing that in Drupal. Authorization is controlled by Drupal.

4. Controlled vocabularies via Drupal taxonomies (Using Taxonomies and Context to handle display and rdf mapping)

• Danny - By using taxonomies and context, we can get away from the one content type one rdf mapping limitation. We can decouple the structural and descriptive part of a content model. Thus, we can have one Drupal islandora content type, which can be configured to display and flush based on taxonomy tags.

• Danny - Instead of making separate content types. We can tag them. Based on tags the display and rdf mapping can be altered.

• Mark Jordan - If we use Drupal taxonomies, instead of rdf types then do we loose some portability?

• Danny - No, we would need to get the taxonomy info of the object into the Fedora.

• Seth - Taxonomies can be used to set the rdf type.

• Rosie - This approach will reduce administrative burden.

• Seth - Interested in seeing how context can be used to define rdf per taxonomy.

• Bethany - Would we put in standard triples in Fedora?

• Danny - yes!

• Bryan - Taxonomies and context can be used to handle many rich use cases. However, taxonomies are usually local URIs. We would need to reconcile with external URIs. If we need to flush external URIs to Fedora instead of local, that is possible.

• Seth - One option is to use Alias.

• Danny - Alias cannot be in different domain.

• Danny - I will create a ticket to investigate how to use taxonomies to handle multiple content types.