PARADISEC Metadata listing
Draft #5 for discussion June 2006
Nick Thieberger  nickt@paradisec.org.au

The following listing has been adapted and combined from several sources, principally the Open Languages Archives Community (OLAC), the Broadcast Wave Format (BWF) metadata, and the National Library of Australia (NLA) metadata set.

We have an online data entry and management form which allows consistency in data entry via pop-up menus of controlled vocabularies. 

There are currently some 3,800 items in our metadata database. Regular exports of parts of the metadata provide XML encoded data for an OLAC- compliant static repository and header information that is encapsulated into the BWF audio files. The Archive is linked to the catalogue at the item level so that, with appropriate password access, a user can find an item in the catalogue and click on a URL that will go directly to the item in the Archive for download. A geographic query tool allows users to search for any item in a given location (determined by a bounding box drawn onto a map) and then to retrieve that item from the Archive.

The catalogue distinguishes three levels: the collection, item and file. 

Each item deposited (e.g. each tape) should have a unique identifier. Don't use delimiters within a filename. Hyphens are reserved characters for our archiving purposes, so ideal names are strings of alphanumerics limited to less than 10 characters if possible. We assign a name to the collection, usually the depositor's initials and then a digit, e.g. 'XP1'. Each tape has your number, e.g. 071, which, together with the collection id forms the persistent identifier for the archival object (the tape), e.g. XP1-071. Each file generated by the process has a derivative name (typically of the form A.wav). The whole filename is then XP1-071-A.wav. This is the persistent filename that you will find on the password-protected archive.

Where collection-level and item-level cells in the table below are shared the data is inherited from the collection level by the item level unless overwritten at the item level.

The collection identifier is PDSC.

In the following table we list correspondences between  PDSC catalogue fields and other metadata schemas, and the XML form that will be output for OLAC and BEXT / BWF Basic data. BEXT is the metadata encapsulated in Broadcast Wave Format (BWF) audio files. 

The assessment of data prior to digitisation serves two main functions. First, it scopes out the number of tapes to be digitised, and second it makes the tapes discoverable.

Tapes	undiscoverable,  
Tapes + catalogue	discoverable locally
Tapes + catalogue + web	discoverable globally
Tapes + catalogue + web + .0digital objects	discoverable globally and available (subject to permissions)

General note on data content.
Certain characters should be avoided as they cause problems for some part of the export or for XML data. Characters currently known to cause problems are angle brackets (< >), ampersand (&), and commas in fields that will be used as BEXT metadata.  

Items marked with # in the leftmost column are required for creation of an archival audio file (BWF)

	Database field	Collection level	Item level	Dublin Core 	Comment	
1.	Item id	N/A	Name of the resource			
2.	Collection id	required, unique	N/A		Combined with Item id to give Persistent identifier, of the form XXX-XXX	
#3.	Persistent id	N/A	required, unique, either given by the depositor, or generated by the accession process “Unique Source Identifier” (USID)Made up of Coll id- Item id		Persistent identifier	
BWF Basic data 	<ARCHIVENUMBER>XXX-XXX</ARCHIVENUMBER>  (MAX 32 Chars)	
OLAC Form	Persistent identifier <identifier>XXX-XXX</identifier>	
DC	Identifier	
4.	Item name	N/A	Identification as given by the depositor	Title		
BWF Basic data	<TITLE>XXXX</TITLE> (MAX 256 Chars)	
OLAC Form	<title>XXXXX</title>	
DC	Title	
5.	URL	-		Link to representational view of the data, currently mainly used for AC2 links to online images of fieldnotes.	
#6.	Collector	Content is a name, with the format surname, first name. 	contributor	taken from the current OLAC draft	
BEXT form	<ORIGINATOR>XXXX</ORIGINATOR>	
OLAC Form	Contributor (see ‘ROLE’)	
7.	Role (repeatable)	N/A	Content is a name, with the format surname, first name. 
Qualifiers: author; complier; composer*; consultant; 
data_inputter; depositor; 
editor;
interviewer; participant; performer; photographer; recorder; researcher; speaker; 
singer; 
translator
		taken from the current OLAC draft	
