...
This section outlines how the Fedora 3 objects associated with the UNSW repositories are conceptually mapped to Fedora 4 nodes.
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 | Use of fedora:status is preferred but not yet supported. Expected to be addressed by Fedora 4.1.1. |
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 | Use of fedora:status is preferred but not yet supported. Expected to be addressed by Fedora 4.1.1. |
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.
Fedora 4 Namespaces
Namespace | URL |
fedora | |
dc |
ResData Namespaces
Namespace | URL |
bibo | |
owl | |
ms21 | http://www.unsworks.unsw.edu.au/ontology/preservation-metadata/ |
VITRO-ANDS | |
core | |
foaf | |
pcdm |
Fedora 4 data model for ResData
Figure 1 below presents a top level view of the Fedora 4 data model for ResData.
...
The ResData Fedora 4 data model is an adaptation of the PCDM model, integrated with a customised version of ANDS VITRO ontology. The resultant ontology consists mainly of the following classes:
Activities, Datasets, Parties (pcdm:Collection)
Activities, Datasets, and Parties are Fedora 4 container nodes of pcdm:Collection type, mainly intended to enable grouping of the three main ResData resource types, i.e. Activity, Dataset and Party. Fedora 4 URI structures for these pcdm:Collection containers are listed below:
Container name | URL |
Activities | /rest/activities |
Datasets | /rest/datasets |
Parties | /rest/parties |
Dataset (VITRO-ANDS:ResearchData, pcdm:Object)
The ResearchData class from the ANDS VITRO ontology is used to define the Dataset resource type in ResData. In the Fedora 4 model for ResData, all instances of the ResearchData class are also defined as nodes of pcdm:Object type with a number of data properties containing descriptive metadata, and object properties containing reference to other related ResData resources, such as Activity (vivo:ResearchActivity), Party (foaf:Person) and other Dataset resources. Figure 2 bellow illustrates the combined use of pcdm:Object and VITRO-ANDS:ResearchData classes to represent various ResData resource types.
Figure 2: ResData Dataset resource defined as pcdm:Object
Fedora 4 URI structures for ResData Dataset-related nodes are as below:
Description | URL |
Dataset | /rest/datasets/[dataset pairtree id] |
Access | /rest/datasets/[dataset pairtree id]/access |
Licence | /rest/datasets/[dataset pairtree id]/licence |
Methodology | /rest/datasets/[dataset pairtree id]/methodology |
Time Period | /rest/datasets/[dataset pairtree id]/timePeriod |
Retention Period | /rest/datasets/[dataset pairtree id]/retentionPeriod |
Subject | /rest/datasets/[dataset pairtree id]/subject |
Publication | /rest/datasets/[dataset pairtree id]/publication |
GEO | /rest/datasets/[dataset pairtree id]/geo |
Rights | /rest/datasets/[dataset pairtree id]/rights |
Storage | /rest/datasets/[dataset pairtree id]/storage |
ms21:PartyRelation
PartyRelation is a custom class for describing a user-specified relation between a Party and a Dataset. Instances of PartyRelation in the ResData Fedora 4 model are also defined as pcdm:Object type nodes.
Fedora 4 URI structures for the PartyRelation nodes are:
Description | URL |
Dataset | /rest/datasets/[dataset pairtree id] |
PartyRelation | /rest/datasets/[dataset pairtree id]/partyRelation1 |
ms21:ResourceRelation
ResourceRelation is a custom class for describing user-defined relationships between Dataset resources. Instances of ResourceRelation in the ResData Fedora 4 model are also defined as pcdm:Object type nodes.
Fedora 4 URI structures for the ResourceRelation nodes are:
Description | URL |
Dataset | /rest/datasets/[dataset pairtree id] |
ResourceRelation | /rest/datasets/[dataset pairtree id]/resourceRelation1 |
Activity (vivo:ResearchActivity, pcdm:Object)
The ResearchActivity class from the VIVO ontology is used to define Activity type resources in ResData. In the Fedora 4 model for ResData, all instances of the ResearchActivity class are also defined as nodes of pcdm:Object type with a number of data properties containing descriptive metadata and object properties containing reference to additional information about a research project, including funding body and affiliation. Figure 3 bellow illustrates how pcdm:Object and vivo:ResearchActivity classes are combined to represent Activity-type resources in ResData Fedora 4 model.
Figure 3: Activity-type resources in Fedora 4 model for ResData
Fedora 4 URI patterns for ResData Activity-type resources are:
Description | URL |
Activity | /rest/activities/[activity pairtree id] |
Funding | /rest/activities/[activity pairtree id]/funding |
Organisation | /rest/activities/[activity pairtree id]/organisation |
Party (foaf:Person, pcdm:Object)
Similar to Dataset and Activity, all Party-type resources are defined as instances of both the Person class from the FOAF ontology and the pcdm:Object class (Figure 4).
Figure 4: ResData Party defined as pcdm:Object
Fedora 4 URI patterns for ResData Party-type resources:
Description | URL |
Activity | /rest/parties/[party pairtree id] |
Funding | /rest/parties/[party pairtree id]/organisation |
...