These guidelines were compiled by the Metadata Working Group (MWG) for use with UCT
digital collections.
The MWG was formed to implement and manage the
Metadata and Information Architecture Policy, one of the Council-approved governance
policies developed by UCT’s Enterprise Content Management (ECM) programme.
The policy aims to ensure that all content objects generated and managed by UCT
have sufficient metadata; that the metadata meets international standards; and
that it is consistently applied. For more information, see the overview page:
Metadata Working Group
Using the guidelines
All relevant guideline information has been grouped in the
Guidelines section below. For a general overview of good metadata capture
practices, see the General Guidelines and Key Principles tab. If you
are capturing metadata for content in your repository, then select the relevant
tab below to view the guidelines for this content type.
Field requirements
Mandatory fields are those fields that you must
include when adding content (whether text, image or multimedia)
to your repository, if the field is applicable and the
information is known.
Recommended fields are those fields
which you should include if the field is applicable and the
information is known, but which are not required.
Optional fields are those fields which
you can include if you want to, but which are not required.
Avoid using abbreviations, particularly if
they would make the record unclear (see exceptions listed
below).
When using an acronym for an organisation,
use the following format: African National Congress (ANC);
United Nations (U.N.).
For names of countries, use the spelled out
form of the name. For example, United Kingdom not U.K.; South
Africa not S.A.
In general, the following abbreviations are
allowed:
- Widely accepted terms such as St. for Saint
- Distinguishing names added to persons such as Mr, Mrs and
Miss
In case of doubt, give the word in full.
Capitalisation
In general, capitalise the first word (of a
title for example) and proper names (names of places, names of
people and names of organisations).
Dates
Enter dates as described below.
- Year: YYYY
- Year and month: YYYY-MM
- Complete date: YYYY-MM-DD
Range of dates:
- 1993 - 1994 (Separate dates with space, hyphen, space)
Approximate date:
- 1994? (follow date with a ? to show approximate or
probable date)
Initial articles
Omit initial articles at the beginning of the
title such as: The, A, An, Die, Le, La etc.
Diacritics
Have a clear understanding of how the
database handles non-standard characters and diacritics.
Input them so that they display and retrieve
effectively.
Unknown data
Fields for which there is no data, should be
left blank.
Principle
Description
Use controlled
vocabularies to make metadata entry consistent and faster.
An encoding scheme is a standardised format for describing
aspects of a digital resource.
A controlled vocabulary is a standardised list of terms and
phrases used to tag units of information so they may be more
easily retrieved by a search.
Whenever possible, digital resources should be described
using encoding schemes and controlled vocabularies.
In addition to improving organization and findability, these
standardised lists serve as a form of quality control.
Ensure quality
control and consistency in metadata capture for findability.
When entering subject terms, consistency is very important
so an effort has to be made to enter the same term for the same
thing throughout the collection.
For example, choose one of the following terms and use
consistently when describing a school child: scholar, pupil,
learner.
Inconsistent and inaccurate data entry could result in
valuable resources not being found by a researcher.
Typing errors, extra punctuation, inconsistent
abbreviations, and inconsistency with regard to what kind of
information goes into what field can all affect the findability
of the resource.
Metadata guidelines for text
Quick Find by field requirement:
Mandatory
Recommended
Optional
Quick Find by field:
Dublin Core Field
Definition
Encoding scheme /
Controlled vocabulary
Notes / Input
Guidelines
Creator
Person/s or organisation/s primarily responsible for
the creation of the document.
Also known as the author.
N/A
Mandatory.
More than one Creator field is allowed.
Add additional authors in separate fields.
Use the format: Surname, Name/s, or, Surname,
Initials.
Do not add titles such as Mr, Mrs, Sir, Professor
unless necessary to identify the person.
In the case of an organisation name which clearly
includes an organisational hierarchy, list the parts of the
hierarchy from largest to smallest, separated by full stops.
Date
Date associated with the life cycle of the
document.
Typically the date will be associated with the
creation or availability of the document.
World Wide Web Consortium encoding rules for date and
times (W3CDTF)
Mandatory.
Only one Date field is allowed.
Follow the YYYY-MM-DD format.
If there is no date of publication, use any
other date available.
It is better to use one date than no date at
all.
To express more about the time period, use
the
Coverage: Temporal field. Here
one can use expressions for the time period (i.e circa 1978)
Identifier
Name of the digital file and/or unique identification
code/number.
N/A
Mandatory.
Only one Identifier field is allowed.
Recommended best practice is to name the document using a
formal identification system.
For example: Uniform Resource Identifier (URI), Uniform
Resource Locator (URL), Digital Object Identifier (DOI).
Publisher
Organisation responsible for making the document
available.
N/A
Mandatory if applicable.
Commercial or non-commercial publisher of the
resource.
With university publications, place the name
of the faculty and/or research group of research school after
the name of the university.
In the case of an organisation name which
clearly includes an organisational hierarchy, list the parts of
the hierarchy from largest to smallest, separated by full stops.
If it is not clear whether there is a
hierarchy present, or it is unclear which is the larger or
smaller portion of the body, give the name as it appears in the
eprint.
Subject
Subject terms or keywords describing the content of
the document.
N/A
Mandatory when applicable.
Typically, a subject will be expressed as
keywords or key phrases that describe the intellectual content of
the resource.
For keywords/key phrases that are not controlled
by a vocabulary or thesaurus either encode multiple terms with a
semi-colon separating each keyword/key phrase, or, repeat the
element for each term.
When terms are taken from a controlled vocabulary
or schema, encode each term in a separate element.
Typically a Rights statement will contain a rights
management statement for the access and use of the document, or, a reference
to a service providing such information.
Rights information often encompasses Intellectual
Property Rights (IPR), Copyright and various property rights.
Person/s who have contributed to the intellectual
content of the resource.
N/A
Optional.
Examples of contributors are: supervisor, editor,
technician or data collector.
More than one Contributor field is allowed.
Add additional contributors in separate fields.
Use the format: Surname, Name/s, or, Surname,
Initials
Do not add titles such as Mr, Mrs, Sir, Professor
unless necessary to identify the person
In the case of an organisation name, which clearly
includes an organisational hierarchy, list the parts of the hierarchy
from largest to smallest, separated by full stops.
Coverage: Spatial
Location/s covered by the intellectual content of the
document.
Best practice is to select a value from a controlled
vocabulary, such as:
Typically this field will be a place name or geographic
coordinates.
Coverage: Temporal
Time period associated with the document.
N/A
Optional.
Only one Coverage: Temporal field is allowed.
Typically this field will include a time period, approximate
date or date range.
Relation
Reference to a related resource.
N/A
Optional.
For example, a link to the data set.
Source
Organisational entity or project which is responsible for content.
N/A
Optional.
Only one Source field is allowed.
For example, the physical collection of which this
document is a part.
Title: Alternative
Any form of the title used as a substitute or
alternative to the formal title of the document.
N/A
Optional.
Only one Title: Alternative field is
allowed.
If there is an additional title, use the
Title: Alternative
field
Use for titles in other languages (Parallel
titles) or translated titles.
Metadata guidelines for theses and
dissertations
Quick Find by field requirement:
Mandatory
Recommended
Optional
Quick Find by field:
Dublin Core Field
Definition
Encoding scheme / Controlled
vocabulary
Notes / Input Guidelines
Creator
Persons primarily responsible for the creation of the thesis.
Also known as the author.
UCT
Mandatory.
If in very exceptional cases there is more than one Creator
and additional Creator field is allowed.
In this case, add additional authors in separate fields.
Use the format: Surname, Name/s, or, Surname, Initials.
Do not add titles such as Mr, Mrs, Sir, Professor unless
necessary to identify the person.
Date: Issued
Date associated with the life cycle of the thesis.
Typically this should be the date that appears on the title
page.
World Wide Web Consortium encoding rules for date and times (W3CDTF)
Mandatory.
Only one Date: Issued field is allowed.
Follow the YYYY format, YYYY-MM.
Identifier
Name of the digital
file and/or unique identification code/number.
N/A
Mandatory.
Only one Identifier field is allowed.
Recommended best practice is to name the document using a formal
identification system.
For example: Uniform Resource Identifier (URI), Uniform Resource Locator
(URL), Digital Object Identifier (DOI).
Publisher: Institution
Name of the institution awarding the degree.
N/A
Mandatory.
Only one Publisher: Institution field is allowed.
For example: University of Cape Town.
Publisher: Faculty
Name of the faculty.
UCT
Mandatory.
Only one Publisher: Faculty field is allowed.
For example: Health Sciences.
Subject
Subject terms or keywords describing the content of the thesis.
N/A
Mandatory when applicable.
Typically, a subject will be expressed as keywords or key
phrases that describe the intellectual content of the resource.
For keywords/key phrases that are not controlled by a vocabulary
or thesaurus either encode multiple terms with a semi-colon
separating each keyword/key phrase, or, repeat the element for each
term.
When terms are taken from a controlled vocabulary or schema,
encode each term in a separate element.
Title
Title of the thesis as it appears on the title page or equivalent.
N/A
Mandatory.
Only one Title field is allowed.
Record the full title, including any subtitles.
If there is a translated title or title in another language
(Parallel title) use the
Title: Alternative field.
Type: Qualification Level
Qualification.
Masters
Doctoral
Mandatory.
Only one Type: Qualification Level field is allowed.
Type: Qualification Name
Name of the specific degree awarded.
UCT controlled list
Mandatory.
Only one Type: Qualification Name field is allowed.
Example: M.Phil, PhD, MA, MSc
Contributor: Advisor
Use for the name/s of the Supervisor/s.
UCT
Recommended.
More than one Contributor field is allowed if there is more
than one Supervisor.
Add additional Supervisors in separate fields.
Use the format: Surname, Name/s, or, Surname, Initials.
Do not add titles such as Mr, Mrs, Sir, Professor unless necessary
to identify the person.
Description
The full text of the abstract taken from the thesis.
May include a translated abstract.
N/A
Recommended.
Only one Description field is allowed unless there is
a translated abstract.
Format
Format of the digital file.
Best practice is to select a value from the list of Internet
Media Types (MIME types)
Internet Media Type (IMT).
Recommended.
Only one Format field is allowed.
Examples for text-based resources: html, pdf, richtext etc.
May be used to determine the software or hardware or other
equipment needed.
Typically a Rights statement will contain a rights management statement
for the access and use of the document, or, a reference to a service
providing such information.
Rights information often encompasses Intellectual Property Rights
(IPR), Copyright and various property rights.
Typically this field will be a place name or geographic coordinates.
Coverage: Temporal
Time period
associated with the document.
N/A
Optional.
Only one Coverage: Temporal field is allowed.
Typically this field will include a time period, approximate date or date
range.
Relation
Reference to a related
resource.
N/A
Optional.
For example, a link to the data set.
Title: Alternative
Any form of the title used as a substitute or alternative to the
formal title of the document.
N/A
Optional.
Only one Title: Alternative field is allowed.
If there is an additional title, use the Title:
Alternative
field.
Use for titles in other languages (Parallel titles) or
translated titles.
Metadata guidelines for datasets
Quick Find by field requirement:
Mandatory
Recommended
Optional
Quick Find by field:
Dublin Core Field
Definition
Encoding scheme / Controlled
vocabulary
Notes / Input Guidelines
Creator
Person/s or organisation /s primarily responsible for the creation of the dataset.
N/A
Mandatory.
More than one Creator field is allowed.
Add additional authors in separate fields.
Use the format: Surname, Name/s, or, Surname, Initials.
Do not add titles such as Mr, Mrs, Sir, Professor unless
necessary to identify the person.
Date
Date associated with the life cycle of the dataset.
Typically the date will be associated with the creation or availability of the dataset.
World Wide Web Consortium encoding rules for date and times (W3CDTF)
Mandatory.
Only one Date field is allowed.
Follow the YYYY-MM-DD format.
If there is no date of publication, use any other date available.
It is better to use one date than no date at all.
To express more about the time period, use the Coverage: Temporal field. Here one can use expressions for the time period (i.e circa 1978).
Identifier
Name of the digital
file and/or unique identification code/number.
N/A
Mandatory.
Only one Identifier field is allowed.
Recommended best practice is to name the document using a formal
identification system.
For example: Uniform Resource Identifier (URI), Uniform Resource Locator
(URL), Digital Object Identifier (DOI).
Subject
Subject terms or keywords describing the content of the dataset.
N/A
Mandatory when applicable.
Typically, a subject will be expressed as keywords or key
phrases that describe the intellectual content of the resource.
For keywords/key phrases that are not controlled by a vocabulary
or thesaurus either encode multiple terms with a semi-colon
separating each keyword/key phrase, or, repeat the element for each
term.
When terms are taken from a controlled vocabulary or schema,
encode each term in a separate element.
Can include field of research.
Title
Title or name of the dataset.
N/A
Mandatory.
Only one Title field is allowed.
Description
An account of the content of the resource.
May include but is not limited to: an abstract, table of contents, or a free-text account of the content.
N/A
Recommended.
Only one Description field is allowed unless there is
a translated abstract.
Use standard sentence form.
Capitalise content according to normal rules of writing.
Format
Format of the digital file.
Best practice is to select a value from the list of Internet
Media Types (MIME types)
Internet Media Type (IMT).
Recommended.
Only one Format field is allowed.
Examples for text-based resources: html, pdf, richtext etc.
May be used to determine the software or hardware or other
equipment needed.
Typically a Rights statement will contain a rights management statement
for the access and use of the dataset, or, a reference to a service
providing such information.
Rights information often encompasses Intellectual Property Rights
(IPR), Copyright and various property rights.
Typically this field will be a place name or geographic coordinates.
Coverage: Temporal
Time period
associated with the dataset.
N/A
Optional.
Only one Coverage: Temporal field is allowed.
Typically this field will include a time period, approximate date or date
range.
Relation
Reference to a related
resource.
N/A
Optional.
For example, a link to a publication.
Metadata guidelines for images
Quick Find by field requirement:
Mandatory
Recommended
Optional
Quick Find by field:
Dublin Core Field
Definition
Encoding scheme / Controlled
vocabulary
Notes / Input Guidelines
Creator
Persons primarily responsible for the creation of the image.
Also known as the photographer.
N/A
Mandatory.
More than one Creator
field is allowed.
Add additional authors in separate fields.
Use the format: Surname, Name/s, or, Surname, Initials.
Do not add titles such as Mr, Mrs, Sir, Professor unless
necessary to identify the person.
In the case of an organisation name which clearly includes an organisational hierarchy, list the parts of the hierarchy from largest to smallest, separated by full stops.
Date
Date associated with the life cycle of the image.
Typically the date will be associated with the creation or availability of the image.
World Wide Web Consortium encoding rules for date and times (W3CDTF)
Mandatory.
Follow the YYYY-MM-DD format.
If there is no date of publication, use any other date available.
It is better to use one date than no date at all.
To express more about the time period, use the Coverage: Temporal field. Here one can use expressions for the time period (i.e circa 1978).
Identifier
Name of the digital
file and/or unique identification code/number.
N/A
Mandatory.
Only one Identifier field is allowed.
Recommended best practice is to name the image using a formal
identification system.
For example: Uniform Resource Identifier (URI), Uniform Resource Locator
(URL), Digital Object Identifier (DOI).
Publisher
Organisation responsible for making the image available.
N/A
Mandatory if applicable.
Commercial or non-commercial publisher of the resource.
With university publications, place the name of the faculty and/or research group of research school after the name of the university.
In the case of an organisation name, which clearly includes an organisational hierarchy, list the parts of the hierarchy from largest to smallest, separated by full stops.
Subject
Subject terms or keywords describing the content of the image.
N/A
Mandatory when applicable.
Typically, a subject will be expressed as keywords or key
phrases that describe the intellectual content of the resource.
For keywords/key phrases that are not controlled by a vocabulary
or thesaurus either encode multiple terms with a semi-colon
separating each keyword/key phrase, or, repeat the element for each
term.
When terms are taken from a controlled vocabulary or schema,
encode each term in a separate element.
Title
Title or name of the image.
N/A
Mandatory.
Only one Title field is allowed.
Description
A descriptive summary of the image.
N/A
Recommended.
Only one Description field is allowed unless there is
a translated abstract.
Use standard sentence form.
Capitalise content according to normal rules of writing.
Format
Format of the digital file.
Best practice is to select a value from the list of Internet
Media Types (MIME types)
Internet Media Type (IMT).
Recommended.
Only one Format field is allowed.
Examples for images: jpeg; gif; tiff; png etc.
May be used to determine the software or hardware or other
equipment needed.
Rights
Information about the
right held in and over the image.
Typically a Rights statement will contain a rights management statement
for the access and use of the document, or, a reference to a service
providing such information.
Rights information often encompasses Intellectual Property Rights
(IPR), Copyright and various property rights.
Typically this field will be a place name or geographic coordinates.
Coverage: Temporal
Time period
associated with the image.
N/A
Optional.
Only one Coverage: Temporal field is allowed.
Typically this field will include a time period, approximate date or date
range.
For example: 1970-1979; circa 1980.
Relation
Reference to a related
resource.
N/A
Optional.
For example, a citation to the published work featuring the image.
Source
Organisational entity or project which is responsible for content.
N/A
Optional.
Only one Source field is allowed.
For example, the physical collection of which this image is a part.
Metadata guidelines for video
Quick Find by field requirement:
Mandatory
Recommended
Optional
Quick Find by field:
Dublin Core Field
Definition
Encoding scheme / Controlled
vocabulary
Notes / Input Guidelines
Contributor
Person or organisation contributing to the content of a film.
N/A
Mandatory (if applicable).
More than one Contributor
field is allowed.
Add additional authors in separate fields.
Use the format: Surname, Name/s, or, Surname, Initials.
Do not add titles such as Mr, Mrs, Sir, Professor unless
necessary to identify the person.
Use for actors, script writers, editors, etc.
In the case of an organisation name which clearly includes an organisational hierarchy, list the parts of the hierarchy from largest to smallest, separated by full stops.
Creator
Persons primarily responsible for the creation of the film.
N/A
Mandatory.
More than one Creator
field is allowed.
Add additional authors in separate fields.
Use the format: Surname, Name/s, or, Surname, Initials.
Do not add titles such as Mr, Mrs, Sir, Professor unless
necessary to identify the person.
Use for the Director of a film.
In the case of an organisation name which clearly includes an organisational hierarchy, list the parts of the hierarchy from largest to smallest, separated by full stops.
Date
Date associated with the life cycle of the film.
Typically the date will be associated with the creation or availability of the
film.
World Wide Web Consortium encoding rules for date and times (W3CDTF)
Mandatory.
Follow the YYYY-MM-DD format.
If there is no date of publication, use any other date available.
It is better to use one date than no date at all.
To express more about the time period, use the Coverage: Temporal field. Here one can use expressions for the time period (i.e circa 1978).
Identifier
Name of the digital
file and/or unique identification code/number.
N/A
Mandatory.
Only one Identifier field is allowed.
Recommended best practice is to name the film using a formal
identification system.
For example: Uniform Resource Identifier (URI), Uniform Resource Locator
(URL), Digital Object Identifier (DOI).
Publisher
Organisation responsible for making the film available.
N/A
Mandatory if applicable.
Commercial or non-commercial publisher of the resource.
With university publications, place the name of the faculty and/or research group of research school after the name of the university.
In the case of an organisation name, which clearly includes an organisational hierarchy, list the parts of the hierarchy from largest to smallest, separated by full stops.
Subject
Subject terms or keywords describing the content of the film.
N/A
Mandatory when applicable.
Typically, a subject will be expressed as keywords or key
phrases that describe the intellectual content of the resource.
For keywords/key phrases that are not controlled by a vocabulary
or thesaurus either encode multiple terms with a semi-colon
separating each keyword/key phrase, or, repeat the element for each
term.
When terms are taken from a controlled vocabulary or schema,
encode each term in a separate element.
Title
Title or name of the film.
N/A
Mandatory.
Only one Title field is allowed.
Description
A descriptive summary of the film.
N/A
Recommended.
Only one Description field is allowed unless there is
a translated abstract.
Use standard sentence form.
Capitalise content according to normal rules of writing.
Format
Format of the digital file.
Best practice is to select a value from the list of Internet
Media Types (MIME types)
Internet Media Type (IMT).
Recommended.
Only one Format field is allowed.
Examples for films: wav; mp3 etc.
May be used to determine the software or hardware or other
equipment needed.
Typically a Rights statement will contain a rights management statement
for the access and use of the film, or, a reference to a service
providing such information.
Rights information often encompasses Intellectual Property Rights
(IPR), Copyright and various property rights.
Typically this field will be a place name or geographic coordinates.
Coverage: Temporal
Time period
associated with the film.
N/A
Optional.
Only one Coverage: Temporal field is allowed.
Typically this field will include a time period, approximate date or date
range.
For example: 1970-1979; circa 1980.
Relation
Reference to a related
resource.
N/A
Optional.
Source
Organisational entity or project which is responsible for content.
N/A
Optional.
Only one Source field is allowed.
For example, the physical collection of which this film is a part.
Title: Alternative
Any form of the title used as a substitute or alternative to the formal title of the film.
N/A
Optional.
Only one Title: Alternative field is allowed.
If there is an additional title, use the Title: Alternative field.
Use for titles in other languages (Parallel titles) or translated titles.
Metadata guidelines for sound
Quick Find by field requirement:
Mandatory
Recommended
Optional
Quick Find by field:
Dublin Core Field
Definition
Encoding scheme / Controlled
vocabulary
Notes / Input Guidelines
Contributor
Person or organisation contributing to the content of a sound file.
N/A
Mandatory (if applicable).
More than one Contributor
field is allowed.
Add additional authors in separate fields.
Use the format: Surname, Name/s, or, Surname, Initials.
Do not add titles such as Mr, Mrs, Sir, Professor unless
necessary to identify the person.
Use for the person being interviewed in oral histories or other interviews.
For example: Boyce, E. (interviewee)
In the case of an organisation name which clearly includes an organisational hierarchy, list the parts of the hierarchy from largest to smallest, separated by full stops.
Creator
Persons primarily responsible for the creation of the sound file.
N/A
Mandatory.
More than one Creator
field is allowed.
Add additional authors in separate fields.
Use the format: Surname, Name/s, or, Surname, Initials.
Do not add titles such as Mr, Mrs, Sir, Professor unless
necessary to identify the person.
Use for the interviewer in oral histories or other interviews.
For example: Ntamesi, S. (interviewer)
Use for the primary speaker in a speech or inaugural lecture.
In the case of an organisation name which clearly includes an organisational hierarchy, list the parts of the hierarchy from largest to smallest, separated by full stops.
Date
Date associated with the life cycle of the sound file.
Typically the date will be associated with the creation or availability of the
sound file.
World Wide Web Consortium encoding rules for date and times (W3CDTF)
Mandatory.
Follow the YYYY-MM-DD format.
If there is no date of publication, use any other date available.
It is better to use one date than no date at all.
To express more about the time period, use the Coverage: Temporal field. Here one can use expressions for the time period (i.e circa 1978).
Identifier
Name of the digital
file and/or unique identification code/number.
N/A
Mandatory.
Only one Identifier field is allowed.
Recommended best practice is to name the sound file using a formal
identification system.
For example: Uniform Resource Identifier (URI), Uniform Resource Locator
(URL), Digital Object Identifier (DOI).
Publisher
Organisation responsible for making the sound file available.
N/A
Mandatory if applicable.
Commercial or non-commercial publisher of the resource.
With university publications, place the name of the faculty and/or research group of research school after the name of the university.
In the case of an organisation name, which clearly includes an organisational hierarchy, list the parts of the hierarchy from largest to smallest, separated by full stops.
Subject
Subject terms or keywords describing the content of the sound file.
N/A
Mandatory when applicable.
Typically, a subject will be expressed as keywords or key
phrases that describe the intellectual content of the resource.
For keywords/key phrases that are not controlled by a vocabulary
or thesaurus either encode multiple terms with a semi-colon
separating each keyword/key phrase, or, repeat the element for each
term.
When terms are taken from a controlled vocabulary or schema,
encode each term in a separate element.
Title
Title or name of the sound file.
N/A
Mandatory.
Only one Title field is allowed.
For oral histories, begin title with Oral history interview…
Description
A descriptive summary of the sound file.
N/A
Recommended.
Only one Description field is allowed.
Use standard sentence form.
Capitalise content according to normal rules of writing.
Format
Format of the digital file.
Best practice is to select a value from the list of Internet
Media Types (MIME types)
Internet Media Type (IMT).
Recommended.
Only one Format field is allowed.
Examples for sound fileswav; mp3 etc.
May be used to determine the software or hardware or other
equipment needed.
Typically a Rights statement will contain a rights management statement
for the access and use of the sound file, or, a reference to a service
providing such information.
Rights information often encompasses Intellectual Property Rights
(IPR), Copyright and various property rights.
Typically this field will be a place name or geographic coordinates.
Coverage: Temporal
Time period
associated with the sound file.
N/A
Optional.
Only one Coverage: Temporal field is allowed.
Typically this field will include a time period, approximate date or date
range.
For example: 1970-1979; circa 1980.
Relation
Reference to a related
resource.
N/A
Optional.
Source
Organisational entity or project which is responsible for content.
N/A
Optional.
Only one Source field is allowed.
For example, the physical collection of which this sound
file is a part.
More information and assistance
If you have any queries regarding: Scholarly content collection queries, please contact Mandy Noble at
mandy.noble@uct.ac.za Business content collection queries, please contact Jenny Wood at
jenny.wood@uct.ac.za
Metadata guidelines for text
Metadata guidelines for theses and
dissertations
Metadata guidelines for datasets
Metadata guidelines for images
Metadata guidelines for video
Metadata guidelines for sound