...

Sprinters

Developers

• Esmé Cowles 

  Status
  title Phase 1

• Benjamin Armintor

  Status
  title Phase 1

• Nick Ruest

  Status
  title Phase 1

  Status
  colour Blue title Phase 2

• Michael Durbin

  Status
  title Phase 1

  Michael Durbin (Maybe)

Testing and Validation

• Michael Durbin

  Status
  title Phase 1

• Joshua Westgard

  Status
  title Phase 1

• Justin Simpson

  Status
  title Phase 1

• Mark Jordan
• Youn Noh

  Status
  title Phase 1

• Yinlin Chen

  Status
  title Phase 1

• Nick Ruest

  Status
  title Phase 1

  Status
  colour Blue title Phase 2

• Bethany Seeger

  Status
  title Phase 1

Documentation

• Youn Noh

  Status
  title Phase 1

• Joshua Westgard

  Status
  title Phase 1

• Nick Ruest

  Status
  title Phase 1

  Status
  colour Blue title Phase 2

Use cases

1. Transfer between Fedora and external preservation systems, such as APTrust, MetaArchive, LOCKSS, DPN, Archivematica, etc
2. Package [Export] the content of a single Fedora container and all its descendant resources
3. Transfer between fedora instances or (more generally) from Fedora to an LDP archive
4. load [Import] the contents of a package into a specified container.
5. Round-tripping resources in Fedora in support of backup/restore
   1. A start has been made on this in FCREPO-1990; 
   2. The implementation referenced in the above ticket is not dead, though not actively being worked on at the moment; pull requests welcomed (though others may well wish to take it in a different direction).
   3. A rebuilder that:
      1. Is not solely dependent on a intact backup of the repository index
      2. Works off shredded serializations that can be supported with file preservation techniques
      3. Can recover as much as possible of a repository in the face of integrity issues (supports partial recovery)
      4. Supports gathering copies of the shreds (serializations) from multiple sources to recover a repository
6. Round-tripping resources in Fedora in support of Fedora repository version upgrades
7. Batch loading arbitrary sets of resources from metadata spreadsheet and binaries (may well be difficult – or not worth it – to try to generalize such a feature).
8. Import or export containers or binaries using add, overwrite, or delete operations. Configure the data model and the source and the target for each resource that will be updated. Allow target containers to be non-empty before import and source containers to be non-empty after export. Maintain ordering, etc. Version or backup to restore. Examples: add issues to a publication; add fragments to a manuscript; add data sets to a longitudinal study; add time-series images from telescopes; remove resources determined to be under copyright; release resources after restrictions on access have expired.

Requirements

External Systems

1.  subtle

   Status
   true colour Blue title Phase 2

   Support import from and export to a TBD list of external systems.
   1. APTrust - University of Maryland (Joshua Westgard)
   2. Archivematica - Artefactual Systems (Justin Simpson)
   3. LOCKSS - Simon Fraser (Mark Jordan)
   4. MetaArchive - Penn State (Ben Goldman)

General

1. Status
   colour Blue title Phase 1

   Support transacting in RDF
   
2. Blue

   Status
   colour
   title Phase 1

   Support  Support allowing the option to include Binaries
3. Blue

   Status
   colour
   title Phase 1

   Support  Support references from exported resources to other exported resources

4. Status
   subtle true colour Blue title Phase 2

   Support  Support transacting in BagIt bags
5. colour

   Status
   Blue title Phase 1

   Support  Support import into a non-existing Fedora container
6. true

   Status
   subtle
   colour Blue title Phase 2

   Support  Support import into an existing, empty Fedora container

7. Status
   subtle true colour Blue title Phase 3

   Support import into an existing, non-empty Fedora container with various policies: add, overwrite, delete, version, skip

8. Status
   subtle true colour Blue title Phase 3

   Support export of resource versions

9. Status
   subtle true colour Blue title Phase 3

   Support import of resource versions
10. Blue

    Status
    colour
    title Phase 1

    Support  Support export of resource and its "members" based on the ldp:contains predicate

11. Status
    subtle true colour Blue title Phase 2

     Support export of resource and its "members" based on a user-provided membership predicate
12. Support recursive RDF insert/updates with LDP Indirect Container specified POST (and PUT / PATCH?) (ref: FCREPO-2042)

...

1. Status
   subtle true colour Blue title Phase 3

   Support preservation of dates during round-tripping 

2. Status
   subtle true colour Blue title Phase 3

   Support preservation of version snapshots during round-tripping 

3. Status
   colour Blue title Phase 1

   The  The URIs of the round-tripped resources must be the same as the original URIs

4. Status
   subtle true colour Blue title Phase 3

   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).

BagIt

1. Status
   subtle true colour Blue title Phase 2

   Single  Single resource bags
   
2. true

   Status
   subtle
   colour Blue title Phase 2

   The  The structure and scope of accepted and produced BagIt bags must be configurable (resource)
   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

3. Status
   subtle true colour Blue title Phase 3

   Multi-resource bags

4. Status
   subtle true colour Blue title Phase 3

   Unambiguously support linking between resources within a bag, and from resources in the bag to resources outside the bag
   1. e.g. for bagged resources A and B, if A contains statement <A> myns:rel <B>, then it is unambiguous that B is a resource in the bag.  Suppose some archive ingests the bag and exposes its contents as web resources with URIs P and Q. If the archive preserves intra-bag links, resource P will have statement <P> myns:rel <Q>.  Likewise, if A contains external link <A> myns:rel2 <http://example.org/outside/the/bag>, then an archive that preserves links will have <P> myns:rel2 <http://example.org/outside/the/bag>

...