In some cases (e.g., Description), default values may be defined in the Administration database editor. In these cases, when a record is created without a field value, the default value is automatically supplied by the portal software. Default values may be overwritten by resource editors at any time. NOTE: Default values persist in a record after deletion in the portal administration database editor. This is the intended behavior, since there is no way to determine whether the value was assigned because it was the default, or because a resource administrator entered that value.
If the Date of Record Creation and Date Record Checked are left blank, the software automatically enters the current date. More information on acceptable date form can be found in the Metadata Field Definitions section.
Limited HTML tags are permitted to increase visual appeal in the Text and Paragraph field types. As the software is shipped these fields include: Title, Alternate Title, URL, Source, Relation, Coverage, Rights, Email Address, and Description. The allowable html tags include the following: bold <b>, italics <i>, underline <u>, strike <s>, anchor <a>, superscript <sup>, subscript <sub>, paragraph <p>, quote <q>, and preformatted text <pre>. An additional HTML tag is permitted in Paragraph type fields (for example, Description), break or <br> tag. Any <br> tags in text fields will be stripped after adding or updating the record in the Metadata Tool. Other than specifically allowed HTML markup, no text within these fields should be contained within angle brackets. NOTE: All HTML tags will be stripped from metadata harvested via RSS and OAI.
If that name matches names already existing in the Names table, a results list will be generated and returned. Check all the appropriate boxes, and click update. The Metadata Tool will add all names checked to the resource record. NOTE: It is important to remember that this table is populated by the user, so when you begin using it, there will be no names included (i.e., after supplied sample records are removed). As you add records, you will be adding names and will eventually build up the Names table.
If that name does not exist [as will be the case often when you begin using the Metadata Tool], or none of the results are the correct name, you may then add that name to the table. The portal software's Metadata Tool allows for a Controlled Name and a Variant Name. A Controlled Name is an official form of a name applied to all records uniformly to avoid confusion or misidentification that may impede retrieval. The Variant Name is intended to record all other forms associated with the name including acronyms, honorary titles, dropped initials, diminutives, etc. Having both a Controlled Name and Variant Names allows all records associated with this name to be linked and also for editing easily across records. The ability to add all variants makes it possible to retrieve those name forms when searching for records. Multiple Variant Names are allowed within the field. NOTE: It is recommended practice to use a semi-colon to separate the distinct values of Variant Names.
Only one image may be added to each particular Screenshot field. Additional fields are required to accommodate additional images.
After an image has been added to a record a Remove Image button will appear. To remove an image already associated with a resource record, simply click on this button. The desired image should then be deleted from the resource record.
Portal developers are strongly encouraged to also complete the Screenshot Description field whenever adding an image(s) to a resource record. This field provides explanatory text for images and graphics. According to established guidelines of accessiblity for World Wide Web resources, images or graphics should always provide appropriate explanatory text to ensure that the image's meaning is understood by persons using screen reader software (generally those who are blind or with low vision). Completing this field is an easy method to incorporate this practice into portal development workflow without modification to HTML code.
Additionally, the Screenshot Description field provides text that can be searched (when enabled by portal administrators) by the Keyword, Advanced Search, and Metadata Tool search engine.