Skip to content
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

Create fixture for Moab example or else update example for data we have #665

Open
zimeon opened this issue Dec 5, 2024 · 3 comments
Open
Assignees
Labels
Editorial Editorial issues (no changes to intent)

Comments

@zimeon
Copy link
Contributor

zimeon commented Dec 5, 2024

We should have a fixture for https://ocfl.io/draft/spec/#example-moab-in-ocfl or else update example for data we have

@zimeon zimeon added the Editorial Editorial issues (no changes to intent) label Dec 5, 2024
@zimeon
Copy link
Contributor Author

zimeon commented Dec 5, 2024

@julianmorley to check to see whether he has the raw data

@julianmorley
Copy link
Contributor

Yes, I have. I need to clear it to make sure it's releasable.

@zimeon
Copy link
Contributor Author

zimeon commented Jan 30, 2025

Julian will create a new object for inclusion in draft/v2 and in the fixtures. This will still generate a warning in validation because of the zero padded version directories used by MOAB. We will add a note to this effect in the example.

The Moab Design for Digital Object Versioning https://journal.code4lib.org/articles/8482#4.1.2

Each object-level folder is subdivided into version folders, named v0001, v0002, etc. The v0001 folder holds the initial version of the digital object. Additional sub-directories of the form “v” hold the files of subsequent versions of the object. The directory names are left padded with zeros so that the directory pathname is 5 characters long and will sort into the correct chronological sequence. Each version folder contains a data folder and a manifests folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Editorial Editorial issues (no changes to intent)
Projects
None yet
Development

No branches or pull requests

2 participants