RSLP Collection DescriptionData Entry Guidelines |
These guidelines are primarily intended to be used with the RSLP Collection Description Tool and should be in conjunction with the associated schema description.
Note that the agent attributes are listed once in these guidelines. They appear four times in the schema (and hence in the tool) - for the collector(s), owner(s) and contributor(s) of the collection and the administrator(s) of the location.
All the RSLP Collection Description attributes are optional - unused attributes should be left blank.
A minimal description should include either the title of the collection or the name of the location, the address or locator of the location and a short description.
Collection |
Enter the name of the collection preserving the original wording, order and spelling. Punctuation need not reflect the usage of the original. Subtitles should be separated from the title by a colon, for example:
Voices from the Dust Bowl: The Charles L. Todd and Robert Sonkin Migrant Worker CollectionWhere a collection has a well known acronym it should be provided in parentheses after the name, for example:
The Wilfred Owen Multimedia Digital Archive (WOMDA)
Although a description might contain detailed subject-specific information, at least part of the description should be understandable by an end-user with no specialist knowledge of the subject area.
Note that the text cannot be explicitly formatted in any way (by using HTML mark-up for example) - it should be treated as a single paragraph of text.
The terms used indicate the subject matter of the collection.
Recommended best practice is to select terms from LCSH level 1.
Where a scheme is used, provide a shortened version of the scheme name. The shortened version of the scheme name should be taken from the enumerated list maintained at <http://www.ukoln.ac.uk/metadata/rslp/schemes/>. Enter the complete subject descriptor, including punctuation and capitalisation, according to the relevant scheme, for example:
World War, 1939-1945 - Germany (Scheme=LCSH)
Germany - History - 1933-1945 (Scheme=LCSH)
Hitler, Adolf, 1889-45 (Scheme=LCSH)
940.43 (Scheme=DDC21)
Where more than one keyword or descriptor is provided, a repeated attribute should be used for each.
The object names used indicate the subject matter of the collection.
Where a scheme is used, provide the shortened version of the scheme name. The shortened version of the scheme name should be taken from the enumerated list maintained at <http://www.ukoln.ac.uk/metadata/rslp/schemes/>. Enter the complete object name, including punctuation and capitalisation, according to the relevant scheme.
Where more than one object name is provided, a repeated attribute should be used for each.
The names used indicate the subject matter of the collection.
Where a scheme is used, provide the shortened version of the scheme name. The shortened version of the scheme name should be taken from the enumerated list maintained at <http://www.ukoln.ac.uk/metadata/rslp/schemes/>. Enter the complete name, including punctuation and capitalisation, according to the relevant scheme.
If no scheme is used, enter personal names, where possible, surname first followed by a comma and the elements of the name that usually precede the entry element. Enter corporate names in direct form. For more precise rules see AACR2 chapters 20-24.
Where more than one name is provided, a repeated attribute should be used for each.
Where a scheme is used, provide the shortened version of the scheme name. The shortened version of the scheme name should be taken from the enumerated list maintained at <http://www.ukoln.ac.uk/metadata/rslp/schemes/>. Enter the complete statement of collection strengths, formatted according to the relevant scheme.
Enter language names in the format defined by by RFC-1766, ISO 639-2 or as a free text description of the languages (or families of languages) used in the collection.
RFC-1766 includes a two-letter language code (taken from the ISO 639-1 standard), followed optionally, by a two-letter country code (taken from the ISO 3166 standard). For example, 'en' for English, 'fr' for French, or 'en-GB' for English used in the United Kingdom
ISO 639-2 provides a list of three-letter language codes. For example, 'eng' for English.
Where more than one language is provided, a repeated attribute should be used for each.
A URI or other identifier for the collection. Internal, library or archival, identifiers can be given here.
Note that this identifier should not be the URL for the location of the resource. Note also that the RSLP Collection Description Web-based tool authomatically assigns a URN to each collection that is described.
The statement may include an indication of the number of items in the collection, the total duration of items and physical or digital space requirements.
Note that the text cannot be explicitly formatted in any way (by using HTML mark-up for example) - it should be treated as a single paragraph of text.
Enter a term taken from the list at <http://www.ukoln.ac.uk/metadata/rslp/types/>.
Enter a date range - two dates separated by a forward-slash (/). Each date should be entered according to the W3C note on 'Date and Time Formats', <http://www.w3.org/TR/NOTE-datetime>. Null dates may be used to indicate open-ended date ranges.
All the following are examples of valid date ranges:
1888/1894indicating, '1888 to 1894 inclusive', '1960 onwards' and 'February 2000 to June 2000 inclusive' respectively.
1960/
2000-02/2000-06
Enter a date range - two dates separated by a forward-slash (/). Each date should be entered according to the W3C note on 'Date and Time Formats', <http://www.w3.org/TR/NOTE-datetime>. Null dates may be used to indicate open-ended date ranges.
All the following are examples of valid date ranges:
1888/1894indicating, '1888 to 1894 inclusive', '1960 onwards' and 'February 2000 to June 2000 inclusive' respectively.
1960/
2000-02/2000-06
Enter the name or identifier of the collection refered to. If a name is entered, the data entry guidelines for collection names should be followed. If a URI is entered, it should be fully specified, for example:
http://memory.loc.gov/ammem/afctshtml/tshome.html
urn:x-cld:950615195-30859
Enter the name or identifier of the collection refered to. If a name is entered, the data entry guidelines for collection names should be followed. If a URI is entered, it should be fully specified, for example:
http://memory.loc.gov/ammem/afctshtml/tshome.html
urn:x-cld:950615195-30859
Enter the name or identifier of the collection refered to. If a name is entered, the data entry guidelines for collection names should be followed. If a URI is entered, it should be fully specified, for example:
http://memory.loc.gov/ammem/afctshtml/tshome.html
urn:x-cld:950615195-30859
Enter the name or identifier of the collection refered to. If a name is entered, the data entry guidelines for collection names should be followed. If a URI is entered, it should be fully specified, for example:
http://memory.loc.gov/ammem/afctshtml/tshome.html
urn:x-cld:950615195-30859
Enter the name or identifier of the collection refered to. If a name is entered, the data entry guidelines for collection names should be followed. If a URI is entered, it should be fully specified, for example:
http://memory.loc.gov/ammem/afctshtml/tshome.html
urn:x-cld:950615195-30859
Enter the name or identifier of the publication refered to. If a name is entered, preserve the original wording, order and spelling. If a URI is entered, it should be fully specified, for example:
http://memory.loc.gov/ammem/afctshtml/tshome.htmlPublications may include Web sites that are based on the collection.
urn:x-cld:950615195-30859
Where possible cover the following areas using terms taken from the bracketed lists:
Note that the text cannot be explicitly formatted in any way (by using HTML mark-up for example) - it should be treated as a single paragraph of text.
Note that the text cannot be explicitly formatted in any way (by using HTML mark-up for example) - it should be treated as a single paragraph of text.
Note that the text cannot be explicitly formatted in any way (by using HTML mark-up for example) - it should be treated as a single paragraph of text.
The statement may cover cover issues such as allowed users, charges, etc. and may give reasons for any restrictions that are in place (for example the physical status of the collection).
Note that the text cannot be explicitly formatted in any way (by using HTML mark-up for example) - it should be treated as a single paragraph of text.
Only enter information here that is not covered by other attributes in the collection description schema.
Note that the text cannot be explicitly formatted in any way (by using HTML mark-up for example) - it should be treated as a single paragraph of text.
Location |
Enter the name of the location preserving the original wording, order and spelling. Punctuation need not reflect the usage of the original.
Where a location has a well known acronym it should be provided in parentheses after the name, for example:
The Natural History Museum (NHM)
Enter the postal address on one or more lines. Separate address components using a comma (,).
Library and Learning Centre, University of Bath, Bath, BA2 7AY
Enter a two-letter country code (taken from the ISO 3166 standard).
uk
Enter the URL of the location. URLs must be fully specified, for example:
http://www.sosig.ac.uk/Do not use this attribute as part of the description of a physical collection. If you want to provide the URL of a Web page that describes the location, use the 'See also' attribute.
z39.50s://z3950.copac.ac.uk:2100/COPAC
The statement may include hours of access, classes of permitted user, etc.
Note that the text cannot be explicitly formatted in any way (by using HTML mark-up for example) - it should be treated as a single paragraph of text.
URLs must be fully specified, e.g.
http://www.bath.ac.uk/Library/
Related Agents |
Record concisely any significant information on the origin, progress, development and work of the organization (or organizations) or on the life and work of the individual (or individuals) responsible for the collection.
This attribute should only be used for the Collector(s) of the collection.
Maintained by: Andy Powell Version: 1.0 (2000-10) |