Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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 preservation metadata
    • Type: Inline XML
    • Mime Type: application/rdf+xml
    • Versionable

 

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

 

  • PM = Preservation metadatapreservation metadata about individual datastream (eg: SOURCE01 would have PM-SOURCE01)
    • Type: Inline XML
    • Mime Type: application/rdf+xml
    • Versionable 
       
    SOURCE
    • Type: Managed
    • Mime Type: any
    • 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

...

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

API

UNSW make extensive uses of Most use Fedora 3 API (REST and SOAP), main uses API are: :

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 

...