BEXT form	None (ORIGINATOR uses the depositor field)	
OLAC Form	<role refine=”XXX”>CONTENT</role>	
#8.	Countries	Country where the object was recorded or which the performance recorded originates from. Using ISO 3166 country codes.	Coverage		
9.	country code 	Code supplied by choice of a popup menu of names for the selected country. One code per country.	Coverage		
OLAC Form	<coverage.country code="ISO 3166-XX”>COUNTRYNAME</coverage.country>	
	But note that OLAC suggest that the country information derives from the language codes and need not be stored here. Since this version of the metadata cannot take advantage of the Ethnologue correlations we will continue to list both country name and country code here. Indeed, the catalogue relies on the selection of country first to then constrain the controlled language list to languages from that country. We now have data that links language name to geography and that will be implemented in the next period.
“Coverage should be used geographically only when the language involved has a wide distribution and the resource focuses on its use in a particular region or geopolitical jurisdiction, or conversely, when the resource deals with a region that encompasses multiple languages." (OLAC)	
10.	Minimum Latitude	These four elements together provide a polygon for data entry or searching by geography			
11.	Maximum Latitude				
12.	Minimum Longitude				
13.	Maximum Longitude				
14.	region/ village	information about region or village where data is from			
#15.	language as in source	free form field for entry of language names as given in the source data.		Used to allow the depositor to enter the preferred language name	
16.	dialect	free form field for entry of dialect  names as given in the source data.			
17.	subject language
(repeatable)	using Ethnologue, popup list of languages of the selected country that are the subject of the data (ISO/DIS 639-3). 	language	language	
18.	subject language code
(repeatable)	Ethnologue code of languages of the selected country that are the subject of the data. Inserted automatically from previous field choice (ISO/DIS 639-3).	language	language	
#19.	content language
(repeatable)	using Ethnologue, popup list of languages of the selected country that are the content of the data (ISO/DIS 639-3).	language	language	
20.	content language code
(repeatable)	Ethnologue, code of languages of the selected country that are the content of the data. Inserted automatically from previous field choice (ISO/DIS 639-3).	language	language	
OLAC Form	<language code=”XXX”>LANGUAGE NAME</language>
<subject.language code=”XXX”>LANGUAGE NAME</subject.language>	
“For a work of literature or other monolingual document aimed at the speakers of a particular language, use Language to identify that language. For a sound recording, use Language for the language being spoken in the recording. For a grammatical description, for instance, use Language for the language the grammar is written in; use Subject.language for the language whose grammar is being described. For an annotated text, use Language for the language in which the annotations are made; use Subject.language for the language of the base text that is being annotated. For a dictionary, use Language for the language in which the definitions are written; use Subject.language for the language whose words are being defined.” (OLAC)

Note that the following is the recommended form for encoding the language used, for example in a title, with the language indicated by the relevant 3-letter code, followed by the title, and then by a translation into English:

<title xml:lang="x-sil-LLU">Na tala 'uria na idulaa diana</title>
<dcterms:alternative xml:lang="en">The road to good reading</dcterms:alternative>

In the catalogue we distinguish 'content language' from 'subject language'.	
#21.	Date 	Last date when data was recorded with format YYYY-MM-DD	date created		
BEXT form	ORIGINATIONDATE	
OLAC Form	<oai:datestamp>YYYY-MM-DD</oai:datestamp>
<date>YYYY-MM-DD</date>	
22.	Datestampcreat	Date when record was created (automatically generated).	date created		
23.	Datestampmod	Date when record was last modified (automatically generated).	date created		
24.	Comments		free form text, comment about form of data, not publishable (see notes)			
25.	Orthographic notes	free form text, comment about orthography used in the metadata.			
26.	notes	free form text, notes about the content of the data, publishable	free form text, notes about the content of the data, publishable			
BEXT form	<COMMENT>XXX</COMMENT> (max 256 chars)	
OLAC Form	Included in <description>	
DC	DCDescription	
27.	Rights/ Access		Qualifiers:
restricted
standard
non-profit
commercial	rights	Adapted from the current OLAC draft
User is able to determine access conditions but is urged to use the rights 'Standard, as per the PDSC Access form'	
28.	Data type		refine:
lexicon
primary text
language description
song*
instrumental music*
[more]		taken from the current OLAC draft	

