-
In an archival repository based on OCFL there are multiple processes handling ingest, update (new versions), format validation (with ever improving tools that cover more formats as time goes on), and …
-
Currently, SHA-512 is used only in a minority of preservation settings as the fixity checking algorithm (see the 2017 [NDSA Fixty Survey Report](https://ndsa.org/documents/Report_2017NDSAFixitySurvery…
-
In response to @awoods request for comments, here is some feedback for your consideration:
* In 3.3, describe `.keep`. I'd suggest based on my experience as a BagIt author, that `.keep` is not an opt…
-
This task is to add the terms (if not their definitions) to section 2: Terminology.
-
I see two options:
1) With the spec as currently written there would need to be a note explaining that these are special cases where the existing file path cannot be the original filepath, it must …
-
I apologize in advance if this is not the best place to raise this question - if that is the case, please direct me to the more appropriate place (I did notice that there are a number of different ema…
-
Section 3.4.2 currently reads:
`Implementers may wish to store their file digests in a system external to their OCFL object stores at the point of ingest, to further safeguard against the possibili…
-
Apologies, I'm reading the spec and noticed a few typos/bits I didn't understand. Feel free to discard.
Para 2: "Nor can these attributes be vaidated" = 'validated'
[note, not my place, but woul…
-
Follows on decision made in #52
-
Should we allow for a Object storage layout disposition hint, along the lines of '1=pairtree_1.0', etc