Step One: when preparing to describe your resources, there are several questions that you will want to consider - what are you describing? what kind of information do you want to record?
Are you describing a physical object, a digital object, a digital representation of a physical object? Who is my audience? What information is needed to identify the resource? What information is needed to properly contextualize it? How do I want people to find it or interact with it? How do I expect them to search for or discover it? How do I expect to use it? How do I expect others to use it, now and in the future? What information is required to communicate who owns it, who can use it, and to what extent?
Step Two: as you begin to answer the questions presented in Step One, list out the information that you would like to include as data points, e.g., title, subject, access rights, etc. For example, if you are wanting to overlay images onto a map, you will want to record coordinate data. This is your metadata wish list.
Step Three: consider the descriptive information or metadata that you may already have: Which elements or what kind of information is recorded or represented there? Is information missing about your resources? Is there information that would be challenging to find or create?
Step Four: find your "golden minimum." Determine what information is essential to facilitate discovery, identification, and to give sufficient context, but no more. What exactly the golden minimum is in the space of your project depends on your project goals and available resources.
Step Five: finalise your list of data points. Choose to codify this list as your own metadata schema or map it to an existing schema, such as Dublin Core.
Step Six: decide whether you want to make use of data value standards (controlled vocabularies, thesauri, encoding or formatting standards). If so, which standards would apply to which fields? Alternatively, you can create your own data value standards, such as a subject vocabulary specific to your topic, or collection of resources or a controlled list of names. Document your decisions as your best practices.
UCD have provided a great LibGuide to metadata, including a video guide from the National Archives of Australia.
The Dublin Core™ Metadata Element Set is a vocabulary of fifteen properties for use in resource description. The name "Dublin" is due to its origin at a 1995 invitational workshop in Dublin, Ohio; "core" because its elements are broad and generic, usable for describing a wide range of resources.
The Dublin Core Metadata Element Set is one of the simplest and most widely used metadata schema. Originally developed to describe web resources, Dublin Core has been used to describe a variety of physical and digital resources.
Dublin Core is comprised of 15 “core” metadata elements.
Dublin Core Element |
Use |
Possible Data Value Standards |
Title |
A name given to the resource. |
|
Subject |
The topic of the resource. |
|
Description |
An account of the resource. |
|
Creator |
An entity primarily responsible for making the resource. |
|
Publisher |
An entity responsible for making the resource available. |
|
Contributor |
An entity responsible for making contributions to the resource. |
|
Date |
A point or period associated with an event in the lifecycle of the resource. |
|
Type |
The nature or genre of the resource. |
|
Format |
The file format, physical medium, or dimensions of the resource. |
|
Identifier |
An unambiguous reference to the resource within a given context. |
|
Source |
A related resource from which the described resource is derived. |
|
Language |
A language of the resource. |
|
Relation |
A related resource. |
|
Coverage |
The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant. |
|
Rights |
Information about rights held in and over the resource. |
|
More information is available at: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/
This work is licensed under CC BY-NC-SA 4.0