-
Notifications
You must be signed in to change notification settings - Fork 63
Models in the Wild
Share your working ActiveFedora Models here. Please add categories as necessary.
Example of a thoroughly commented Model: https://github.com/projecthydra/active_fedora/blob/master/spec/samples/special_thing.rb
Model Name Description Relevant Use Case(s)
If your code is in a public repository, provide
- link to the model
- links to any tests for the model
- links to any fixture objects that are instances of the model
If your code is not in a public repository, provide a link to gist
- copy of the model
- copies of any tests for the model
- copies of any fixture objects that are instances of the model
In both cases, include any code/info about datastreams, OM terminologies, etc.
Video | Image | Generic File | Policy Object | Book | Item | Set | Collection | Workflow Object | ETD | Journal Article Preprint
From dor-services at Stanford: You can see many examples of models used for our digital object workflow at https://github.com/sul-dlss/dor-services/tree/master/lib/dor/models. ActiveFedora models include Item, Set, and Collection, and other model behaviors are mixed in via Describable, Embargoable, etc.
- Admin Policy Object (APO): model fixture
- Item: model fixture
- Set: model
- Collection: model
- Workflow object: model
From Hydrus at Stanford: You can see model definitions at https://github.com/sul-dlss/hydrus/tree/master/app/models/hydrus. Notice that many of these are extensions of the models declared in dor-services, e.g., the APO model extends the dor-services APO model.