Editing Field Properties
You can edit collection metadata fields if you have rights to configure settings and field properties.
Collections have two sets of metadata fields: collection fields and administrative fields.
Administrators can view and edit the set of administrative fields, however, some of these field types are system-defined and cannot be edited.
The field types are displayed in the Metadata Fields and Edit Field pages.
Field Name. The names of the metadata fields. These fields can be changed to more closely reflect the contents of a collection. The maximum length of a field name is 60 characters.
DC Map. Shown as Dublin Core Mapping in the Edit Field page. Determines which field in the Dublin Core element set that the field maps to. This is particularly important when searching across multiple collections. Fields mapped to the same Dublin Core element can be queried in searches across collections.
The Dublin Core Metadata Element Set and Element Refinements recommended by the Dublin Core Metadata Initiative are available from the Edit Field Properties page. Fields mapped to a simple (unqualified) Dublin Core element (for example, "Relation") will be searched in queries on a qualified version of that element (for example, "Relation-Is Part Of"). Queries on a simple (unqualified) Dublin Core element will search fields mapped to all qualified versions of that element.
Data Type. The type of data. Currently supported data types are Text, Date, and Full Text Search. See Changing Data Types.
Large Field. Shown as Show Large Field in the Edit Field page. Determines how a field is displayed within CONTENTdm Administration and the Project Client. This field setting does not change the amount of text that you can enter. It only changes your view of the text box so that you may more easily enter a large amount of text. The single-byte character limit is 128,000 for each field. The double-byte character limit is 64,000 for each field. The drop-down list provides two choices as to how the field will be displayed in the Web editing functions and the Project Client.
- Choosing No displays the field as a single-line text box.
- Choosing Yes displays the field as a multiple-line text box.
Search. Shown as Searchable in the Edit Field page. Defines whether or not the field is indexed for search queries. If so, this field will appear in the search screen drop-down lists and can be used to perform text queries to identify and retrieve items from the collection. If a field is not searchable, the field will not appear on the query screen but will be displayed when the metadata for an item is retrieved.
Hide. Shown as Hidden in the Edit Field page. Defines whether or not the field is shown to all users. Fields marked as hidden will not appear in the public Web interface but will be visible to administrators and catalogers through the Project Client and CONTENTdm Administration.
Required. Defines whether the field is required for all items in the collection. Fields designated as required are indicated in item editing interfaces, including CONTENTdm Administration and the Project Client. Items missing metadata in required fields cannot be added to the pending queue, and they cannot be approved using the detailed approval queue actions. (Items that do not have metadata in required fields are approved automatically if you use the full approval queue actions, including scheduled approvals.) You can define which fields are required. The Title field is required by default and cannot be changed. (Note: The Required property is ignored when using Connexion digital import.)
Vocab. Shown as Controlled Vocabulary in the Edit Field page. Indicates whether or not a vocabulary has been defined for a field and whether that vocabulary is shared across fields and collections. Controlled vocabulary is a way to limit the terms entered into a field to only those in the vocabulary list.
The administrative fields are system-defined. You can edit some properties of these fields, but you cannot move or delete them. All administrative fields can be searched and mapped to Dublin Core (DC map), if you edit the default properties. All administrative fields are hidden by default.
The large field designation does not apply to any of the administrative fields, and you cannot edit them by using the Find and Replace function.
Archival file. Contains volume and file name information about the archival file associated with the item. The display of the field is determined by the Hidden field property setting, which can be viewed and configured on the Metadata Fields page in CONTENTdm Administration under the Collections tab.
OCLC number. Contains the OCLC number for items added to CONTENTdm using the Connexion client. For more information about using Connexion, see Using OCLC Connexion Digital Import (PDF tutorial.) If your collections are harvested by WorldCat, the items are also assigned an OCLC number, which you can then enter in this field. The OCLC number is a unique identifier within WorldCat.
Date created. Indicates the date the item was first added to the collection and indexed.
Date modified. Indicates the last date the item was edited and indexed.
CONTENTdm number. Contains the item pointer that identifies the item in CONTENTdm.
CONTENTdm file name. Contains the name of the digital file stored in CONTENTdm.
Editing a field property could make profound changes to the collection and increase the functionality of the collection.
Two sections that have special functionality are changing data types and controlled vocabulary.
Changing a data type means using the drop-down list to change the field's Data Type to Text, Date, or Full Text Search.
Text is the most common data type and has no rules for implementation.
Date is used when you want to enter a date and keep the integrity of the date format to support accurate sorting and date range searching. A Search by Date option is available on the Advanced Search pane, if one or more collections contain a searchable field with the data type set to Date. Using the Date type requires the Project Client user to understand formatting rules for entering dates.
Full Text Search has special properties that distinguish it from a text field. Only one full text search field is allowed per collection.
A full text field is required if you need to activate the transcript functionality within CONTENTdm. This data type allows transcripts to be used with the Metadata Templates or when creating compound objects. See About Working with Full Text. If you do not have a field with full text searching enabled, the Transcripts section of the wizards will be inactive.
Having a full text field enables you to automatically extract text from PDFs. The full text search field must be empty when you import the PDF. For more information, see Importing PDFs.
If you import an Encoded Archival Description (EAD) file and want the data in the EAD to be extracted and added to the metadata record, you must have a full text field. See Add Finding Aid for more information.
If an item has a Full Text Search field, end users can search the text while viewing the item.
A full text field also enables special features for viewing and searching compound objects. When you view a compound object in a collection that has a Full Text Search field, a search tab displays in the viewer. Clicking the search box allows you to search the full text contained in the compound object. You also have the ability to see the page and text view in a separate tab in the viewer.
When using spell check in the Project Client, Full Text Search fields are not checked. You can choose to check full text fields by changing a setting in the Project Client. See Checking for Spelling Errors for more information.
You can also choose whether the full text is displayed within the metadata by configuring the Items > Full Text option in the Website Configuration Tool. For more information, see Items.
A controlled vocabulary defines a list of valid terms that can appear in metadata fields within CONTENTdm. A controlled vocabulary enables an administrator to restrict metadata in selected fields to specific words or phrases. An administrator establishes which fields will have a controlled vocabulary. Controlled vocabularies can be shared between fields and collections, which means they can edited by other collection administrators. For information on enabling a controlled vocabulary and best practices for sharing, see Using Controlled Vocabulary.
To edit a field property:
In the Field Properties page, determine which field you need to change.
Click Edit in that field row. The Edit Field page opens.
If desired, make changes to Field Name. Use drop-down lists to make changes to Dublin Core Mapping, Data Type, Show Large Field, whether the field is searchable, whether the field is hidden or required, and whether it has controlled vocabulary.
Click Save Changes.