Title

<titleInfo><title>
<nonSort> [Title of Resource]
</titleInfo>

One title must be included. Title must be inside the <titleInfo> wrapper element. If the title starts with a definite or indefinite article (the, an, etc.), it is desirable to include these characters, and the space following in a <nonSort> sub-element.

Resource Type

<typeOfResource with value = [value from enumeration list]> </typeOfResource>

Permitted values include:

• notated music
• manuscript music
• sound recording-musical
• text
• still image
• moving image
• multimedia
• mixed material
• three dimensional object

One instance must be included.

Date

<originInfo>
<dateIssued encoding="marc">YYYY<dateIssued>AND, if desired
<dateIssued encoding="iso8601">YYYYMMDD</dateIssued>AND/OR
<dateCreated="iso8601">YYYYMMDD</dateCreated> AND/OR
<dateCaptured="iso8601">YYYYMMDD</dateCaptured> AND/OR
<dateValid="iso8601">YYYYMMDD</dateValid> AND/OR
<dateModified="iso8601">YYYYMMDD</dateModified> AND/OR
<copyrightDate="iso8601">YYYYMMDD</copyrightDate> AND/OR
<dateOther="iso8601">YYYYMMDD</dateOther>
</originInfo>

For date ranges:

<originInfo>
<dateIssued>1967-1987</dateIssued>
<dateIssued point="start" encoding="iso8601">19680000</dateIssued>
<dateIssued point="end" encoding="iso8601">19870000</dateIssued>
</originInfo>

For uncertain dates (use appropriate sub-element):

<originInfo>
<dateIssued>c. 1967</dateIssued>OR
<dateIssued qualifier="questionable">1967</dateIssued>
</originInfo>

One or more date sub-elements must be included. Dates must be inside the <originInfo> wrapper element.

Please note that we required one instance of <dateIssued encoding="marc">YYYY;/dateIssued> as this populates a key date sorting field in MARC records. MARC records include encoded dates used for sorting and retrieval, and non-encoded dates visible to the user. Please note that although MODS supports qualifiers such as "inferred", "questionable" or "approximate", the only qualifier which can be successfully converted to a textual data field in MARC records is "questionable". For this reason, you may prefer to use textual equivalents of the qualifiers in your non-encoded data fields, e.g."c", "?", "approx". We can use a single encoded date statement to populate coded and textual date fields.

Use <dateIssued> for published printed music, or music released by a record company.

Use <dateCreated> for unpublished printed music or sound recordings.

Use <dateCaptured> for recording dates.

Encoded dates must conform to ISO8601 (but with no dashes in the string). Fill MMDD with zeroes if your system does not record this information.

Issuance

<originInfo>
<issuance>monographic</issuance>
</originInfo>

Issuance must be inside the <originInfo> wrapper element. The value "monographic" is used solely to distinguish "single" publications from serial or journal publications. Use "continuing" for ongoing publications such as journals. These fields will not be displayed to the public, but are required for NBD management processes.

Australian Content Indicator

<subject>
<geographicCode="marcgac">u-at---</geographicCode>
</subject>

Note:

The Australian content code (geographicCode) u-at--- must be inside the <subject> wrapper element. This data is used to indicate that the item has Australian content and is especially important to ensure that items of Australian music or about Australian music published overseas are selected and represented in Music Australia. It is also useful for items published in Australia so we ask that you include this information even if you have used the Australian place code at for the place of publication in <originInfo>.

Music Subject Heading

Selection for Music Australia requires:

• Australian content indicator

and either:

• Resource type notated music, manuscript music, or sound recording-musical, OR
• At least one LCSH (Library of Congress Subject Heading) music related heading. The heading may contain the term for a musical genre, instrument or person. This will enable us to identify and extract music related records from the Australian National Bibliographic Database. If you cannot map your own subject/genre terms to LCSH, please include the boilerplate:

<subject authority="LCSH">
<topic>Music Australia</topic>
</subject>

in each record.

Holding or Managing Organisation

<location>
<physicalLocation>[Your NUC code]</physicalLocation>
<location>

Notes:

One instance only. If you do not have a NUC (National Union Catalogue) code, please contact the Music Australia administrator. This code will be used to display the name of the organisation contributing the record and will be linked to further information about your organisation, including ordering and inter-library loan services.

URL for online items only

