The Cleveland Museum of Art
CMS Demonstration Scenarios
Curatorial: Search capabilities demonstrate how:
1. A curator might determine how many works are in the collection were once owned by an individual?
2. Which works in a collection were shown in a specific exhibition?
3. How many times in the last x number of years have works been loaned to exhibitions at a specific museum?
4. Which works in the collections are by American artists who were born in Ireland?
5. When was a specific work last on public display in the galleries?
6. Sort works by donor
7. Sort works by subject
8. A user can export records to a tombstone label?
9. A user can export records to an art movement form?
General: Searching
Exact, phrase and keyword options should be available for all indexed fields. Wild card searching should be an option.
All fields should be indexed and all indexes should be searchable exclusively or in combination.
EXAMPLES:
Find all records with blue in the title and painting in the material type.
"Words adjacent," you can type in the phrase German expressionism and the system will understand that you want only records that have the word German NEXT to the word expressionism.
Boolean operators AND, OR, and NOT in your search. For example, you could type (prints OR drawings) AND Picasso to retrieve all records having prints or drawings in them, together with the word Picasso.
Word Stemming to find matches that contain portions of words. For example, paint? will retrieve paint, paints, painting, paintings, painter, etc. In another example, ? ology will retrieve anthropology, archaeology, egyptology, etc. The ? character may also be used to find variant spellings. For example, brueg?el will find both brueghel and bruegel.
If you searched Frederick Church and wanted to expand your search to other landscape paintings owned by CMA a subject link would allow you to do this. Additionally, if you wished to search all works by Church owned by CMA in line-linking would be functional.
PAHMA
From Services Team Design Meeting August 27, 2009, possibly relating to ordering search results:
Specifying Sort Order
Another key concept that emerged from the design meeting was that of sort order. This discussion touched on how clients/applications should be able to query objects (or the services that provide them) for their sort keys, and on how sorting might work. One model:
- There would be some general algorithms for sorting, presumably varying by data type.
- Museums could provide their own set of rules for sorting any particular key, which would override the general algorithm. Examples: "sort numerically on the first part of an accession number, ignore the hyphen that follows, then sort string-wise on the next part..." or "ignore initial articles, like 'the', unless the name is in French".
- There would be an ability to provide sorting 'hints' on a record-by-record basis that would effectively change the sort position of those records.
The ID Service will likely need to provide a mechanism for sorting on Object numbers and Other numbers.
Walker Art Center
From Walker Art Center - January 26, 2010:
Add Comment