...

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

1. Support recursive RDF insert/updates with LDP Indirect Container specified POST (and PUT / PATCH?) (ref: FCREPO-2042)
2. Supports lossless roundtripping.  (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).
   1. dates must be preserved through the roundtrip
   2. version snapshots must be preserved through the roundtrip
3. Import/Export must support transacting in Fedora-compliant RDF along with optional Binaries
4. Import/Export must support transacting in BagIt bags
5. The structure and scope of accepted and produced BagIt bags must be configurable (resource)
6. 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>
7. After round-tripping resources, the URIs of the newly ingested resources must be the same as the original URIs

...