July 26, 2017

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

• Bethany Seeger
• Melissa Anez
• Yamil Suarez
• Eddie Rubeiz
• Natkeeran
• Jon Green
• Daniel Lamb
• Jared Whiklo
• Diego Pino

Agenda

1. CLAW Update
2. XML Convo Revisited Revisited
   1. More discussion of the potential in https://github.com/mnylc/dcmny/blob/master/twig/mods_twig_base.html
3. ... (feel free to add agenda items)

Minutes

CLAW Update

• Adding Link Header. Link Headers are important to write smart clients/REST APIs. This is needed for derivative related functionality.
• Have done some exploitative work related to "xml stuff" for configuration related work.
• Trying to use the Pencil to create wire frames.
• yamil contributed PR related PHP Doc.

XML Convo

• Danny - What to do with people with XML metadata. This is a barrier to migration into CLAW. We need to find a way to get the XML metadata into Drupal as Fields. Converting into fields provides many affordances such as Solr Search, RDF Mapping etc. The other part of the coin is how to get XML out from Fields. Diego has done work to use Twig template to export XML from Fields.

• Diego - The main advantage of Twig is that you don't need an XML parser, thus less expensive. Twig is relatively easy to use, and to incorporate it into Drupal (i.e export as XML). We can also export it for OAI-PMH.

• Diego - The main issue is how to put everything we need from MODS into Drupal Fields. Data type plugins, Data definitions can possibly used to export MODS into Drupal Fields. Media Entity may be built using this.

• Bethany - Does this (Twig!) allow for looking up of URL when parsing (i.e for subjects)?

• Diego - Twig can run custom code, which can possibly be used to resolve URLs etc.

Working with Islandora CLAW

• Bethany - I am doing an Islandora install. I've am mostly there. I am wondering about how the events system work in Drupal.

• Danny - In short, we use the Rules module to generate the AS2 events. These are published to ActiveMQ broker. That is read by Camel/Karaf, which then orchestrates the required actions such as creating Fedora entries.

• Bethany - Seems like events are not firing! Where does the JSON Web Token come into play here?

• Danny - Actual enforcement is done in a component in Tomcat and with some components jonathangee contributed. If you are getting nothing, you should see some failed messages in the Drupal interface. Clearing Cache seems to help!

• Danny - You should be seeing a lot of stuff in the Karaf log. You can see the configuration setting for Broker here: http://localhost:8000/admin/config/islandora/core. It does do some basic validation to establish the connection.

• Bethany - If the Broker is working ok, then the issue might be Alpaca.

• Bethany - What is Islandora doing with Fedora's REST endpoint?

• Danny - PUT (RDF and files) and DELETE are being used right now. Once in Fedora, we use the resources to do derivative generation using micro-services (API-X, Crayfish). After this is fully completed, we will add other Rules actions.

• Danny - We use PUTS and DELETE. PUT uses update_date to decide if a resource need to be updated. For files, it checks the checksum to decide if it need to be update. PUT and DELETE are used to handle failure cases better.

What is needed with XML

• Diego - We need to get detail specifics with respect to XML support in CLAW.

• Jonathangee - People would want to import XML into Drupal, then serialize it back.

• Diego - Would people want to edit XML in Drupal? People have expertise with XML.

• Bethany - We need to convince people that is about the data and not about the format. Locally, we are not going to use MODS.

• Diego - It would be difficult to convince everyone to not to use XML. Library of Congress will continue maintain MODS for foreseeable future. People have attachment for formats or standards.

• Danny - We need to get to a point where MODS can be imported, and exported.

• Jonathangee - ContentDM does something similar. But, people are not comfortable with that workflow/solution. Perhaps, we can provide some advantages such as bulk updates on fields. I share the concerns. People are attached to XML.

• Diego - We have to follow standards, that is what Islandora has done best.

• Danny - We are offering different options with respect to MODS.

• Jonathangee - Is this really feasible? If MODS is there, is it useful if people cannot edit it.

• Danny - We are not planning to support editing of XML in Drupal. It is very difficult to maintain. What we will support is being able to update XML. We don't duplicate functionality for Form Builder and Editor for XML.

• Jonathangee - I don't think we should support XML Forms in CLAW. Feeding XML into Fields then serialize back into XML, then that is a good compromise. But, this can be hard sell. ContentDM made this a hard sell, because they did it poorly. A lot of people have been impacted by that.

• Diego - People have trust issues with developers. They fear that their beautiful MODS would be hacked.

• Jonathangee - Some concerns are probably warranted. There are some bad software out there in this field.

• Danny - We have to give some software for people to play and give feedback.