Page History

...

Fedora stores system metadata about the binary (image.tiff) in a JSON file that contains 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. The . 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 file is documented later in this documentheader 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 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 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 the name of the binary's ACL with the appropriate extension, ".json". ("image.tiff~fcr-acl.json", in this example)

Fedora Atomic Resource - Container

A Fedora container resource is effectively an empty directory with LDP-defined behaviors depending on its "interaction model" (i.e. type: basic, direct, indirect), and associated metadata, along with an optional ACL. Since OCFL does not support empty directories as valid objects, there is no direct OCFL analogous object for a Fedora container atomic resource.

[object root]
    ├── 0=ocfl_object_1.0
    ├── inventory.json
    ├── inventory.json.sha512
    └── v1/
        ├── inventory.json
        ├── inventory.json.sha512
        └── content/
            ├── .fcrepo/
            │   ├── fcr-root.json           <-- Required "header" file holding system metadata about the binary. See description below.
            │   └── fcr-root~fcr-acl.json   <-- Optional, only present if this Fedora resource has its own ACL.
            ├── fcr-container.nt        <-- Required "binary description". See description below.
            └── fcr-container~fcr-acl.nt         <-- Optional, only present if this Fedora resource has its own ACL.

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.

Basic OCFL Structure

The following is an example of an OCFL object that contains one version, consisting of a hierarchy of files and directories. For more information on OCFL, see the specification.

...