Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This article describes the role of the “Cluster” named graph in MMS5. Layer 1 forbids arbitrary writes to this graph and instead exposes a set of LDP endpoints.

This named graph holds organizational objects that are global to the deployed MMS5 cluster. Specifically, a Project is the container for version-controlled data (similar to a git repository), a Collection is readonly view that selects the union of any number of Refs when queried, and an Org is an entity that owns Projects or Collections.

Linked Data Platform (LDP)

The following nested bulleted lists describes the LDP semantics of various HTTP operations available on Cluster objects.

  • /projects

    • GET – Enumerates all projects along with their public annotation properties.

  • /projects/{PROJECT_ID}

    • PUT – Creates a new project.

      • Required properties: mms:org {ORG} and dct:title "{PROJECT_TITLE}"

    • GET – Reads public annotation properties of the given project.

    • PATCH – Updates an existing project.

    • DELETE -- Deletes a project.

  • /collections

    • GET – Enumerates all projects along with their public annotation properties.

  • /collections/{COLLECTION_ID}

    • PUT – Creates a new collection.

      • Required properties: mms:org {ORG} and dct:title "{COLLECTION_TITLE}"

    • GET – Reads public annotation properties of the given project.

    • PATCH – Updates an existing project.

    • DELETE -- Deletes a project.

  • /orgs

    • GET – Enumerates all orgs along with their public annotation properties.

  • /orgs/{ORG_ID}

    • PUT – Creates a new org.

      • Required properties: dct:title "{ORG_TITLE}"

    • GET – Reads public annotation properties of the given org.

    • PATCH – Updates an existing org.

    • DELETE -- Deletes an org.

  • No labels