Project Overview

<Insert description here>

Collection Description

UNSWorks

• The institutional repository – UNSWorks – contains more than 12,000 objects. These include research publications such as digital theses and conference papers. It includes some metadata-only records as well as objects with file attachments. New records are sourced via the university publications management system (ROS). 

ResData

• A research data management system containing over 250 records. The records describe datasets and research data management plans plus related parties (i.e. people) and activities (i.e. grants and projects). Information about people, grants and projects is sourced from other institutional databases via the data warehouse.

Other UNSW disciplinary repositories

• Approximately 25,000 records are stored across 5 other specialist disciplinary repositories. While most are metadata-only records, there is also some managed content such as video files. 
  

Fedora 3 Details

Object Models

UNSWorks

Resource

• DC

  • Type: Inline XML

  • Mime Type: text/xml

  • Versionable

• MODS = descriptive metadata
  • Type: Inline XML
  • Mime Type: text/xml
  • Versionable

• RELS-EXT
  • Type:Inline XML
  • Mime Type: application/rdf+xml
  • Versionable
  • Contains additional informatiion of the object such as persistent identifier (handle)

• RELS-INT
  • Type: Inline XML
  • Mime Type: application/rdf+xml
  • Versionable
  • Contains additional information about the datastreams, such as type of resource and relation.

• DP-EVENT = PREMIS preservation metadata
  • Type: Inline XML
  • Mime Type: application/rdf+xml
  • Versionable

• SOURCE
  • Type: Managed
  • Mime Type: any
  • Versionable

• PM = preservation metadata about individual datastream (eg: SOURCE01 would have PM-SOURCE01)
  • Type: Inline XML
  • Mime Type: application/rdf+xml
  • Versionable 

ResData

Dataset, Activity (grants/projects), and Party (people) object 

• DC

  • Type: Inline XML

  • Mime Type: text/xml

  • Versionable

• RELS-EXT
  • Type:Inline XML
  • Mime Type: application/rdf+xml
  • Versionable
  • Contains additional informatiion of the object such as persistent identifier (handle/doi) and resource type

• RELS-INT
  • Type: Inline XML
  • Mime Type: application/rdf+xml
  • Versionable
  • Contains additional information about the datastreams, such as type of resource, relation, version, and publishing status

• RDF = descriptive metadata plus links to related parties and activities for published object

  • Type: Inline XML

  • Mime Type: text/xml

  • Versionable

• RDFNP = descriptive metadata plus links to related parties and activities for unpublished object

  • Type: Inline XML

  • Mime Type: text/xml

  • Not Versionable
    
    

Research Data Management Plan object

• DC

  • Type: Inline XML

  • Mime Type: text/xml

  • Versionable

• RELS-EXT
  • Type:Inline XML
  • Mime Type: application/rdf+xml
  • Versionable
  • Contains additional informatiion of the object such as persistent identifier (handle/doi) and resource type

• RDFNP = descriptive metadata plus links to related parties and activities for unpublished object

  • Type: Inline XML

  • Mime Type: text/xml

  • Not Versionable

Notes: Record status includes draft, pending, published. Only dataset, activity and party objects can be published (not research data management plans). Published records are versionable = True. Different pid format based on object type (e.g. sample activity object pid = resdataa:2222; sample dataset object pid = resdatac:3333).

Functionality

Storage: Legacy storage (or Akubra)

UNSWorks uses Legacy storage and ResData uses Akubra.

XML metadata : datastreams

See object models above.

XML metadata : inline

See object models above.

Content models

Default Fedora Content Model.

Datastream types (inline, managed, redirect, and external)

Non metadata datastream is a managed datastream.

Identifiers

UNSW uses custom namespaces for PIDs. Some repositories use multiple PID prefixes. All UNSW repositories use handles as persistent identifiers for objects. The ResData repository also uses DOIs for some objects. 

Indexing strategies (GSearch, RI-Search vs. F4 approaches)

UNSW uses the Generic Search Service (GSearch) and Resource Index (RISearch) Search. 

Replication/Journaling

UNSW does not use replication or journaling. 

Security policies: XACML

Default XACML with minor modification for accessing rights metadata on UNSWorks.

OAI-PMH

UNSW does not use the Fedora OAI-PMH module. UNSW uses the Fedora 3 API to export XML metadata and jOAI as the OAI-PMH data provider.

