...
Single resource bagsStatus colour Blue title Phase 2
The structure and scope of accepted and produced BagIt bags must be configurable (resource)Status colour Blue title Phase 2 - Clarification: structure relates to required and optional tagfiles in the bag
- Clarification: scope relates to contents of the bag, e.g. single object or object and all members based on specific membership predicate
Multi-resource bagsStatus 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 bagStatus subtle true colour Blue title Phase 3 - 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>
Verification Tool
Verify same number of resources on disk as in fcrepoStatus colour Blue title Phase 2
Verify same number of resources in fcrepo as on diskStatus colour Blue title Phase 2
Verify same checksum for binariesStatus colour Blue title Phase 2
Verify same triples for containersStatus colour Blue title Phase 2
Record which resources have been verifiedStatus colour Blue title Phase 2
Verify fcrepo to fcrepoStatus colour Blue title Phase 2
Verify disk to diskStatus colour Blue title Phase 2
Use generated config file as sole inputStatus colour Blue title Phase 2 Status colour Blue title Phase 2
Considerations
- Import/export performance as is possible under the assumption that this work is done via the REST interface
...