Time/Place

Attendees

Related

Agenda

  1. Overview of Phase 1 work & stakeholder feedback
    1. Review of current state
      1. Completed Phase-1 requirements
      2. Not yet completed Phase-1 requirements
      3. Open tickets
    2. A few additional questions that have arisen during testing:
      1. Best way to represent redirects (specifically, is the zero-byte placeholder useful?)
      2. Specifying a location for the config when one does not exist
      3. Handling slash vs. no slash at the end of the base repository path
    3. How can we improve the stakeholder engagement/feedback process?
    4. Verification tool
      1. see also, for a version that verifies RDF: https://github.com/jwestgard/fcrepo-import-export-verify
  2. Overview of Phase 2 requirements
    1. Support import from and export to a TBD list of external systems
      1. APTrust
      2. Archivematica
      3. MetaArchive
    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
  3. Sprint resources
    1. Developers
      1. Esmé Cowles
    2. Testing and Validation
      1. Youn Noh
      2. Joshua Westgard
    3. Documentation
      1. Youn Noh
      2. Joshua Westgard
  4. ...

Minutes

  • Review of the requirements from Phase 1:
    • Support transacting in RDF – yes.
    • Support including Binaries in export – yes.
    • Support references to other resources – yes: There was some related discussion here of external references and the creation of binary placeholder files.
    • Action item: Josh will create a ticket for deciding the best way to handle this (not create this binary or for the verification tooling to better handle it when encountered).
    • Support import into a non-existing container – yes.
    • Support export of resource and members based on "LDP:contains" predicate – yes.
    • The URIs of round-tripped resources should be the same (assuming the same base repository URI): yes, but with an asterisk because of the pair-tree issue (FCREPO-2240).
  • Outstanding issues: The biggest one is the pair-tree issue mentioned above.
  • Open tickets:
  • Getting more stakeholder feedback:
    • Would a template such as that employed for release testing be useful?
    • There is a danger that this could box stakeholders into testing in a pre-defined way that is not helpful.
    • Action item: Josh will create a single wiki page with links to the tooling and instructions to which stakeholders can be directed.
    • It seems reasonable to ping folks who signed up but who have not yet provided feedback.
  • Prioritizing work for December sprint:
    • The consensus was that cleanup of the open issues is a requirement before the Bagit work starts.
    • The bug fixes may not be an enormous amount of work but with the current commitments it may not be possible to get to the Bagit phase of work in December.
    • If we can get more developer commitments we can hopefully get to some of Phase 2 as well.
    • Action item: Nick will approach some ~5 developers he has in mind to try to recruit additional participants.
  • Additional interested potential stakeholders introduced themselves and described their use-cases.

 

 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.