Call in details:

• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • You may also call in using the VoIP dialer from a web browser, or Android/iOS apps
• IRC:
  
  • Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #fcrepo on irc.freenode.net

Sprinters

• Developers

  • Danny Bernstein

  • Ben Pennell

  • Michael Durbin

  • Esmé Cowles

  • Joshua Westgard

  • Longshou Situ

• Testing and Documentation

  • Kieran Etienne
  • Harsha Ummerpillai
  • Youn Noh
  • Jim Coble
  • Bridget Almas

Objectives

The objectives of sprint-04 are to:

1. Test compatibility of exported Bags with:
   1. APTrust
   2. Perseids
   3. Archivematica 
2. Test compatibility of import/export round-tripping between community and alternate Fedora implementations
3. Import/export of versions
   1. Note: Want to keep upcoming Memento API alignment
4. Lossless round-tripping (particularly dates)
   1. other round-tripping issues, e.g.:  FCREPO-2429 - Semantic differences between exports Open
5. Resolve import bugs that were reported from v0.1 testing
6. Verification tool
   1. Unicode-escaping when resources are exported leads to mismatch when those resources are re-imported
   2. Users are confused by the tool output
   3. Lower priority:
      1. Gracefully handling server-managed triples and timestamps that can't be updated
      2. Verifying Fedora-to-Fedora and disk-to-disk
      3. Anything special required for Bags?
7. Lower-priority
   1. Importing into non-empty containers
      1. There may be several facets to this: importing into a container that already exists (other children of the same resource already exist) seems very useful, but syncing with an existing resource may be much more complex.  We should support the easy things, and be careful when tackling the more complex scenarios to maintain a good scope with stakeholder input.
   2. Maintain links in Bags with links to resources outside of Bags
      1. Revisit whether this is still an issue given the current Bag export/import functionality
   3. Incremental diffs of Bags, relating to sending updated Bags to preservation services, not re-transmitting large files that haven't changed, and not overwriting good content with content that's been corrupted, etc.
      1. Interesting functionality once the other functionality is solid

Resources

1. Design - Import - Export
2. Applications / tools for using and testing the import export
   1. Fedora 4.7.2 one-click (jetty-console jar : https://github.com/fcrepo4/fcrepo4/releases/tag/fcrepo-4.7.2
   2. Fedora 0.1.0 Import / Export utility : https://github.com/fcrepo4-labs/fcrepo-import-export/releases/tag/fcrepo-import-export-0.1.0
   3. Fedora 0.0.3 Import / Export verification utility : https://github.com/fcrepo4-labs/fcrepo-import-export-verify/releases/tag/0.0.3

   4. Steps for using the above

      Click here to expand...

      # Download the utility:
      https://github.com/fcrepo4-labs/fcrepo-import-export/releases

      # Have a running Fedora
      If you do not have a Fedora to test with, you may want to start up the "one-click run":
      https://wiki.duraspace.org/display/FEDORA4x/Quick+Start#QuickStart-One-ClickRun

      # Have data in your Fedora
      If you do not have data in your Fedora, you will likely want to load some of your own or one of the existing example datasets:
      https://github.com/fcrepo4-labs/fcrepo-sample-dataset/tree/master/additional_datasets

      Although there are minimal instructions in the readme linked above, if you run into issues loading any of these datasets, I would be happy to help... the possibility of issues arising is not inconceivable.

      # Export your data as Bagit bags
      Here are some minimal instructions:
      https://github.com/fcrepo4-labs/fcrepo-import-export/blob/master/README.md#running-the-importexport-utility-with-a-bagit-support

      To export APTrust-style bags, use the ''--bag-profile aptrust" argument when running the utility.

3. Import / Export utility tickets

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

4. Import / Export verification tickets

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Meetings

Standups

IRC Template

[Import/Export Standup]
Finished yesterday: 
  {ticket titles and associated JIRA links}
  {and/or brief textual description}
Working on today:
  {ticket titles and associated JIRA links}
  {and/or brief textual description}
Blockers:
  {brief textual description}