Short answer
The deterministic ZIP contains ten members: mets.xml, premis.xml, a bilingual README, a CC BY 4.0 attribution file, five reusable data files and checksums-sha256.txt. METS fileSec inventories seven preserved files by relative path, IANA media type, byte size and SHA-256, while its logical structMap groups data and documentation and points to every file exactly once. A METS 2.0 mdRef links the complete external PREMIS record without using XLink, which METS 2 removed. PREMIS records seven File Objects with matching original names, formats, sizes and fixity; one successful metadata-creation Event; publisher and generator Agents; and one CC BY 4.0 Rights statement linking every Object. Both XML records validate offline against byte-pinned official XSD snapshots from immutable public source commits. The bundle also checks all paths, digests, 37 CSV rows, 37 JSON Lines records, ZIP order, fixed timestamps and file modes. The ZIP is a deterministic transfer wrapper, not a METS-defined archive format. The package has no DOI and does not claim repository registration, external ingest, third-party certification, institutional endorsement or a digital signature.
Download the ZIP and checksums-sha256.txt, verify the outer ZIP digest, extract without changing relative paths, then validate mets.xml and premis.xml against the cited official XSD versions. Confirm that all seven METS file entries, seven PREMIS File Objects, Event links and Rights links match the extracted bytes before repository ingest.
What to look for before choosing
- Complete U+3105 through U+3129 coverage in canonical 37-row CSV and equivalent JSON Lines
- METS 2.0 fileSec, logical structMap and external PREMIS 3.0 mdRef with no XLink dependency
- Seven PREMIS File Objects, one generation Event, two Agents and one CC BY 4.0 Rights statement
- Official byte-pinned METS 2.0 and PREMIS 3.0 XSD validation performed offline
- Deterministic ten-member ZIP with per-file and outer SHA-256 checksums
A practical decision process
- Open the bilingual package guide and download the ZIP plus checksums-sha256.txt.
- Verify the published outer SHA-256 before extracting the transfer wrapper.
- Validate mets.xml and premis.xml against the exact cited official XSD versions.
- Compare every METS file and PREMIS Object path, media type, byte size and SHA-256 with the extracted payload.
- Review the PREMIS Event, Agents, Rights statement and your local repository policy before ingest.
Quick comparison
| Need | What to check | Why it matters |
|---|---|---|
| Repository inventory and structure | METS 2.0 fileSec inventories seven files and structMap points to every file exactly once | Repository tooling can discover payload and documentation roles without guessing from filenames |
| Preservation provenance and rights | PREMIS 3.0 links seven File Objects to one Event, two Agents and one Rights statement | Fixity, creation provenance and CC BY 4.0 permissions remain explicit at transfer |
| Byte-level verification | METS and PREMIS values match local paths, media types, byte sizes and SHA-256 digests | A repository can reject an incomplete or altered payload before ingest |