November 22, 2017

Time/Place

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

• Time: 1:00pm Eastern Standard Time US (UTC-5)
• 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

• Melissa Anez
• Marcus Barnes
• Rosie Le Faive
• Seth Shaw
• Danny Lamb
• Natkeeran
• Jared Whiklo
• Jonathan Green

Agenda

1. Sprint Recap
2. Fedora API Specification Release Candidate on the way
3. https://github.com/Islandora-CLAW/CLAW/issues/656
   1. Proposal to use Context module instead of Rules?
4. Storing Drupal URIs in Fedora? https://groups.google.com/forum/#!msg/islandora-dev/WqgmbkLlUUY/cGVzS2OIAgAJ

Minutes

1. Sprint recap

   New people joining and contributing.

   Some things got done

   Moving close to feature parity

   Some new development in the Centos/Ubuntu split.

   As soon as PR-24 is merged we should start deprecation of claw_vagrant in lieu of claw-playbook

2. API specification

   Watch for the coming Release candidate today or on Monday.

   There will be a one month review period.

   Any feedback is appreciated.

3. Filter what is persisted to Fedora

   Lots of research but Rules conditions are not flexible and don't always work.

   Rules conditions are locked down to what you can get from an annotation, no UI to use.

   Also looked at Business Rules, which is an add-on module. But is more useable, but has some bad assumptions baked in.

   Mark Jordan brought up the Context module, some investigation reveals some very neat options and could allow possible ways to handle a lot of UI issues. But also a way to do this filtering of what to persist. It is neato!

   UTSC uses islandora_context module for 7.x to allow adding additional CSS and JS based on object.

   Existing Rules would be replaced with Context if Context can cover all our other use cases.

   Make sure we can do this with Context before we remove Rules.

   Most of the core conditions are core Drupal and so are very re-usable.

   Going to try writing a regular Action and wrap it in a Context Reaction, because Actions are available to use for Views Bulk Operations.

   When you are using the Rules, you can the content as it operates. Do you get the same level of content access with Context? Yes, you will get the same level.

   Danny will look at creating a PR or feature branch with some example context that doesn't replace the Rules but operates similarly.

4. Storing Drupal URIs in Fedora

   Picking a predicate is not a pleasant process, those can be difficult conversations.

   There are some things that are missing that we will need to resolve.

   Linking the object in Fedora to the object in Drupal somewhere in the Fedora resource.

   Drupal Media bundle needs to be persisted to the Fedora, makes it easier to post to the endpoint to create a Drupal content-type. This is needed for standing up a new Drupal front-end from an existing Fedora backend.

   How do we know which JPEG is a source document (basic image) versus a derivative (large image).

   Right now if you want different RDF types to flow to Fedora and triplestore. But that will lead to a lot of duplicated bundles with small differences. We need to boil down the media types to mime-types so we could determine what to do from the containing resource. So an "image" owned by a "basic image" is the source document, but owned by a "large image" is already a derivative.

   But you can re-use the media bundle once the information is stripped out.

   The concept of the OBJ is now a field and whatever it references is the "OBJ" (or the preservation master)

   But we need to be able to look at the media bundle and what points to it and then add additional RDF to the media bundle before we persist it.