...
- Time: 3:00pm 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
- Andrew Woods
- Nick Ruest
- Joshua Westgard
- Youn Noh
- Esmé Cowles
- David Wilcox
- Jon Stroop
- David Chandek-Stark
- Elliot Metsger
- Aaron BirklandDavid Wilcox
- A. Soroka
- Michael Durbin
- Unknown User (acoburn)
- Audrey Templeton
- Don Richards
- Bethany SeegerDaniel Davis
- Mark Jordan
- Justin Simpson
- Yinlin Chen
- Benjamin Armintor
Related
...
- Finish: Initial Requirements
- Two flavours of import/export effort; RDF and binaries vs BagIt Bags
- Workplan and timelines
- Sprint scheduling
- August 8-19, 2016
- Developers
- Nick Ruest
- Esmé Cowles
- Michael Durbin (Maybe)
- A. Soroka (Maybe)
- Testing and validation
- Documentation
- Sprint scheduling
Minutes
Workplan and Timelines
- Sprint 1 changed to start August 29 due to people being unavailable for the 8th
- Developers
- Nick
- Esme - Nick will follow up
- Mike
- Ben
- Testing/validation
- Josh
- Mike
- Youn- Nick will follow up
- Nick
- Yinlin
- Bethany
- Documentation
- Youn
- Nick
- Josh
- Developers
Requirements
External systems
- Support import from and export to a TBD list of external systems.
- Already discussed
- Add Archivematica - Justin
- Add LOCKSS - Mark J
General
- Support transacting in Fedora-compliant RDF
- What do we mean by Fedora-compliant?
- Strike unless/until someone clarifies the meaning
- Support allowing the option to include Binaries
- No issues
- Support references from exported resources to other exported resources
- Important but challenging requirement
- Is this restricted to subtree resources?
- Need clarification on this point
- Support transacting in BagIt bags
- No issues
- Support import into a non-existing Fedora container
- Split into 2 requirements
- With same relative path
- With a different relative path
- Merge 5, 6, and 7?
- Split into 2 requirements
- Support import into an existing, empty Fedora container
- Same issues as 5
- Support import into an existing, non-empty Fedora container with various policies: add, overwrite, delete, version, skip
- Same issues as 5
- Support export of resource versions
- No issues
- Support import of resource versions
- No issues
- Support export of resource and its "members" based on the ldp:contains predicate
- No issues
- Support export of resource and its "members" based on a user-provided membership predicate
- No issues
- Support recursive RDF insert/updates with LDP Indirect Container specified POST (and PUT / PATCH?) (ref: FCREPO-2042)
- Non-RESTful - impacting many resources by interacting with one
- Could be done client-side using transactions
- Makes more sense with PATCH than POST or PUT
- Can we put this aside for now pending further discussion?
- Not a priority for the first sprint
- Consider import/export performance as is possible under the assumption that this work is done via the REST interface
- This is not a requirement, just a recommendation
- We would need numbers to work against in order to turn this into a requirement
- Needs more discussion
Round-Tripping
- Support preservation of dates during round-tripping
- No issues
- Support preservation of version snapshots during round-tripping
- No issues
- Will be challenging to implement
- The URIs of the round-tripped resources must be the same as the original URIs
- No issues
- Note: within Fedora’s existing capabilities
- Support lossless round-tripping. (ie, if you export a resource, delete that resource and import there is no difference from if you had never performed any of those operations).
- No issues
- No difference = no semantic difference
- There would still be an audit trail
Bag-It
- The structure and scope of accepted and produced BagIt bags must be configurable (resource)
- This is client-side - a script will pull the appropriate profile and assemble a bag
- Unambiguously support linking between resources within a bag, and from resources in the bag to resources outside the bag
- Is there already an assumed requirement that bags contain multiple resources?
- We should start with single resource bags as an initial goal
- This feature will not be very useful to some people if we cannot support multi-resource bags
- Needs more discussion at the beginning of the sprint (and during the sprint)
- Is there already an assumed requirement that bags contain multiple resources?
- Nick will send out a Doodle poll to nail down a call on the 29th for the beginning of the sprint