Time/Place

• Time: 10:00AM Eastern Time US
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php

Attendees

• Nick Ruest
• Andrew Woods
• Esmé Cowles
• Joshua Westgard 
• Karen Estlund
• Bethany Seeger
• Bridget Almas

Related

• Design - Import - Export

Agenda

1. How can we improve the stakeholder engagement/feedback process?
2. Verification tool
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Requirements (discussion)
      1. Verify same number of resources on disk as in fcrepo
      2. Verify same number of resources in fcrepo as on disk
      3. Verify same checksum for binaries
      4. Verify same triples for containers
      5. Record which resources have been verified
      6. Others?
         1. Verify fcrepo to fcrepo
         2. Verify disk to disk
         3. Use generated config file as sole input
3. Overview of Phase 2 requirements
   1. Support import from and export to a TBD list of external systems
      1. APTrust
      2. Archivematica
      3. MetaArchive
      4. Perseids (Tufts) - possible
   2. Support transacting in BagIt bags
   3. Support export of resource and its "members" based on a user-provided membership predicate
   4. Single resource bags 
   5. The structure and scope of accepted and produced BagIt bags must be configurable
      1. Clarification: structure relates to required and optional tagfiles in the bag
      2. Clarification: scope relates to contents of the bag, e.g. single object or object and all members based on specific membership predicate
   6. Overview of existing Phase 2 tickets
4. Sprinters
   1. Developers
      1. Esmé Cowles
      2. Jared Whiklo
   2. Testing and Validation
      1. Youn Noh
      2. Joshua Westgard
   3. Documentation
      1. Youn Noh
      2. Joshua Westgard
5. ...

Minutes

1. Improving Stakeholder Feedback
   1. Reach out to Fedora Leaders to ask them to make participation a priority.
   2. Circulate the call for feedback more widely (currently went only to the two Fedora lists, but could go to Islandora and Hydra communities as well).
   3. It is OK to reach out directly to folks who have previously self-identified as stakeholders but who have not yet responded.
   4. Perhaps setting up a framework in which more help was available for those wishing to test and give feedback would encourage participation from folks who are otherwise hesitant about their own ability to contribute.
2. Verification Tooling
   1. Original tool to walk Fedora repositories and compare them.
   2. Looking for additional feedback on what might be desired in such a tool.
   3. Would Fedora supporting fixity checks for RDF sources make this verification process easier?
   4. Walking a subset of a repository would also be good.
   5. Once the import/export can support re-import of server-managed triples, we should definitely also be verifying those.
   6. Prioritization: 
      1. i-v seem to represent basic verification.
      2. vi.1-3 would be "nice to have" 
3. Requirements for Phase 2
   1. Support for certain bag profiles, including a generic profile; for the Perseids project, this is likely to be a Research Object Bundle profile per https://github.com/ResearchObject/bagit-ro
   2. Both import and export should be able to transact in BagIt bags.
   3. Other predicates should be possible, which will also have the side-effect of allowing single-resource bags.