Skip to main content

Search help

Using the CRCE search interface

1. Search interface

The CRCE search interface supports two complementary navigation modes:

  • keyword-based search
  • filter-based browsing

These may be used independently or in combination. The system is designed for exploratory listening and corpus navigation rather than formal database querying.

The search box supports keyword matching, not structured query syntax.

Users may enter:

  • example numbers
  • author names
  • contrapuntal procedures
  • textures
  • cantus-firmus labels
  • variant types

Examples of valid searches:

  • canon
  • Lusitano
  • three
  • mode 1
  • added melody
  • 57

The system does not interpret:

  • logical operators
  • field syntax
  • quotation logic
  • query expressions

For example, searches such as:

canon AND three_voice
type:canon
"added melody"

are not required and may not behave as expected. Instead, users should enter simple keywords.

3. Filters

Filters provide structured navigation across the corpus and may be combined freely.

Filter Function
Author Navigate by treatise author
Counterpoint type Navigate by procedural category
Texture Navigate by number of voices
Variant Navigate by type of realisation
Register Navigate by vocal/instrumental range configuration
Volume Navigate by corpus volume
Cantus firmus Navigate by cantus firmus identity
Canon interval Navigate by canonic interval structure

Filters operate cumulatively. For example:

  • Author + Counterpoint type
  • Texture + Variant
  • Cantus firmus + Register

Keyword search and filters may be used together. Example workflow:

  1. Select Author: Lusitano
  2. Select Counterpoint type: canon
  3. Enter keyword: three

This will restrict results to three-voice canons by Lusitano.

5. Keyboard navigation

Playback and corpus navigation may be controlled using the keyboard.

Key Action
Space Play / pause
← / → Seek backward / forward
↑ / ↓ Previous / next track

Keyboard navigation follows the order of the current search result list or volume tracklist. This enables continuous listening-based exploration without requiring pointer interaction.

6. Intended use

The search environment is designed as:

  • an analytical listening tool
  • a pedagogical navigation interface
  • a corpus exploration system