DCB-3.1.22

Add / edit resource descriptions: Dublin Core

Main Page > Canadiana.org Digital Collection Builder user manual > DCB-3 Add / edit content > DCB-3.1 Add / edit resource descriptions (Dublin Core) > DCB-3.1.22 Dublin Core elements





1. Identifier
 * In Dublin Core, an identifier is "an unambiguous reference to the resource within a given context. Recommended best practice is to identify the resource by means of a string conforming to a formal identification system."

2. Title
 * "A name given to the resource. Typically, a Title will be a name by which the resource is formally known."

3. Creator, publisher, contributor and/or dates
 * See UM-3.1.22.1 Add new event

4. Type
 * "The nature or genre of the resource. Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element."
 * The DCB provides a data entry field using a drop-down menu to select Type derived from the Dublin Core Types taxonomy
 * This taxonomy can be edited by administrators and editors on the list taxonomy terms screen.
 * If the term you want to use does not appear on the menu, you (or your system administrator or editor) must first add it to the taxonomy.
 * For more on editing terms and adding to taxonomies, see UM-3.5 Edit taxonomies.
 * For more information on the Dublin Core Type taxonomy, see http://dublincore.org/documents/dcmi-type-vocabulary/

5. Format
 * "The file format, physical medium, or dimensions of the resource. Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME]."

6. Description
 * "An account of the resource. Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource."

7. Relation
 * "A related resource. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system."
 * The DCB implements Relation as two fields:
 * 1) Relation - parent level is a drop-down menu from which the user selects parent levels of description if the arrangement of the records is hierarchical. For example, if describing a file, the user may select the series to which the file belongs.
 * 2) Relation is a free-text field for describing other types of relationships.

8. Language
 * "A language of the resource. Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646]."
 * The DCB implements this as a drop-down menu. The user may select as many languages as desired."

9. Subject
 * "The topic of the resource. Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element."
 * The values in the subject drop-down menu is drawn from the subjects taxonomy.
 * This taxonomy can be edited by administrators and editors on the list taxonomy terms screen.
 * If the subject you want to use does not appear on the menu, you (or your system administrator or editor) must first add it to the taxonomy.
 * For more on editing terms and adding to taxonomies, see UM-3.5 Edit taxonomies.

10. Coverage
 * "The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant."
 * In the DCB this field is implemented for spatial coverage only, in the Coverage - spatial field. This field uses a drop-down menu, the values of which are derived from the Places taxonomy.
 * This taxonomy can be edited by administrators and editors on the list taxonomy terms screen.
 * If the place you want to use does not appear on the menu, you (or your system administrator or editor) must first add it to the taxonomy.
 * For more on editing terms and adding to taxonomies, see UM-3.5 Edit taxonomies.

11. Source
 * "A related resource from which the described resource is derived. The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system."

12. Rights
 * "Information about rights held in and over the resource. Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights."
 * For each description, choose the same parent record