Pre-ingestion (=undigitised) or Collection assessment metadata. 
This infomation is used in assessing existing (typically not digitised) data collections. These collections should also be discoverable via the PARADISEC catalogue, and their listing here also assists in planning which collections to target for ingestion into the digitising process. There is a natural link between collection assessment metadata and preservation metadata.

	Collection level	Item level	Dublin Core 	OLAC	Comment	
29.	Date of assessment	Date when tapes were assessed.				
30.	Lengthsum cassette	N/A
	Length of audio cassette tapes in time. Calculated from number of objects by individual length.			
31.	Lengthsum reel to reel	N/A	Length of reel to reel tapes in metres. Calculated from number of objects by individual length			
32.	Lengthsum video	N/A	Length of video tapes in time. Calculated from number of objects by individual length.			
33.	Total cassette length	N/A	Running total of length all audiocassettes for the found dataset.			
34.	Total reel to reel length	N/A	Running total of length all reel to reels for the found dataset.			
35.	Total video length	N/A	Running total of length all videoes for the found dataset.			
36.	Reel to Reel speed	N/A	Where known, speed at which tapes were recorded			
37.	Reel to reel time	N/A	R to R  time calculated assuming a speed of 3.75 inches (or 9.525 cm) per second (say 343 mtr per hour)			
38.	Priority for ingestion	N/A	Number 0-10 assigned to indicate least to highest priority for ingestion. Criteria include: state of media; content of media (unique/ highly endangered/ sole record etc.); originating university;			
39.	Originating uni	Which university in the consortium the tapes came from.				
40.	Number of tapes	
	number of reel to reel tapes			
41.	Number of cassettes		number of audicassettes			
42.	Number of videoes		number of videoes			
43.	Media		Type of original media (tape brand, etc)			
44.	Conditions	Outlines conditions of storage (e.g. in filing cabinet in air-conditioned office), input into prioritising for ingestion.				
45.	Metadata source	Is the metadata compiled from observation of the collection or provided by the depositor?				
46.	Location	free form text. Where original media are located. NOT the current location of accessioned items.				

