Request For Comments (RFCs)
  • Request for comments (RFC)
  • RFC 001: Matcher architecture
  • RFC 002: Archival Storage Service
  • RFC 003: Asset Access
  • RFC 004: METS Adapter
  • RFC 005: Reporting Pipeline
  • RFC 006: Reindexer architecture
  • RFC 007: Goobi Upload
  • RFC 008: API Filtering
  • RFC 009: AWS account setup
  • RFC 010: Data model
  • RFC 011: Network Architecture
  • RFC 012: API Architecture
  • RFC 013: Release & Deployment tracking
    • Deployment example
    • Version 1
  • RFC 014: Born digital workflow
  • RFC 015: How we work
    • Code Reviews
    • Shared Libraries
  • RFC 016: Holdings service
  • URL Design
  • Pipeline Tracing
  • Platform Reliability
    • CI/CD
    • Observability
    • Reliability
  • RFC 020: Locations and requesting
  • RFC 021: Data science in the pipeline
  • RFC 022: Logging
    • Logging example
  • RFC 023: Images endpoint
  • RFC 024: Library management
  • RFC 025: Tagging our Terraform resources
  • RFC 026: Relevance reporting service
  • RFC 026: Relation Embedder
  • RFC 027: Pipeline Intermediate Storage
  • RFC 029: Work state modelling
  • Pipeline merging
  • RFC 031: Relation Batcher
  • RFC 032: Calm deletion watcher
  • RFC 033: Api internal model versioning
  • RFC 034: Modelling Locations in the Catalogue API
  • RFC 035: Modelling MARC 856 "web linking entry"
  • RFC 036: Modelling holdings records
  • API faceting principles & expectations
  • Matcher versioning
  • Requesting API design
  • TEI Adapter
  • Tracking changes to the Miro data
  • How do we tell users how to find stuff?
  • Removing deleted records from (re)indexes
  • RFC 044: Tracking Patron Deletions
  • Work relationships in Sierra, part 2
    • Work relationships in Sierra
  • Born Digital in IIIF
  • Transitive hierarchies in Sierra
  • RFC 047: Changing the structure of the Catalogue API index
  • RFC 048: Concepts work plan
  • RFC 049: Changing how aggregations are retrieved by the Catalogue API
  • RFC 050: Design considerations for the concepts API
  • RFC 051: Ingesting Library of Congress concepts
  • RFC: 052: The Concepts Pipeline - phase one
  • RFC 053: Logging in Lambdas
  • RFC 054: Authoritative ids with multiple Canonical ids.
  • RFC 055: Genres as Concepts
  • RFC 055: Content API
    • Content API: articles endpoint
    • Content API: Events endpoint
    • Content API: exhibitions endpoint
    • The future of this endpoint
  • RFC 056: Prismic to Elasticsearch ETL pipeline
  • RFC 57: Relevance testing
    • Examples of rank CLI usage
  • RFC 059: Splitting the catalogue pipeline Terraform
  • RFC 060: Service health-check principles
  • RFC 060: Offsite requesting
    • Sierra locations in the Catalogue API
  • Content-api: next steps
Powered by GitBook
On this page
  1. RFC 57: Relevance testing

Examples of rank CLI usage

All flags in the following commands should be optional, and the CLI should prompt the user for any missing information, allowing them to select from the available options where appropriate.

rank
├── index
│   ├── list
│   ├── create
│   ├── update
│   ├── delete
│   ├── get
│   └── replicate
├── task
│   ├── check
│   └── delete
├── search
│   ├── get-term
│   └── compare
└── test
    ├── run
    └── list
rank index list

List all the indices in the rank cluster.

rank index create --source <source> --target <target> --config <config>

Create a new index in the rank cluster, using data from a copy of a production index (also in the rank cluster), and a locally defined settings/mapping config.

rank index update --index <index> --config <config> --run
rank index delete --index <index>

Delete an index in the rank cluster.

rank index get --index <index>

Fetch a copy of the settings/mapping config for an index in the rank cluster.

rank index replicate --source <source> --target <target>
rank task check --task <task>

Check the progress/status of a reindex or update-by-query task.

rank task delete --task <task>

Cancel a task.

rank search --index <index> --query <query> --search-terms <searchTerms>

Run a search against an index in the rank cluster, outputting formatted results to stdout.

rank search get-terms -n <n> --timestamp <timestamp> 

Fetch a set of real search terms from the reporting cluster for each content type, and write them to a local file. n should specify the number of terms to fetch, and timestamp should specify the point in time before which search terms should be retrieved. If a timestamp is not provided, the current time should be used. Specifying a timestamp allows users to fully reproduce a test at a later date or in a different environment.

rank search compare-query-speed --index <index> --query <query> --terms <terms>

Run searches against an index in the rank cluster using a set of real search terms, and compare the speed of the candidate query against the production query.

rank test run --index <index> --query <query> --test-id <testId>

Run a test against an index in the rank cluster. Test ID should be optional, and if not provided, all tests should be run.

rank test list

List the available tests using a modified pytest --collect-only

PreviousRFC 57: Relevance testingNextRFC 059: Splitting the catalogue pipeline Terraform

Last updated 10 months ago

Update the settings/mapping config for an existing index in the rank cluster. Should allow the user to run the for all documents immediately, or leave it to be run later.

Copy an index from the rank cluster to a production cluster using .

update-by-query
cross-cluster replication