-
We discussed the definition for Objects in today's community call. It was suggested to move this to GH as a next step. I'm not able to branch and pr on the repo atm so I will post this as an issue her…
-
Discussed on [2018-07-18 editors' call](https://github.com/OCFL/spec/wiki/2018.07.18-Editors'-Meeting), we propose the adopt the following policy in order to get more content up quickly before the in-…
-
An institution decides that it will employ an institutional repository system that does not implement OCFL, but that it wishes to use OCFL for long-term preservation. They implement OCFL on their long…
-
From a preservation/validation perspective, would it be appropriate to require the existence of a plain-text inventory schema at the Storage Root?
-
Before diving too far into the details of the specification, agreement on the top-level outline would be helpful.
-
... or not?
-
Currently there is an issue with inventory.jsonld file where it does not support file renaming. We need to resolve this.
Relates to ocfl/Use-Cases#26
-
A particularly poorly-written OCFL library was not built to observe the OCFL version stored in the root of the filesystem, and has written an object to the filesystem using the older specification. An…
-
The reason this is so important is because containers either have a single entrypoint, or a programatically predictable (internally modular) set of entrypoints (e.g., see [https://sci-f.github.io](htt…
vsoch updated
5 years ago
-
Some institutions may have very large files that are inconvenient or impossible to store as single files within and OCFL digital object. It would always be possible to split files into multiple parts …