Search & Browse Tenant Configuration (UXPROD-4196)

[UXPROD-4203] Ability to configure search indexes Created: 14/Apr/23  Updated: 01/Dec/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Search & Browse Tenant Configuration

Type: New Feature Priority: P3
Reporter: Christine Schultz-Richert Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: LC4, SolutionArchitecture, loc, metadatamanagement, search
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Search & Browse Tenant Configuration
Front End Estimate: Out of scope
Front End Estimator: Khalilah Gambrell
Back End Estimate: XXXL: 30-45 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Spitfire
PO Rank: 0

 Description   

Current situation or problem:

In scope

  • Configure indexes based on:
    • String of subfields
    • String of subfields in a grouping
    • Single repeatable or non-repeatable subfield
  • Configure/modify keyword indexes
  • Customized stop-word list
  • Ability to define whether indexes are available in the discovery layer
  • Configure primary/secondary/tertiary subsorts
  • Define normalization rules:
    • For left-anchored indexes
    • Normalization in keyword tokenization
  • Create keyword indexes for domain-specific metadata (financial data, serials check-in, circ, etc.)

Out of scope

Use case(s)

  •  

Proposed solution/stories

  •  

Links to additional info

Questions



 Comments   
Comment by Khalilah Gambrell [ 16/May/23 ]

Hey Christine Schultz-Richert  - can you clarify this feature? 

Generated at Fri Feb 09 00:38:04 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.