Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend default search predicates #282

Open
leskneebone opened this issue Oct 17, 2024 · 3 comments
Open

Extend default search predicates #282

leskneebone opened this issue Oct 17, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@leskneebone
Copy link
Collaborator

Default search predicates are mentioned here:

https://github.com/RDFLib/prez/tree/v4.1.0?tab=readme-ov-file#language-and-search-configuration

default_search_predicates

rdfs:label
skos:prefLabel
sdo:name
dcterms:title

Suggest extending the defaults to include additional textual labels used in vocabularies:

skos:altLabel
skos:hiddenLabel

These properties capture the synonyms (semantic variants, but also including alternate spellings, acronyms etc) and are key to connecting user search terminology with resource language.

@lalewis1 lalewis1 self-assigned this Oct 17, 2024
@recalcitrantsupplant
Copy link
Collaborator

I wonder if we provide a query parameter where you can specify the search predicates so you can when running a query? In a UI you could then select whichever predicates you want (and set whatever defaults in the UI).

Would people always want to include alt/hidden labels in the search?

@leskneebone leskneebone added the enhancement New feature or request label Oct 17, 2024
@leskneebone
Copy link
Collaborator Author

Alt/hidden labels pretty much exist to improve search. In my opinion they are as essential as the prefLabel.

But I like the idea of a parameter because there could be other cases that are less clear cut. For example, schema:description / dcterms:description. Depending on the catalogue, these may improve search results, or they might just create noise and false positives. That might not be a good default, but would be good to have as an option (I'm thinking an option for an admin user, not an end user). What kind of user would use such a parameter?

@recalcitrantsupplant
Copy link
Collaborator

recalcitrantsupplant commented Oct 17, 2024

OK sounds best if we add them in with the defaults and also add an option to specify which one to use.

So this would be, including full text search:

  • For regex search, config specifies defaults (including alt/hidden). User can specify one or more of any predicate to use these instead.
  • For full text search, config specifies indexed fields. These are used as a default (search all indexed fields), and users can specify one or more fields to search, within the set of indexed fields.

This would also allow UIs to define other defaults; the UI can always pass through an alternate set of predicates to use for search.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants