November 2, 2016

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)
• 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

• Nick Ruest
• Amanda Lehman
• Ed Fugikawa
• Danny Lamb
• Marcus Barnes
• Don Richards
• Diego Pino
• Natkeeran Ledchumykanthan ⭐
• Jared Whiklo
• Melissa Anez
• Jon Green
• Tom Shorock
• Mark Cooper

Agenda

1. Vagrant -> 16.04
2. Vagrant -> Solr 6.+
3. Import-Export
4. ... (feel free to add agenda items)

Minutes

1. Vagrant -> 16.04

Nick: Earlier, there were issues suing ubuntu/* vagrant boxes. Thus, CLAW initially used bento/* box. The issues should have been addressed by now. This PR moves the vagrant box to ubuntu. We need developers to test it against various vagrant and os environments.

2. Vagrant -> Solr 6.+

Nick: Currently we are using Solor 4. Solr 6 provides additional features, easier to install and has better documentation. This PR moves the CLAW vagrant to Solr 6.

Danny: Need to see if Drupal supports it. Users can still use older Solr's!

Diego: Solr 6 has many advantages. However, we would have to review the transforms.

Nick: Need volunteers to test Solr 6.0 vagrant . Solr PR is of lower priority than the above Ubuntu PR.

3. Import-Export

Nick: Phase 2 of the import/export work is being carried out. The agenda and call details can be found here: https://wiki.duraspace.org/display/FF/2016-11-07+-+Import-Export+Planning+Meeting. The third sprint is schedule for December. We have two developers and looking for one more.

4. ... (feel free to add agenda items) - https://github.com/Islandora-CLAW/CLAW/issues/398

Danny: I am running into an issues mapping routes and operations (CRUD) for entity resources. Druapl needs to know type of entity and the bundle (entity type) to create a new entity resource. Currently drupal expects a URI local to its installation (ex :http//mydomain:8080/rest/type/node/page). This is problematic because the ontology required by the drupal would have to be specific to its installation. I.e JsonLD request has to point to the local URIs. This will require people publish own set of ontologies for each islandora installation!!

Diego: We cannot use domain specific URIs. Will be problematic for people using separate fedora and drupal installations.

Danny: One option is to handle this by pre processing requests in the module, i.e using hooks.

Diego: Another option is to use config mapping. Similar to how API-X! For instance, we can specify the mapping using config entities (YAML). Need to look into this further, if we can support all use cases.

Danny: It may be sufficient to do the mapping in the code.

Nick/Jared: That can work.

Danny: Is this something metadata people concern about?

Amanda: I just need to know how to preserve the relationships already in Islandora. How to map, basically.

Nick: Mapping of relationships can be done via https://github.com/fcrepo4-exts/migration-utils

(Not directly related to the above issue.)

Diego: Had similar issues when Syncing resources. Should we consider having multiple end points for a single resource!

Danny: Some issues exist with that option. Replication of URIs pointing to the same resource is a bad practice!.

Diego: It may be sufficient to limit operations based on use cases. What is the use of having GET directly on entity type? However, it does make sense to POST it to the entity type.

Amanda: We will need to support multiple URLs pointing to the same resources, such as Authority records.

Diego: This is for internal handling only.

Nick: Having multiple end points can confuse developers. Can add to technical debt.

Danny: These issues have to be further explored. Will iterate through some solutions to get further clarification.