-
Notifications
You must be signed in to change notification settings - Fork 0
Issues: OCFL/Use-Cases
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Application Profiles
Component: Extension
Confirmed: In-scope
Use case will be included in the upcoming version of the spec or implementation notes.
Large Inventory.json files
Component: Specification
Confirmed: Out-of-scope
Use case will not be included in the upcoming version of the spec or implementation notes.
#48
opened Nov 5, 2023 by
awoods
Collapsing OCFL Object Versions
Component: Specification
Confirmed: In-scope
Use case will be included in the upcoming version of the spec or implementation notes.
OCFL as a formal standard?
Component: Specification
Confirmed: Out-of-scope
Use case will not be included in the upcoming version of the spec or implementation notes.
#45
opened Sep 22, 2023 by
zimeon
Support physical file-level deletion
Component: Specification
Confirmed: In-scope
Use case will be included in the upcoming version of the spec or implementation notes.
OCFL Object Forking
Component: Specification
Confirmed: In-scope
Use case will be included in the upcoming version of the spec or implementation notes.
Package per version storage
Component: Specification
Confirmed: In-scope
Use case will be included in the upcoming version of the spec or implementation notes.
Flagging file loss/corruption
Component: Validation
Confirmed: In-scope
Use case will be included in the upcoming version of the spec or implementation notes.
ProTip!
Add no:assignee to see everything that’s not assigned.