Preservation Metadata  
(a subset of the NLA preservation metadata set, see http://www.nla.gov.au/preserve/pmeta.html) 

		Collection level	Item level	File level	Dublin Core 	OLAC	Comment	
47.	Date digitised	N/A
	Date when digitised. Date with format YYYY-MM-DD				
48.	Digitised	N/A	checkbox, yes/ no				
49.	files
(repeatable)	N/A	name of all files that are part of this item.	
			
OLAC Form	<dcterms:hasPart>FILENAME</dcterms:hasPart>	
50.	Bitrate	N/A
	bitrate of each file that is part of this item.	
			
51.	Samplerate	N/A	samplerate of each file that is part of this item.	
			
52.	Date received	N/A	Date when tapes received by Paradisec. Date with format YYYY-MM-DD				
53.	Duration	N/A	Time duration of the digitised sound sequence with format hh:mm:ss:d				
BWF Basic data 	<DURATION> hh:mm:ss:d </DURATION> (10 characters)	
OLAC Form		
54.	id assigned	N/A
				has a PI been assigned and marked on the physical object? At the assessment stage a single item level entry is assigned with the id 'ASS' preceded by the collection id to form a temporary identifer.	
55.	audio notes	N/A	notes about the audio quality, errors, etc.			
56.	CD Burnt	N/A	Check box yes/no			
57.	CD id	N/A	Id number of CD distribution copy			
58.	Archive tag number	N/A	Number used to retrieve archival copies from the Sydney mass data store.			
59.	File description		Content is the file type, the qualifier is as follows. Thus, for example: audio, aiff; Image, TIFF
Image
Audio
Video
Text
Database
Executables				
60.	Operator	N/A	Name of the person responsible for transferring data from tape to digital form. 		
BWF Basic data 	<OPERATOR></OPERATOR>	
OLAC Form		
61.	Relations	N/A	Relationships between this version and other objects necessary for preservation management, e.g. "this is a reworking of item XXX/XXX', or "Item xxx/xxx is a reworking of this object".
isCopyOf
isCopiedBy
requires
isRequiredBy
hasPart
isPartOf
hasVersion
isVersionOf
replaces
isReplacedBy 
isTranscriptOf
hasTranscript
Name: isVersionOf 
Label: Is Version Of 
Definition: The described resource is a version, edition, or adaptation of the referenced resource. Changes in version imply substantive changes in content rather than differences in format. 
Has Version 
Name: hasVersion 
Label: Has Version 
Definition: The described resource has a version, edition, or adaptation, namely, the referenced resource. 
Is Replaced By 
Name: isReplacedBy 
Label:  is Replaced By 
Definition: The described resource is supplanted, displaced, or superceded by the referenced resource. 
Replaces 
Name: replaces 
Label: Replaces 
Definition: The described resource supplants, displaces, or supersedes the referenced resource. 
Is Required By 
Name: isRequiredBy 
Label: Is Required By 
Definition: The described resource is required by the referenced resource, either physically or logically. 
Requires 
Name: requires 
Label: Requires 
Definition: The described resource requires the referenced resource to support its function, delivery, or coherence of content. 
Is Part Of 
Name: isPartOf 
Label: Is Part Of 
Definition: The described resource is a physical or logical part of the referenced resource. 
Has Part 
Name: hasPart 
Label: Has Part 
Definition: The described resource includes the referenced resource either physically or logically. 

Is Referenced By 
Name: isReferencedBy 
Label: Is Referenced By 
Definition: The described resource is referenced, cited, or otherwise pointed to by the referenced resource. 

References 
Name: references 
Label: References 
Definition: The described resource references, cites, or otherwise points to the referenced resource. 

Is Format Of 
Name: isFormatOf 
Label: Is Format Of 
Definition: The described resource is the same intellectual content of the referenced resource, but presented in another format. 

Has Format 
Name: hasFormat 
Label: Has Format 
Definition: The described resource pre-existed the referenced resource, which is essentially the same intellectual content presented in another format.

hasTranscript 
Name: hasTranscript
Label: hasTranscript
Definition: The described resource pre-existed the referenced resource, which is essentially the same intellectual content presented in another format.

IsTranscriptOf
Name: IsTranscriptOf
Label:  hasTranscript
Definition: The described resource pre-existed the referenced resource, which is essentially the same intellectual content presented in another format.	We don't find this set of relations very useful and are looking to develop an RDF approach in future.	
The following are suggested additions that are not yet built in to the catalogue system.

62.	Extent	refine:
duration
size
number of files			
63.	Audio	refine:
algorithm, content = " PCM,MPEG1L1,MPEG1L2,MPEG1L3,MPEG2L1,MPEG2L2,MPEG2L3"
Sampling frequency, content = "11000,22050,24000,32000,44100,48000"
Bitrate, content ="all bitrates allowed in MPEG 2 (ISO/IEC 13818-3)> [kbit/s per channel]"
Word Length, content ="8,12,14,16,18,20,22,24"
Mode, content="mono,stereo,dual mono,joint stereo"
Duration, content ="minutes;seconds;hundredths of a second."				
64.	Video	refine:
File format and version, content ="Quicktime 4, [more]"
Duration, content ="minutes;seconds;hundredths of a second."
Frame rate, content ="25fps [more]"
Compression, content ="MPEG3 [more]"
Video encoding structure, content ="Mpeg3, [more]"
Video sound, content = ""				
65.	Text	refine:
Format and version, content = type of WP, text/ proprietary, eg "RTF, MS Word, Nisus"
Text character, content ="ASCII, Unicode, EBCDIC"				
66.	Database	refine:
Format and version, content = "MS Access, FMPro 5.5"
[more]				
67.	Executables	refine:
Code type and version, content = "Perl, Java version X, [more]"				
68.	Known system requirements	Describes the system or software necessary to access the object.
e.g. Win 98; Java Virtual machine...				
69.	Access Inhibitors	Any method used to inhibit access, which would impact on preservation procedures, such as encryption or watermarking. e.g. password access, dongle required...