You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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

  • DC
  • RDF = main descriptive metadata plus links to related parties and activities
  • RELS-EXT = used to store the resource type, handle and doi
  • RELS-INT = used to store information about the version status (e.g. published) and access permissions

Research Data Management Plan object

  • DC
  • RDF = main descriptive metadata plus links to related parties and activities
  • RELS-EXT = used to store the resource type and storage information and access permissions

  • Activity object (grants/projects)
    • DC
    • RDF = main descriptive metadata
    • RELS-EXT = used to store the resource type and handle
    • RELS-INT = used to store information about the version status (e.g. published) and access permissions
  • Party object (people)
    • DC
    • RDF = main descriptive metadata
    • RELS-EXT = used to store the resource type and handle
    • RELS-INT = used to store information about the version status (e.g. published) and access permissions

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

TODO: Outline Fedora 4 details!
Model 

Storage: Legacy storage (or Akubra)

XML metadata : datastreams

XML metadata : inline

Content models

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

Identifiers

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

Replication/Journaling

Security policies: XACML

OAI-PMH

Versions

Disseminators

Audit history

API

 

 

 

 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.