Difference between revisions of "Relation element"
Ccrussell1 (talk | contribs) (→Required?) |
Ccrussell1 (talk | contribs) (→Guidelines for Creation of Content) |
||
| Line 24: | Line 24: | ||
This where your element's indexing guideline is written out. ''Whenever possible'', you must write out a step-by-step data entry procedure including where to obtain the data for each image. (NOTE, not all elements are amenable to specific data entry procedures; we will discuss in class.) | This where your element's indexing guideline is written out. ''Whenever possible'', you must write out a step-by-step data entry procedure including where to obtain the data for each image. (NOTE, not all elements are amenable to specific data entry procedures; we will discuss in class.) | ||
| + | |||
| + | |||
| + | Use the relation element only if it is necessary as indicated by the presence of asterisks (*) beside the image file names. | ||
| + | The relation element should be completed following the completion of the identifier. | ||
| + | |||
| + | When adding the relation element, assume that each set of images with asterisks is already in sequential order. Number the images accordingly, i.e. given the set [img_8237*, img_9283*, img_7274*], img_8237 is 1, img_9283 is 2, and img_7274 is 3. | ||
| + | |||
| + | After the identifier for each image, add an underscore (_) and the relation number for each image. For example, img_8237 would become "identifier_1." | ||
===Examples=== | ===Examples=== | ||
Revision as of 20:13, 30 March 2019
Contact Caitlin with your questions about indexing this element
Contents
Complete These Sections of your Element's Indexing Instructions
- Example element description: This is the reference template for how to create the indexing guidelines entry for your element
Label
Relation
Element Description
The relation element allows us to clarify which images are directly related to each other because they depict events that have occurred in a sequence. This provides additional context for each image and allows the end user to better understand how the still images fit together.
Required?
Optional. Not all images will be part of a sequence.
Repeatable?
The relation element cannot be repeated. Each instance of the relation element is unique to both the set of sequential images to which it belongs and the place of each image within the set.
Guidelines for Creation of Content
This where your element's indexing guideline is written out. Whenever possible, you must write out a step-by-step data entry procedure including where to obtain the data for each image. (NOTE, not all elements are amenable to specific data entry procedures; we will discuss in class.)
Use the relation element only if it is necessary as indicated by the presence of asterisks (*) beside the image file names.
The relation element should be completed following the completion of the identifier.
When adding the relation element, assume that each set of images with asterisks is already in sequential order. Number the images accordingly, i.e. given the set [img_8237*, img_9283*, img_7274*], img_8237 is 1, img_9283 is 2, and img_7274 is 3.
After the identifier for each image, add an underscore (_) and the relation number for each image. For example, img_8237 would become "identifier_1."
Examples
If appropriate, provide data entry examples
Notes
Provide additional information about your element, including links to other guidelines with examples that clarify your entry.
Back to Metadata Project - Spring 2019
