
Hyku’s Underlying Metadata
One of the reasons to move to Hyrax/Hyku from legacy systems is the underlying RDF-based Fedora-4 layer, so it is important to understand what this means for your metadata and data as a whole. Work at Indiana University has created two great documents to help you understand Fedora’s metadata and a switch from XML to RDF:
- Fedora Metadata Storage Philosophy (PDF, 2007)
https://wiki.dlib.indiana.edu/spaces/flyingpdf/pdfpageexport.action?pageId=441 - The Semantics of Metadata: Avalon Media System and the Move to RDF (2017)
https://journal.code4lib.org/articles/12668
So while objects in Hyku have most of their metadata at the generic work level, available to view here, theres still quite a few things that exist at the Fedora level, some of which is shown here.
Below are the fields shown in a sample generic object in Hyku within the Fedora GUI.
| Prefix | Predicate |
|---|---|
| acl: | accessControl |
| dc: | creator |
| dc: | relation |
| dcterms: | dateSubmitted |
| dcterms: | isPartOf |
| dcterms: | modified |
| dcterms: | title |
| ebucore: | hasRelatedImage |
| ebucore: | hasRelatedMediaFragment |
| fedora: | created |
| fedora: | createdBy |
| fedora: | hasParent |
| fedora: | lastModified |
| fedora: | lastModifiedBy |
| fedora: | writable |
| iana: | first |
| iana: | last |
| ldp: | contains |
| ns001: | hasModel |
| ns002: | rights |
| ns003: | hasMember |
| ns005: | dpt |
| ns006: | objState |
| rdf: | type |
Bridge2Hyku Partners BEST-PRACTICES
metadata fedora samvera