January 6, 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

1. Daniel Lamb
2. Diego Pino
3. Nick Ruest
4. Melissa Anez ⭐
5. Ed Fugikawa
6. Jared Whiklo
7. David Wilcox

Agenda

1. https://github.com/Islandora-CLAW/chullo/pull/30
2. https://github.com/Islandora-CLAW/CLAW/pull/131
3. https://github.com/Islandora-CLAW/CLAW/pull/126
4. Sprint planning
5. Islandora Foundation contract
6. California Fedora Camp

Minutes

See also irc log from 1pm-2pm

1. Chullo ticket looks good. Danny had had a look at it. Diego notes that all the tests we have are on the chullo class, but since we're using the fedora api, he could make the same tests for the Fedora API. Also, what do we think about the uuid generator? Danny: we can inject that as a service.
2. Example Resource service. Danny hasn't looked at it since the update, but it was already pretty solid. Can't really speak to the changes until he has a better chance to review. This and the previous tickets have commits from Diego and Danny both, so someone else should pull it down to test, and some one else should hit the merge button. Jared asks: since we're changing services to use Fedora API, why are we hanging on to chullo? Danny: Thinks we'll have a use for it, but we don't have a use case yet. Jared: we could keep it around as a slightly formed client, for those who have a use for it. Just wondering if it's something we'll have to maintain that isn't going to be widely used. Danny: It's a good idea, but we don't have case for it yet. It's in revision control in case we need to roll it back. Is fine if we want to axe it. It's in the Git history in case we change our minds. Diego: doesn't think we need to develop the fedora API much further. It does what it needs to do right now. Chullo will have more utility models than Fedora API, that we will use in the future; rdf traversing, parsing, getting, etc. In this resource service where it's already formed this isn't needed, but when we get into PCDM stuff, chullo could prove very valuable. Danny: How about we hang onto it for now and if we're still not using it when we are done with the PCDM stuff, we can reevaluate. Danny: The file is getting big enough for us to ask when we should move to actual classes with named member functions, etc. Not sure we're there yet. As long as we document everything with function comments, we can roll with this for a while. it depends on what those involved want.
3. Example Service Pretty much the same discussion as above. Already pull into Diego's 131 PR. Closed since it's superseded.
4. Sprint planning - runs January 18 - 29. Sign up here Nick proposes we continue on with unfinished tickets from the previous sprint. Danny would like a focus on the collection service to come next. It'd the simplest of the PCDM constructs. That will sort out whether we use the raw API everywhere or whether we use chullo. We'll be getting into multiple fedora interactions per request. The act of doing it is simple; handling all potential failures is not. Nick brings up the fcrepo java client that's coming up from that project. Comes from Aaron Coburn work, supersedes the old Fedora client. Does not yet have transaction support. Jared: do we use this over the RESTful API? Danny: Not if we don't have to. Can foresee a use case if we want to go all-java, but 99% of the time, the Islandora community wants php. Jared: even if we use it, we'll still have to figure out how to deal with errors. Nick: so, if we were to write up a blurb about the second sprint, what would we cover? Jared: continuing on with tickets. We should have one for collection services, and note that it's our focus. Danny: we are beginning to formalize our implementation of PCDM. Nick and Melissa will work on a blurb for islandora.ca and Nick will post to the listserv. We should consider starting a document on building PCDM objects, along the lines of the one for Middleware Services. Nick and Diego are in for the sprint; Jared will likely participate as well.
5. Islandora Foundation contract. The IF has some one-time funding to be put to use on this project and hire a developer. Nigel Banks has put together an outline of work for Ansible provisioning for CLAW. Nick and Melissa are working on the contracts documents and hopefully things will be set up by the end of the week or early next week, so Nigel can get started.
6. Fedora Camp in California at Caltech in April. Diego will be an instructor! The goal is to have five people to deliver content, with adjustments for individual expertise. Diego will be looked to for Islandora specific topics, since that was popular at the last one.