<identifier type="uri">[http://yourdeliverysystem.html]></identifier>

OR

<identifier type="uri" displayLabel="[Text identifying an individual constituent part and/or delivery version associated with the resource]">http://yourdeliverysystem.html</identifier>

AND/OR

<location>
<url>[http://yourdeliverysystem.html]></url>
</location>

OR

<location>
<url displayLabel="[Text identifying an individual constituent part and/or delivery version associated with the resource]">[http://yourdeliverysystem.html]></url>
</location>

Notes:

The electronic location of your resource must be inside either the <location> or <identifier> wrapper elements.

MODS 3.0 supports inclusion of this data in either field. On conversion to MARC, this data will be mapped once only.

If you wish to reference individual delivery versions of your online resource, please use the displayLabel attribute to clearly identify your versions, i.e. Thumbnail, View, Examination; Realsound High Bandwidth, Realsound Low Bandwidth; Quicktime; Windows Media Player etc.

See notes below on referencing electronic locations of individual contents.

Administrative Information

<recordInfo>
<recordContentSource>[Your NUC code]
<recordCreationDate with encoding ="iso8601">[YYYY]
</recordCreationDate>
<recordChangeDate with encoding="iso8601">[YYYYMMDDHHMM.S]
</recordChangeDate>
<recordIdentifier>[Your system number]
</recordIdentifier>
<languageOfCataloguing authority="iso639-2b">eng
</languageOfCataloguing>
</recordInfo>

Notes:

Data for each sub-element of the <recordInfo> wrapper element must be supplied as specified. Dates must conform to ISO8601 (but with no dashes in the string). Fill MMDD and DDHH.S with zeroes if your system does not record this information. Replace English code "eng" with appropriate ISO639-2b code if your record (not the item itself) is in a language other than English

Name

Encoded:

<name>
<namePart>[Surname, Firstname]</namePart>
</name>

Notes:

Name must be expressed as <namePart> inside the <name> wrapper element.

AND/OR Statement of responsibility

<note with type="statement of responsibility">[Text]</note>

Note:

Use a statement of responsibility note to record information about the people or organisations responsible for the item as recorded on the item itself, e.g. "Words and music by Jack Lumsdaine", "Arranged by Percy Grainger", "Words by Jack Lumsdaine; music by Jack O"Hagan".

Name types

<name type="personal">
<namePart>Surname, Given</namePart>
</name>

Note:

Permitted name type values are:

• personal
• corporate
• conference

Publisher/Label

<originInfo>
<publisher>[Name of publisher]</publisher>
</originInfo>

Note:

Publisher or record label name must be inside the <originInfo> sub-element.

Copyright date

<originInfo>
<copyrightDate encoding ="iso8601">YYYYMMDD</copyrightDate>
</originInfo>

Note:

Include copyright date if this information is known, and is different from publication, release or other specified dates.

Place of publication or release

<originInfo>
<place>
<placeTerm type="text">AND/OR
<placeTerm type="code">
</placeTerm>
</place>
</originInfo>

Notes:

Place of publication must be inside the <originInfo><place> sub-element. Text only data is acceptable. If coded data is included, please use the MARC country codes, available at: http://www.loc.gov/marc/countries/cou_pt2codes.htmlcountry code

OR the Australian place codes available at:

http://www.nla.gov.au/kinetica/marccodes.html

The MARC code for Australia is at. Addition of this code is highly desirable, as it is another means of ensuring selection of Australian content.

Edition

<originInfo>
<edition>
</originInfo>

If the item is not the first edition, include information on the edition if known.

Extent

<physicalDescription>
<extent>[Text defining extent of resource]</extent>
</physicalDescription>

Note:

One instance should be included. Extent must be inside the <physicalDescription> wrapper element. This field can include: the dimensions and pagination for scores; the number of sound carriers associated with a sound recording; the total playing time of a sound recording; additional information about the physical resource, including illustrations etc.

Name Roles

<name>
<namePart>Surname, Forenames</namePart>
<role>
<roleTerm authority="marc" type="text">[Role text]</roleTerm>
</role>

AND/OR

<role>
<roleTerm authority="marc" type="code">[Role code]
</roleTerm>
</role>
</name>

Note:

Inclusion of role relator codes or terms, as specified by the Library of Congress at:

http://www.loc.gov/marc/sourcecode/relator/relatorlist.html

will assist users to identify the individual roles played by multiple individuals and organisations associated with a resource. Multiple terms/codes can be assigned to individual names. MARC relator terms and codes of special interest to Music Australia include:

• arranger [arr]
• choreographer [chr]
• composer [cmp]
• conductor [cnd]
• creator [cre]
• director [drt]
• editor [edt]
• interviewee [ive]
• interviewer [ivr]
• librettist [lbt]
• lyricist [lyr]
• performer [prf]
• producer [pro]
• transcriber [trc]
• translator [trl]

If you wish to indicate that one person or organisation has played a principal role, use the term/code creator in addition to more specific role term/codes.

Contents

<relatedItem type="constituent">
<titleInfo>
<title>[Title]</title>
</titleInfo>
<name type="personal" OR "corporate">
<namePart>Surname, Given</namePart>
</name>
</relatedItem>

AND/OR

<tableOfContents>Title/Name " Title/Name " Title -- Title--</tableOfContents>

Note:

Wherever possible, individual contents, e.g. songs within an album of published music or tracks on a sound recording, should be described as <relatedItem type="constituent"> which supports full description of titles, names, roles, dates, individual electronic locations etc., rather than in the Table of Contents.

This will assist users to navigate between related music items that are contained within publications, e.g. a song printed in a music album and a performance of a song on a sound recording compilation.

Displaying these entities will help users to identify and navigate between related music items.

Please note that MARC records do not currently support inclusion of individual electronic locations for constituent parts. As any constituent part <location><url> sub-elements will be transferred to the MARC 856 field, inclusion of the "displayLabel" attribute will assist users to identify the part they are interested in.

Note or Abstract

<note>[Text]</note>
<abstract>[Text]</abstract>

Note:

Any other significant information about the item can be included in a <note> or <abstract> element. Use Note with the appropriate type attribute for short notes about the item. Use Abstract for longer prose descriptions or summaries of the item.

A list of agreed <note> types and MARC mappings if available is at:

http://www.loc.gov/standards/mods/mods-notes.html

Note types of interest to Music Australia contributors include:

• Biographical
• Performers
• Statement of Responsibility
• Venue

Standard Identifiers

<identifier with type=[value from MODS list]></identifier>

Standard identifier types in the MODS suggested identifier values include:

• ISBN (International Standard Book Number)
• ISMN (International Standard Music Number)
• ISRC (International Standard Recording Code)
• ISSN (International Standard Serials Number)
• ISTC (International Standard Text Code)
• Matrix Number
• Music Plate Number
• Music Publisher Number
• SICI (Serial Item and Contribution Identifier)
• UPC (Universal Product Code)

Note:

ISBN, ISMN and ISRC data should always be included if this data is available. Please note that ISBNs will be checked for validity.

Access Conditions

<accessConditions>[Text]</accessConditions>

Minimum of one instance should be included. The text included may be access conditions specific to the resource, or a generic "Contact the [contributor] for access information" message.