Skip to content
Natkeeran edited this page Oct 3, 2018 · 14 revisions

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

Agenda

  1. Roadmap still open for review
  2. Riprap fixity microservice overview and demo
  3. Islandora CLAW and OpenAIRE: How does it fit into our roadmap?
  4. New PR to install/test all changes for Islandora-CLAW/CLAW#888
  5. New Issues:
    1. https://github.com/Islandora-CLAW/CLAW/issues/945
    2. https://github.com/Islandora-CLAW/CLAW/issues/946
    3. https://github.com/Islandora-CLAW/CLAW/issues/947
    4. https://github.com/Islandora-CLAW/CLAW/issues/948
  6. https://github.com/Islandora-CLAW/CLAW/issues/854#issuecomment-426630758
  7. ... (feel free to add agenda items)

Minutes

1. Roadmap still open for review

2. Riprap - checksum/fixity monitoring and audit trail - Mark Jordan

  • Riprap provides fixity monitoring and audit trail. It is written as a micro service and can be run as a cron job or via api calls. It has a plugin in architecture which can be used to extend or customize its functionality. It issues a GET or HEAD request against Fedora to get the checksum. It can store the results in a database, store it back to repository or to other locations. Currently it supports get, add new and update methods.

  • MJ is looking for feedback with respect to how to traverse the repository objects. Also, how to schedule checksum monitoring cycles. Danny suggested https://github.com/fcrepo4-exts/fcrepo-camel-toolbox/tree/master/fcrepo-reindexing approach might be useful. Danny also noted that drupal node list can be queried, and it has paging mechanism.

  • Nat brought up the issue of whether a new version of a resource will be recorded as an error by checksum checker. Jared noted that versions are explicitly created and change in resource does not necessarily crate new versions. A approach to handling this use case is needed.

  • MJ is looking for users to test and provide feedback for this module.

3. OpenAIRE

  • Melissa noted that OpenAIRE people have reached out to her to see if Islandora CLAW is planning to support OpenAIRE v4. Several people noted that they did not fully understand what supporting OpenAIRE fully entails.

  • JG/MJ noted that supporting OAI-PMH may go long way in OpenAIRE. Support for OAI-PMH is a priority roadmap item for CLAW. Making OAI-PMH elements templateable can fulfil much of OpenAIRE requirements.

  • Seth and Jared noted that OpenAIRE has specific value statement requirements. Also, requirements related to capturing funding related info.

  • Jared - We can say Islandora CLAW will be built with the ability to share and make metadata harvestable.

  • Danny/Melissa to create an issue to follow up as well as to provide response to OpenAIRE.

4. PR - refining the Islandora CLAW vocabularies

  • This PR pushes major changes (mostly configuration) to refine the vocabularies or tags that drive much of Islandora CLAW's drupal behavior. It makes use of DCMI Type Vocabulary.

  • Some additional modifications include field groupings, content browser for auto complete and field permissions.

5. Recent Issues - Explore possibility of a Fedora-less CLAW

  • Several users showed interest in this. JG noted that this could be an entry level hosted service. BB noted that S3 can be used a low cost preservation layer instead of Fedora.

  • Seth and Danny noted that with some configuration and tweaking this is possible. Though, users may loose some functionality such as audit checking.

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

⚠️ ARCHIVED Islandora Tech Calls

⚠️ ARCHIVED Islandora User Calls

Clone this wiki locally