/
Overview of cModels & sDefs

Overview of cModels & sDefs

Mapping Ruby Model Names to cModel Pids

This is how Ruby Model names will map to cModel pids (not currently implemented)

Hydra::StaticImage

>>

hydra-cModel:staticImage

Hydra::FileAsset

>>

hydra-cModel:fileAsset

Hydrangea::Dataset

>>

hydrangea-cModel:dataset

Hydra::Article

>>

hydrangea-cModel:article

MyArticle

>>

local-cModel:myArticle

Primitives

A primitive is a fundamental atom object that bears an actual file payload. Most Hydra primitives will use the fileAsset cModel, putting their payload into a datastream called "content".

Current

hydra-cModel:fileAsset (formerly genericContent)
hydra-cModel:staticImage
hydra-cModel:jpeg2000

Posible Additions

hydra-cModel:dcAsset
hydra-cModel:modsAsset
hydra-cModel:modsImage

Higher Level Objects

Current

hydrangea-cModel:dataset
hydrangea-cModel:article

Possible Additions

stanford-cModel:etd

Service Definitions

Like a Java interface – a Service Definition (sDef) is just a list of methods/behaviors

Current

hydra-sDef:genericContent

methods:

  • content – returns the content "payload" of the object

hydra-sDef:genericImage

methods:

  • thumbnail
  • screen
  • max

Possible Additions

hydra-sDef:dynamicImage

methods:

  • region
  • resize

Related content

Core Hydra Ruby Models
Core Hydra Ruby Models
More like this
Samvera objects, content models (cModels) and disseminators
Samvera objects, content models (cModels) and disseminators
More like this
Hydra content models and disseminators
Hydra content models and disseminators
More like this
Community Content Modelling
Community Content Modelling
More like this
ContentMD discussions
ContentMD discussions
More like this
Don't call it a 'content model'!
Don't call it a 'content model'!
More like this