Title <unittitle>

Status	Mandatory
Description	A formal or supplied title for the unit of description
Source	Local
Format	No requirements. Should not be a single word or name. Should not be excessively long.
Collection/Component level	Required at collection level and all component levels
Tips/Recommendations	Ensure that titles make sense within the context of an online service Think about users undertaking title searches or browsing a list of titles Titles should uniquely identify the material and preferably consist of a name element, a term indicating the nature of the unit being described and optionally a topical segment Try to avoid very general titles, especially as the collection level, such as 'Miscellaneous Papers' or titles that are too brief such as 'Cooper Collection' (a common surname - maybe add forname or initials to help identify the collection) We recommend putting the dates into the date field rather than the title, as this makes it clearer to users what the dates signify It is helpful to supply the forms of material where there are only one or two, or to specify predominant forms

Examples

Input text: Ethel W. Baker Papers

EAD encoding: <unittitle>Ethel W. Baker Papers</unittitle>

Rendered in web browser as: Title: Ethel W. Baker Papers

Input text: Liverpool Association of Graduate Women correspondence, reports and other papers

EAD encoding: <unittitle>Liverpool Association of Graduate Women correspondence, reports and other papers</unittitle>

Rendered in web browser as: Title: Liverpool Association of Graduate Women correspondence, reports and other papers

Input text: John Ruskin correspondence with the Rev. W L Brown on <title>The Seven Lamps of Architecture</title>

EAD encoding: <unittitle>John Ruskin correspondence with the Rev. W L Brown on <title>The Seven Lamps of Architecture</title></unittitle>

Rendered in web browser as: Title: John Ruskin correspondence with the Rev. W L Brown on The Seven Lamps of Architecture

ISAD(G) 3.1.2 Title