Page History

...

1. Introductions
2. Logistics
   1. Virtual daily stand-ups?
   2. IRC? 
   3. Conference calls?
   4. Email check-in?
   5. Sprint retrospective?
3. Phase 1 priorities
   1. Support transacting in RDF
      
   2. Support allowing the option to include Binaries
   3. Support references from exported resources to other exported resources
   4. Support import into a non-existing Fedora container
   5. Support export of resource and its "members" based on the ldp:contains predicate
   6. The URIs of the round-tripped resources must be the same as the original URIs
4. Assign work

Minutes

1. Introductions
2. Logistics
   1. Virtual daily stand-ups on IRC by 10 am ET
      1. What you did yesterday
      2. What you plan on doing today
      3. Blockers
   2. Conference calls on this line if needed
   3. Sprint retrospective on Sep 9 at 3:30 pm ET
      1. What worked
      2. What didn’t work
      3. Try to wrap up by Thursday
3. Phase I Priorities
   1. Camel serializer
      1. Supports transacting in RDF and option to include binaries
      2. Listens for messages on queues; need to run indexer before running export
      3. Basic case: dump to disk and gzip
      4. Need to parse RDF to figure out information required for import, e.g., base url for repository
      5. Provides options for RDF serialization supported by REST API and supply default serialization
4. Looking ahead to Phases II and III
   1. Versions
      1. JCR versioning will include any version of parent
      2. For Camel serializer, does Fedora send out a message when it creates a version?
      3. Possible way forward is to consider basic case as export of current version and then to build in capability to export version that is not the current version with additional metadata
      4. Need to consider layout of versions on disk
      5. Fedora API specification is leaning towards making versions first-class resources
   2. Bags
      1. Client tool
      2. Generate from REST API calls to repository or from filesystem?
      3. Only LDP basic containers? Connected graph from root; basic containers if not starting at root
      4. Stakeholder use cases include exporting individual resources, not entire graph, and being able to generate resources that can be imported into other repositories (such as APT) from documented export formats
5. Design considerations
   1. Camel may make bar too high for users; code may need to be re-implemented
   2. Some discussion of using bash or python for prototyping; final consensus was to use java
   3. Testing plan should define success, describe tests that will be run, and include test data
   4. Integration test suite in java; unit tests included with utilities
   5. Logging
6. In-flight tickets
   1. FCREPO-2127: Document how the Camel RDF Serializer exports content to disk
   2. FCREPO-2128: Review Camel RDF Serializer implementation
   3. FCREPO-2129: Create import-export github repository in the fcrepo4-labs organization
   4. FCREPO-2130 (close out FCREPO-1990): Create skeletal import client utility
   5. FCREPO-2131: Create skeletal export client utility
   6. FCREPO-2132: Create a test plan
   7. FCREPO-2133: Create sample test dataset
   8. FCREPO-2134: Document sprint resources
   9. FCREPO-2135: Create user documentation
   10. FCREPO-2136: Create Import/Export wiki documentation

Meeting 02 -