July 27, 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

Diego can't speak but did stuff. Drupal 8 integration, a JSON-LD serialiser service for Drupal and some experiments with inline_entity_form to aggregate multiple linked entities (custom/fedora) inside a Node derived type content. Will pull by end of the week
Ben will keep on working during this weekend. Nick clarifies that even when Sprints have a specific time span, everyone is free (and encouraged) to work on CLAW issues between sprints
Kim and Kirsta could not attend today
Jared has been working on CLAW integration tests
Ed had a ton of paper work to deal with. Will make some progress later this week but he worked on Fedora 4 performance test. Potentially making Andrew Woods very happy!
Nick fixed in CLAW/Chullo a change in Fedora4's API, fixity was moved from an http argument to a header. Also did a Chullo and Crayfish version bump. https://github.com/Islandora-CLAW/chullo/pull/53 and https://github.com/Islandora-CLAW/chullo/pull/51. This work also included PHP Unit tests. Jared and Diego did code review. Also some Vagrant work, PHP7, back port to OpenJDK instead of OracleJDK in Ubuntu 14.04 (needs compiling or waiting for official package)

Jared is working on providing standardised integration tests for Fedora4/CLAW so that our microservices can be tested again real data and API changes. Questions raised if this should belong into https://github.com/Islandora-CLAW/CLAW/ or somewhere different.
Jared: likes the idea to have it in the CLAW repo: then not, and then yes again. Mostly because since claw's microservices code can change if fedora API changes, our tests should be always work against micro services. The conclusion is "YES" to move to CLAW repo.
Diego also likes the idea, Nick too. Also some silence. Finally Jared will move to CLAW/CLAW.
This does not cover UI, just Microservices and Fedora4 interaction
Diego asks about upgrade scenario testing, like the changes that can happen when moving to Jena 3.1.
Nick correctly explains this is not needed right now since there are no Production CLAW repositories that could need upgrade to be tested.

We are using a free service named http://codecov.io to check for our code test coverage. We have now YAML config files for this for each service being tested, making sure we test and stats are only against master. Also ttps://github.com/Islandora-CLAW/chullo/blob/master/phpunit.xml.dist#L15-L22 was updated to whitelist which files should be considered in coverage.

Each CLAW service has a /test folder. example here We just need to finish (or start!) PDX tests.
Diego says we could also tests constructors and /controllers which are being ignored right now.
See https://github.com/Islandora-CLAW/CLAW/issues?q=is%3Aissue+is%3Aopen+label%3Atests
If anyone is interested in contributing with Tests for PDX, it would be highly appreciated

To resume a long discussion: https://github.com/duraspace/pcdm/issues/53
PCDM 2.0 is based on Hydra Works and imposes(or suggests right now) a more complex structure for files, based on FileSets construct, an indirect container.
Diego thinks there is nothing to worry about if all the changes are just based on documenting use cases. If the ontology itself does not imposes this restrictions, then we will always be free to be Ontology compliant (which is the important thing in semantics)
Jared does not agree completely, and correctly expressed concerns about how much is PCDM needed right now really and if the promise of interoperability can really be fulfilled
Diego: to read hydra data we need to use PCDM as they use it, means as they have documented it, which is not the same as what the Ontology itself says but also use hydra namespace “hasmodel” or similar. Does not remember exactly the predicate.
Diego asks about political implications: Nick says we need to discuss this further and support a open discussion in the PCDM channels, means more Islandora community interaction.
Marcus: That would be a good project for the next community sprint.
Melissa: good one to follow: https://groups.google.com/forum/?hl=en&fromgroups=#!forum/pcdm
Jared suggests the idea of an TCK that could run against an existing repo, and validate PCDM object constructs, traverse and build the graph.

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