Title (Goal) | Support Fedora 3-style object classes (content models) |
---|---|
Primary Actor | Repository architect & implementer |
Scope | Data architecture and access |
Level | High |
Story (A paragraph or two describing what happens) | We want to implement a Fedora repository using our own client. Since we are not using Islandora or Hydra frameworks to manage object classes, therefore the solution in Fedora 3 would be to set up content models that can be attached via "hasModel" relationships to objects. If we decide to use F4 for our repository, we need a similar facility to rely on at repository level. Specific F3-style use cases:
Enforce access policies and other relationships. Objects attached to "image resource" content model MAY NOT be attached to "text resource" or "multimedia resource" content models and MAY have a "isResourceOf" relationship with an object with "manufact" content model. DC properties of objects with "published for web" content model are readable by all. These goals are determining for whether we may be able to implement F4. |