...
Fedora stores system metadata about the binary (image.tiff) and the binary's description (currently, image.tiff/fcr:metadata) in respective JSON files that contain elements such as the creation date and creator, as well as its interaction model (i.e. type), whether the object is an archival group, etc. Additionally, Fedora resources can optionally have their own ACLs, which if present also have their own JSON header file. The full contents and format of the JSON header file and ACLs are detailed later in this document.
Naming conventions
- The binary: the filename provided during ingest of the binary is retained in the OCFL persistence. ("image.tiff", in this example)
- The binary's description: the filename of the binary's description is the name of the binary with the addition of the suffix, "~fcr-desc.nt". ("image.tiff~fcr-desc.nt", in this example)
- The binary's ACL: the filename of the binary's ACL is the name of the binary with the addition of the suffix, "~fcr-acl.nt". ("image.tiff~fcr-acl.nt", in this example)
- The binary's header file: the filename of the binary's header (JSON) file is is the name of the binary with the addition of the extension, ".json". ("image.tiff.json", in this example)
- The binary description's header file: the filename of the binary description's header (JSON) file is the is the name of the binary description with the appropriate extension, ".json". ("image.tiff~fcr-desc.json", in this example)
- The binary ACL's header file: the filename of the binary's ACL's header (JSON) file is is the name of the binary's ACL with the appropriate extension, ".json". ("image.tiff~fcr-acl.json", in this example)
...