...

• 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

• 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

• • 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 =
• 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
  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

• 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

Models

TODO: Outline Fedora 4 details!
Model 

Functionality

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