...
- 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 Object Models
UNSWorks
- Resource
- DC
- MODS = descriptive metadata
- Managed content
- PREMIS = preservation metadata
- RELS-EXT = used to store the persistent identifier for the object (handle)
- RELS-INT = used to store information about the file format and related preservation software
- Other datastreams with supporting documentation (various managed or inline datastreams e.g. rights metadata)
...
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).
Fedora 3 Functionality
STORAGE: UNSW uses the default Fedora 3 storage architecture.
DATASTREAM TYPES: UNSW uses inline and managed datastream types. External datastream types are not used.
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 STRATEGY: In Fedora 3, UNSW uses the Generic Search Service (GSearch) and Resource Index (RISearch) Search.
REPLICATION/JOURNALING: UNSW does not use replication or journaling.
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.
DISSEMINATORS: UNSW does not use disseminators.
API Functionality
AUDIT HISTORY: UNSW uses the audit history for the majority of objects in the repositories. Some draft, unpublished objects in the ResData repository are not versionable.
API: UNSW uses the Fedora 3 API functionality.
SECURITY: <Insert description here>