July 11, 2018

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)
• Zoom link: https://zoom.us/j/203396828
• 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

• Daniel Lamb
• Melissa Anez ⭐️
• Jonathan Green 🌠
• Marcus Barnes
• Mark Jordan
• Meredith Hale
• Natkeeran
• Paul Pound
• Paul Clifford
• Rosie LeFaive
• Seth Shaw
• Tom Shorock

Agenda

1. CLAW Update
2. Any examples of CLAW online?
3. Rosie
4. ... (feel free to add agenda items)

Minutes

1. • CLAW Update from Danny:
     • Have 11 people for the upcoming sprint
     • August 20 - 31
     • Take all the migration attempts people have worked on and turn it into something that the community can work with.
     • Lots of metadata questions buried in there.
     • Good representation from the MIG.
   • Question from Jonathan: Will there be more breaking API changes once the open beta is released.
     • Low possibility, but there could be more breaking changes in the open beta period.
     • Will support migrations to move things from the beta versions to things in the future.
   • Seth shared: https://github.com/seth-shaw-unlv/controlled_access_terms
   • Danny has basically finished the Flysystem work he has been doing.
     • Has some PRs with substantial changes for downstream modules of the change.
     • Want to demo some flysystem worth with dropbox at iCamp Halifax.
     • Interface changes to Milliner. (Melissa's notes from here on out)
     • It works an it's really neat
   • Mark asks for summary of how CLAW manages Very Large Files
     • End goal is to use Fedora's abilities, once the community implementation is there
     • For now we can point at an external source (AWS, etc). Can be in cloud or local. Then you go through and make db files for it in Drupal, leaving the masters where they are. Drupal becomes a gateway and access control, normalizing object regardless of where they live.
     • Good for large files you don't want to move, or existing collections of files you want to put a new front on
     • Main factor to look at is access. Whether we use Fedora's WebAC or not. If files are 'in' CLAW but not Fedora, Drupal's security rules. It will act like a Drupal private file system.
     • Fixity checks will access the file in the external system, which could be an expensive operation for external content. There's an [open issue]https://github.com/Islandora-CLAW/CLAW/issues/847) for managing Fixity in CLAW where this can be discussed further. Might be handled with external microservice to solve the bandwidth issue.
   • Seth asks how Canteloupe will work with this
     • Right now, it just doesn't The flysystem work has broken Canteloupe. BUT - it can be just given uris. Danny has a plan.
2. • Request for real live CLAW sites on the web. There is:
     • [Dragoman Renaissance Research Platform]http://dragomans.digitalscholarship.utsc.utoronto.ca/home)
     • UPEI Herbarium
     • UNLV has a site but it's not public.
     • Several sites setting up in the fall
   • Is there documentation for using Tags + Context in CLAW? it looked cool in the demo video
     • Not yet, but it's coming. The system itself is not quite finalized and will get more features (splitting out access control via tags, for instance)
     • At heart, it's just Drupal Taxonomy and Context, but we're adding into complications with uris. Everything we're doing with Tags, could be done with something else that triggers Context module.

3. Question from Rosie: "How are folks dealing with “test” and “production” environments? We want our final repo to be at our canonical “nice” domain (islandarchives.ca) but that’s currently in use with the old repo. We don’t want to migrate the domain till we’re finished making it on CLAW, but the URI’s are getting minted at our development domain. Is this gonna be a problem?" - This is tricky. We need to figure it out. You should not get stuck with what's on your dev site. There are a handful of options, but the easiest would be to use Drupal migrate to go from Drupal to Drupal (this is what it's for, after all), and we'd need a process to go in and update what would be missed by that. Gemini will be a problem. Fedora will respect the host header of whatever you give it. - Drupal does not care about domains. It's Gemini and the tripestore that would need to be updated. It's an issue at the Fedora level and Linked Open Data in general. - Should have a use case in the issue queue - It's honestly pretty cool that some one is far enough in production with CLAW to be asking this question 😻