Skip to content
Jared Whiklo edited this page Oct 11, 2017 · 5 revisions

Time/Place

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

Attendees

  1. Rosie LeFaive
  2. Jonathan Green
  3. Bryan Brown
  4. Eddie Rubiz
  5. Yamil Suarez
  6. Favenzio Calvo
  7. Jared Whiklo
  8. Audrey Templeton
  9. Adam Soroka
  10. Natkeeran Kanthan
  11. Minnie Rangel

Agenda

  1. Second Ansible Sprint Sign-Up: https://docs.google.com/spreadsheets/d/1s5GCs9zrJsXevOulyRehpC-wdn4ShOVvEeaHDN_A2eo/edit#gid=130055771
  2. https://github.com/Islandora-CLAW/CLAW/issues/730
  3. https://github.com/Islandora-CLAW/CLAW/issues/731
  4. https://github.com/Islandora-CLAW/CLAW/issues/729 pending @Natkeeran
  5. ... (feel free to add agenda items)

Minutes

  1. Sign up if you are interested, Sprint is scheduled for November 6th - 17th. Finish CLAW Playbook and then do what is necessary... Centos/Redhat perhaps.

    Trying before American Thanksgiving to not get crushed by the rush for Xmas.

    Questions can be sent to Danny.

  2. Blazegraph will not be supporting clustering, so want to make sure other triplestores are supported.

    No choices in mind. Just want to make sure we are able to use other Sparql compliant 3store.

    Have Ansible allow us to choose a triplestore when building.

  3. Can't deploy API-X and Alpaca into the same Karaf. Not sure why, but this is the point of OSGi is to allow string isolation for components.

    Lots of options, unsure how best to resolve this.

    Could also run two Karaf containers, but that seems less useful.

    What about a different container instead of Karaf.

    Perhaps using something like Apache ServiceMix, which is a packaging of certain libraries along with Karaf.

    Break API-X out into one Karaf container and move Alpaca into something else...another container.

  4. Modelling complex RDF relationships from Drupal to a triplestore.

    A person entity can be related to another person by any of a set of "relationships". So the simplest way is to model each relation as a property.

    Drupal allows multiple mappings per field. For drupal forces you to have one field for each type of relationship.

    If we start building DC term metadata then do we have all the possible fields that you can define in DC.

    Perhaps we build out the core RDF Mapping, or at least open a ticket on Drupal.org and see what the current maintainers say. It might lead to a better path for collaboration.

    Nat has a work around for now, but we should continue looking for a better way to support mapping the differs by field and node instead of just bundle and without intermediate URIs if possible.

  5. Should CLAW playbook issues be put in the main CLAW issues?

    Yes, transfer them over to the main queue and disable issues on the Islandora-DevOps.

    The main problem with Github has been permissions related. Perhaps "projects" might allow for some separation but still under the same organization/repository.

    Bryan will move the issues and then Danny will close the issue queue.

This is an archive. For new Tech Call notes, click here

⚠️ ARCHIVED Islandora Tech Calls

⚠️ ARCHIVED Islandora User Calls

Clone this wiki locally