📇
Catalogue API
  • Catalogue API
  • developers
  • How users request items
  • Search
    • Current queries
      • images
      • Query structure
    • Search
      • Changelog
      • Collecting data
      • Query design
      • Query design
      • wellcomecollection.org query development index
      • Reporting and metrics
      • Work IDs crib sheet
      • Analysis
        • Less than 3-word searches
        • Subsequent searches
        • Searches with 3 words or more
      • Hypotheses
        • Behaviours
        • Concepts, subject, and another field
        • Concepts, subjects with other field
        • Concepts, subjects
        • Contributor with other field
        • Contributors
        • Further research and design considerations
        • Genre with other field
        • Genres
        • Mood
        • Phrases
        • Reference number with other field
        • Reference numbers
        • Search scenarios
        • Synonymous names and subjects
        • Title with other field
        • Titles
      • Relevance tests
        • Test 1 - Explicit feedback
        • Test 2 - Implicit feedback
        • Test 3 - Adding notes
        • Test 4 - AND or OR
        • Test 5 - Scoring Tiers
        • Test 6 - English tokeniser and Contributors
        • Test 7 - BoolBoosted vs ConstScore
        • Test 8 - BoolBoosted vs PhaserBeam
    • Rank
      • Rank cluster
      • Developing with rank
      • Testing
Powered by GitBook
On this page
  • Expectations:
  • Examples:
  1. Search
  2. Search
  3. Hypotheses

Reference numbers

Expectations:

  • Users expect search to be able to locate works by their local and external identifiers eg Catalogue API IDs, Sierra IDs etc and for these to appear first in results

  • Works that mention the reference number in other fields should come after the exact match

  • Searches should be case-insensitive

  • Users searching for an identifier and other input, should find works matching the identifier and input at the top of the results

  • Note: We have instances where a user may have one alternative version of a reference number that has been referred to as something else, e.g. WMS 682 / MS 682 / MS.682. They are the same item.

Examples:

  • L0029993

  • SA/MED/L

  • 727416i

  • HALDANE/4/16/1/4

  • MS PERSIAN 373

  • V1234567

  • V1234567 i1234567 aTrf569

PreviousReference number with other fieldNextSearch scenarios

Last updated 10 months ago