...
Namespace | URL |
fedora | |
dc | |
| access | http://fedora.info/definitions/1/0/access/ |
| premis | http://www.loc.gov/premis/rdf/v1# |
ResData Dataset
...
Descriptive and Administrative Metadata
In Fedora 4, the RELS-INT and RELS-EXT information associated with the ResData resources will be migrated as data properties of the corresponding Fedora 4 resource nodes.
Below is the RELS-INT and RELS-EXT information that will be migrated to Fedora 4 as data properties of Dataset, Party, and Activity resources in ResData:
| Property | Note |
|---|---|
| VITRO-ANDS: dateOfPublication | |
| ms21:status | |
| bibo:doi | only for Dataset |
| ms21:handle | only for Dataset |
Data Model
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
Classes
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]/[partyRelation id1] |
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]/[resourceRelation id1] |
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 |
Namespaces
Descriptive and Administrative Metadata
In Fedora 4, the RELS-INT and RELS-EXT information associated with the ResData resources will be migrated as data properties of the corresponding Fedora 4 resource nodes.
Below is the RELS-INT and RELS-EXT information that will be migrated to Fedora 4 as data properties of Dataset, Party, and Activity resources in ResData:
| Property | Note |
|---|---|
| VITRO-ANDS: dateOfPublication | |
| ms21:status | |
| bibo:doi | only for Dataset |
| ms21:handle | only for Dataset |
Namespaces
Namespace | Namespace | URL |
bibo | ||
owl | ||
ms21 | http://www.unsworks.unsw.edu.au/ontology/preservation-metadata/ | |
VITRO-ANDS | ||
core | ||
foaf | ||
pcdm |
...
Note: All classes are derived from existing classes used on Fedora 3 used in RELS-INT and RELS-EXT
Classes
unsworksp:collection
Collection access (pcdm:Object)
Access is a class describing a group of records. Aside from descriptive metadata, it contains administrative metadata containing access information to the records belonging to the collection.set of authorised users and/or groups. It is used to detail the access constraints placed on a record or collection. All of access classes are also defined pcdm:Object type node in the Fedora 4 UNSWorks model.
unsworksp:collection (pcdm:Object)
Collection is a class describing a group of records. Collection includes descriptive metadata with a link to access information. Similar to access class, instances of collections in the UNSWorks Fedora 4 model are also defined as pcdm:Object type node.
Property | Note | |
| unsworksp: | hasCollectionhasAccessConstraint |
unsworksp:record
A record class individual class represents a container for an intellectual entity such as a thesis, a book, moving image, etc. It it has descriptive metadata in Dublin Core and administrative metadata. it can have a link to other individual such as metadata, rights, and resourceabout the record and can contain other metadata and/or binary files and rights associated with the record as described on the next classes. Similar to collection and access classes, all instances of UNSWorks records are also defined as pcdm:Object type node.
Property | Note |
unsworksp:hasMetadata | |
unsworksp:hasRights | |
unsworksp:hasResource | |
unsworksp:hasCollection | |
| unsworksp:hasAccessConstraint |
unsworksp:resource (pcdm:File)
A resource class individual represents the a electronic resource of the record such as a PDF file of a thesis . It and it is stored as binary data and it can link to another resource describing the record has another binary data in another format type . Additionally this class is used to represent a converted file for preservation purpose. For example: , a thesis record has binary file in word document and there is another binary file in PDF format which is converted from the word documentin MS Word document format will have a preservation copy in PDF format. The relationship between these files will be represented by the unsworksp:migratedFrom property. All resources are also defined as a pcdm:File type node.
Property | Note |
unsworksp:migratedFrom |
unsworksp:metadata (pcdm:File)
The metadata class is used to represent additional descriptive metadata of a record that cannot be added as properties in record class, for example: MODS and MARCXML descriptive metadata. These type of metadata
Metadata class is a class describing a metadata of a record. It is used to represent other record metadata not in Dublin Core format which will be stored as binary datafile (pcdm:File). Similar to the resource class, it can link to same type another metadata may have a converted version for preservation purpose.
Property | Note |
unsworksp:migratedFrom |
unsworksp:rights (pcdm:File)
The rights class is used to Rights class individual represent a licence or agreements that author of the electronic resource has signedsigned by the person submitting the resource. Similar to resource and metadata, it can has a link to same type another metadata its converted version for preservation purpose and it is also defined as a pcdm:File type node.
Property | Note |
unsworksp:migratedFrom |
...
Descriptive and Administrative Metadata
...
In Fedora 4, the RELS-INT and RELS-EXT is mapped as resource property for UNSWorks are mapped as data properties of the resource as a administrative metadatanode.
Below is the RELS-INT and RELS-EXT information that will be ported to Fedora 4 as part of Resource property:
| Property | Note |
|---|---|
unsworksp:resourceType |
|
unsworksp:dunsworkspid |
|
unsworks:embargodate |
|
unsworks:embargoRemoved |
|
| owl:SameAs | Alternate URL |
...
Based on the model above, each resource can be added on the root using Fedora 4 default ingest using PairTree. The binary file of that particular resource will be added with the resource node as the parent using PairTree. For example:
| Type | unsworksp:record |
|---|---|
| URL | http://localhost:8080/fcrepo-webapp-4.1.0/rest/e3/93/78/f1/e39378f1-dc42-40d9-9199-545ff5860308 |
| Identifier | e3/93/78/f1/e39378f1-dc42-40d9-9199-545ff5860308 |
| Parent | http://localhost:8080/fcrepo-webapp-4.1.0/rest |
Below are Fedora 4 URI patterns for UNSWorks nodes. Collections, records and accesses are pdcm:object act as acontainer for collection, record, and access.
Description | URL |
Collection | /rest/collections/[collection pairtree id] |
Record | /rest/records/[record pairtree id] |
Resource | /rest/records/[record pairtree id]/[resource id1] |
Metadata | /rest/records/record/[record pairtree id]/[metadata id1] /rest/records/record/[record pairtree id]/[metadata id2] /rest/records/record/[record pairtree id]/[metadata id3] |
Rights | /rest/records/record/[record pairtree id]/[rights id1] /rest/records/record/[record pairtree id]/[rights id2] /rest/records/record/[record pairtree id]/[rights id3] |
Access | /rest/access/[access pairtree id] |
| Type | unsworksp:resource |
|---|---|
| URL | http://localhost:8080/fcrepo-webapp-4.1.0/rest/e3/93/78/f1/e39378f1-dc42-40d9-9199-545ff5860308/1f/fa/ef/05/1ffaef05-ad57-46b6-a553-08566680cfc2 |
| Identifier | 1f/fa/ef/05/1ffaef05-ad57-46b6-a553-08566680cfc2 |
| Parent | http://localhost:8080/fcrepo-webapp-4.1.0/rest/e3/93/78/f1/e39378f1-dc42-40d9-9199-545ff5860308
Functionality
Storage: Legacy storage (or Akubra)
...
In Fedora 3, the UNSWorks and ResData repositories only uses inline and managed datastreams. Inline datastreams is used for descriptive metadata such as DC, RDF, MODS, and MARCXML . DC and RDF metadata can be mapped to properties of Fedora 4 container node, others will be stored as binary file as Fedora 4 binary node. Similarly for managed datastreams, all will be stored as Fedora binary node (pdcm:File). See the UNSWorks and ResData Data Models for more information.
...