Versions

All datastreams are mostly versionable.

Disseminators

UNSW does not use disseminators. 

Audit history

UNSW uses audit history for statistic, preservation, and versioning. 

API

Most use Fedora 3 API (REST and SOAP):

API_A 

• findObjects

• getDatastreamDissemination

• listDatastreams

API_M

• Datastream Management

  • addDatastream

  • getDatastreams

  • getDatastreamHistory

  • getDatastream

  • modifyDatastreamByValue

  • modifyDatastreamByReference

  • setDatastreamState

  • setDatastreamVersionable

  • purgeDatastream

• Object Management

  • modifyObject
  • purgeObject
  • getNextPID
  • ingest

Fedora 4 Details

Data Model

Fedora 3 Properties to Fedora 4:

Fedora 3 Object  Properties to Fedora 4:

Fedora 3 Datastream Properties to Fedora 4:

Note: all properties with fedora namespace are not user-modifiable.

Namespace

ResData Data Model

Note: All classes are derived from existing classes used on Fedora 3 used in RELS-INT and RELS-EXT

Classes

ms21: UNSW_ResearchDataCollection

A ResearchData class individual represents an entity describing about dataset. It has a descriptive metadata and it must have a link to an instance of ResearchActivity and Person. A link can be established to another ResearchData for describing a related ResearchData

ms21:ResearchDataManagementPlan

ResearchDataManagementPlan is a class describing a dataset plan. Similar to ResearchData class, it must have a link to an instance of ResearchActivity and Person.

vivo:ResearchActivity

ResearchActivity is a class describing an entity describing a research project or grant. It must be linked to a ResearchData.

foaf:Person

Person is a class describing a person.

Descriptive and Administrative Metadata

ResData uses RELS-INT and RELS-EXT to describe additional information on the Fedora 3 object and datastream for storing administrative information and searching purpose. For example status, published date, embargo date, etc.

In Fedora 4, the RELS-INT and RELS-EXT is mapped as resource property of the resource as a administrative metadata.

Below is the RELS-INT and RELS-EXT information that will be ported to Fedora 4 as part of Resource property:

For descriptive metadata, the format for each of Fedora 4 resource is a Dublin Core metadata format.

Namespace

UNSWorks Data Model

Note: All classes are derived from existing classes used on Fedora 3 used in RELS-INT and RELS-EXT

Classes

unsworksp:collection
Collection 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.

unsworksp:record
A record class individual represents an intellectual entity such as a thesis, a book, moving image, etc. It has descriptive metadata in Dublin Core and administrative metadata. it can have a link to other individual such as metadata, rights, and resource.

unsworksp:resource
A resource class individual represents the electronic resource of the record such as a PDF file of a thesis. It is stored as binary data and it can link to another resource describing the record has another binary data in another format type 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 document.

unsworksp: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 data. Similar to resource, it can link to same type another metadata for preservation purpose

unsworksp:rights

Rights class individual represent a licence or agreements that author of the electronic resource has signed. Similar to resource, it can link to same type another metadata for preservation purpose

Descriptive and Administrative Metadata

Similar to ResData, UNSWorks also uses RELS-INT and RELS-EXT to describe additional information on the Fedora 3 object and datastream for storing administrative information and searching purpose. For example doi and handle.

In Fedora 4, the RELS-INT and RELS-EXT is mapped as resource property of the resource as a administrative metadata.

Below is the RELS-INT and RELS-EXT information that will be ported to Fedora 4 as part of Resource property:

For descriptive metadata, the format for each of Fedora 4 resource is a Dublin Core metadata format.

Namespace

Sample URL structure on Fedora 4

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:

Functionality

Storage: Legacy storage (or Akubra)

XML metadata : datastreams

XML metadata : inline

The inline XML metadata is a metadata of the resource. It is mapped as property of a fedora:container.

See Data Model

Content models

Datastream types (inline, managed, redirect, and external)

Identifiers

Indexing strategies (GSearch, RI-Search vs. F4 approaches)

Integrate Fedora 4 with external triple store using JMS Message Consumer to accommodate search with SPARQL.

Replication/Journaling

N/A

Security policies: XACML

OAI-PMH

Versions

Disseminators

Audit history

API