When setting up the fields for your CONTENTdm collection, remember to treat Date fields differently. Here are some tips.
Searchable Date: Want a Date field to be searchable as a date? Set its data type to "Date" and set its searchability to "Yes". The data type lets CONTENTdm know what sort of data to expect: text, date, or full text search. Go to "fields" on the "collections" tab in the CONTENTdm Administration interface, click "edit" next to the Date field and set its properties:
Field name: Date (or Searchable Date if you prefer)
Dublin Core mapping: Date
Data type: Date Note: Now you must enter metadata in one of the date formats that CONTENTdm allows.
Hidden: No (or Yes if you want to display to the user another date field instead as described below)
A separate Display Date (optional): Have another Date field that you want to display instead, with more informal metadata in it? Some collection managers have created two Date fields -- one for searching (as described above), and another for display to the user. This is common when collections have a lot of dates that are formatted differently from the CONTENTdm standard date formats, such as "Circa 1980s" or "Undated, likely late 1800s". You can set up your fields to show the more informal date to the user but provide a date-formatted date to the search engine, if you like. Set the searchable date as described above, and also set its "Field name" to "Searchable date". Then create a second date field and edit its properties:
Field name: Display Date (or just "Date" if you are only displaying this one)
Dublin Core mapping: None (to prevent it being harvested)
Data type: Text
Digital Date: Map "Digital Date" (Date.Digital) to "None" and set "Searchable" to "No". Only the original "Date" of the item should be mapped to Dublin Core "Date" and set to be searchable. The user expects to find the date of the material when searching by date, not the date of the digitization.