Specifications for Search Forms and Results Hitlists

Principles

• All hit lists should display title/creator/date.
• All advanced search forms should look like standard web advanced search forms. An example would include the advanced search in VIRGO, where a series of input boxes are aligned next to a series of index dropdown boxes.

Specifications for Hitlists

All hitlists will now pull from the descmeta & so the specs are identical:

• <descmeta>
• <presentation>
• <displayAgent>
• <sortAgent>
• <displayTitle>
• <sortTitle>
• <displayDate>
• <sortDate>
• </presentation >
• </descmeta>

Examples:

• If the elements are strung together in the display, end each element with a full stop & bold only the title.

Great Expectations. Dickens, Charles. 1861.

Harriet Tubman Series #1. Lawrence, Jacob. 1939-1940

• If the elements are not strung together in the display, no punctuation is needed (the MSG prefers this option. Even though it consumes more screen space, we believe it is easier to read.):

Great Expectations
Dickens, Charles
1861

Harriet Tubman Series #1
Lawrence, Jacob
1939-1940

When displaying hitlists alphabetically (or by date), the results should sort on:

• <descmeta><presentation><sortTitle>
• <descmeta><presentation><sortAgent>
• <descmeta><presentation><sortDate>

and display on:

• <descmeta><presentation><displayTitle>
• <descmeta><presentation><displayAgent>
• <descmeta><presentation><displayDate>

Image Advanced Search Form

The advanced full-text search needs to look more like a web advanced search screen:

• input box1 index dropdown
• input box2 index dropdown
• input box3 index dropdown

limit by:

• input box date (with example format in parens)
• input box collection

Changes from Current Form

• replace “time of content” with “subject (date)”
• replace “place of content” with “subject (place)”
• replace “place created or housed” with “location”
• replace “physical description” with “materials”
• dropdown order:
• anywhere
• title
• creator
• This is indexing <agent>, and is getting creators & providers (including corporations) but not people as subjects.
• date created or changed (with example format in parens)
• location
• subject
• ideally subject by itself will also include indexing of covtime & covplace.
• subject (name)
• indexes subject also
• subject (date) (with example format in parens)
• indexes covtime
• subject (place)
• indexes covplace
• culture
• style
• description
• materials

Cross Collection Advanced Search Form

 Change “Cross Collection search” to “Cross Collection Catalog Search” (to emphasize that this is a metadata search.

On the text & image search, the advanced search button is a blue button more towards the top of the screen. On the cross collection search, it says “Advanced Cross-Collection Search” within the basic search box. This needs to be made consistent with the others.

The advanced full-text search needs to look more like a web advanced search screen:

• input box1 index dropdown
• input box2 index dropdown
• input box3 index dropdown

limit by:

• input box date (with example format in parens)
• input box collection

Change/add to dropdowns & order as:

• anywhere
• title
• creator
• date created (with example format in parens)
• location
• subject (date) (with example format in parens)
• subject (place)
• subject
• ideally subject by itself will also include indexing of covtime & covplace

Text Advanced Search Form

keyword anywhere:

• input box1 proximity dropdown
• input box2

limit by:

• input box author
• input box date (with example format in parens)
• input box collection

We need some way to indicate to the user that they can use the “limit boxes” without using the “keyword anywhere”. This will need design attention.