Skip to content

Models Hydra Conventions

no-reply edited this page Nov 29, 2012 · 4 revisions

Hydra Modeling Conventions

See the duraspace hydra wikis for information at the architecture level: http://github.com/projecthydra/hydra-head/wiki

Reference info on the Duraspace Hydra Wiki

Hydra objects, content models(cModels) and disseminators

Don’t Call it a Content Model

genericContent cModel

  • descMetadata (required): Descriptive Metadata like MODS or DC. MODS is recommended
  • rightsMetadata (recommended): Rights, License, and Permissions information. Hydra rightsMetadata XML is recommended.
    h4. Understanding Parts (Where will my uploaded files go?)
Primitives contain actual files

A primitive is a fundamental atom object that bears an actual file payload. They are single, (near-) universal content types which may either stand-alone or be incorporated into higher order content types (in a book or ETD, e.g.).

Higher Level Objects

Higher Level Objects represent higher-level, molecular objects that may have primitives and/or other Higher-level objects as children.

Relationships

isPartOf — Hydra reserves this predicate for use in representing part-whole relationships between objects. This occurs most often when representing which Primitives (ie. an uploaded PDF) are part of a Higher Level object (ie. a MODS Article)

For Further Information

See Reference for more links.