...
This section outlines how the Fedora 3 objects associated with the UNSW repositories are conceptually mapped to Fedora 4 nodes.
Fedora 3 Object and Datastream properties
Mapping Fedora 3 Object Properties to Fedora 4
...
Fedora 3 | Fedora 4 | Example | Note | |||||||||
PID | PID | dc:identifier | resdatac:1 | Legacy Fedora 3 identifier | ||||||||
State | state | access:objState | Active | Using solution as described in
| ||||||||
Label | label | dc:title | Record title | |||||||||
Creation Date | CREATED | premis:hasDateCreatedByApplication | 2014-01-20T04:34:26.331Z | premis:hasDateCreatedByApplication is used because fedora:created is not user-modifiable. | ||||||||
Last Modified Date | lastModifiedDate | fedora:lastModified | 2014-01-20T05:39:08.601Z | Date of migration is to be treated as a “modification”. | ||||||||
Owner Identifier | ownerId | ms21:owner | z2212222 | The creator of the object |
Mapping Fedora 3 Datastream Properties to Fedora 4
...
Fedora 3 | Fedora 4 | Example | Note | |||||||||
DSID | ID | identifier or dc:identifier | MODS | This is the legacy Fedora 3 datastream identifier | ||||||||
State | state | access:objState | Active | Using solution as described on
| ||||||||
Control Group | CONTROL_GROUP | N/A | X | Migration is deemed unnecessary | ||||||||
Versionable | VERSIONABLE | fedora:hasVersions | true | The “VERSIONABLE” property of Fedora 3 is not semantically equivalent to Fedora 4’s hasVersions data property. The mapping proposed is intended to enable migration of Fedora 3 data but will no not be used after migration. | ||||||||
Label | LABEL | dc:title | MODS Metadata | |||||||||
Creation Date | CREATED | premis:hasDateCreatedByApplication | 2014-01-20T04:34:26.331Z | Intended to enable migration of Fedora 3 creation dates. premis:hasDateCreatedByApplication is used because fedora:created is not user-modifiable. | ||||||||
Last Modified Date | N/A | fedora:lastModified | 2014-01-20T05:39:08.601Z | Fedora 3 uses “Creation date” for last modified date for datastream. | ||||||||
Mime Type | MIMETYPE | fedora:mimeType | text/xml | |||||||||
Size | SIZE | premis:hasSize | 50000 | Automatically handled by Fedora 4 | ||||||||
Alternate ID | AltIds | premis:hasOriginalName | sample_file.pdf | Automatically handled by Fedora 4 | ||||||||
Checksum Type | checksumType | MD5 | SHA1 | Fedora 4 combines checksum type and checksum in one field on fedora:digest property | ||||||||
Checksum | checksum | fedora:digest | Fedora 3 example: b4df41775c142aa18518d6586a8193c8e0b7dc96
Fedora 4 example: urn:sha1:b4df41775c142aa18518d6586a8193c8e0b7dc96
| Automatically added by Fedora 4 | ||||||||
Format URI | formatURI | N/A | N/A | This field is not used |
Note: all data and object properties under the official Fedora 4 namespace cannot be modified via Fedora 4 REST API.
Objects and Datastreams Namespaces for Fedora 4
...
Namespace | URL |
fedora | |
dc | |
| access | http://fedora.info/definitions/1/0/access/ |
| premis | http://www.loc.gov/premis/rdf/v1# |
Fedora 4 data model for ResData Dataset
Figure 1 below presents a top level view of the Fedora 4 data model for ResData . Dataset
Figure 1: Fedora 4 data model for ResData
...