Databases search shape ambiguity

This is part of the submitted UseCaseList.

Scenario

A description of the scenario that you have in mind.

When the user looks for watermarks in the databases he doesn't want to spend more time browsing because he misinterpreted the name of the shape he was looking for. The same S-formed shape can be classified as "snake" and interpreted by the user as "ribbon".

Importance

How important do you see this use case as?

• Recommended
• Would make search easier.

Dependencies

What other use cases are affected by the implementation of this one?

• Databases usability / db integration / dating / authentication / cartography / bibliography

Input

Things that the user must/might supply to the system.

• Visual search by user.

Output

Things that the user will recieve in response to their request.

• Watermarks are found.

Difficulties

Areas in which you foresee problems/issues arising.

• Apart the ambiguity in the textual description of watermarks, there are also inherent shape ambiguities.

Example

An example supporting this use case.

• Nr. 56.132 in Piccard-Online (search with "Suche") is catalogued as "Ochsenkopf", yet to any layperson this labeling is highly unlikely to occur.

Other Information

Any other information that you think is important to include.

• ...

Comments

Comment from other partner regarding the use case.

• The snake/ribbon example gives a hint, that in some cases there exists a visual ambiguity. Information given by watermark does not allow to do decision, whether one term or another is the right one. The printed Piccard, vol. 17, is titled “Hand und Handschuh”. Piccard did not try distinction between hands and gloves. The coats of arms of the city of Augsburg – a pine cone – Piccard put to the grapes implying visual equivalence (vol. 14). Perhaps we should organize a help desk to present and to explain such multivalent images. – FriederSchmidt

-- VladAtanasiu - 13 Sep 2006