pelias / pelias/api

[story] category weighting

Open
#151 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

processed story
Dominant language
JavaScript
Stars
259
Forks
168
Avg merge
6h 15m
Merged PRs (30d)
1

Description

revisit category weighting and try to come up with a solution which will emphasize 'more important' records.

the classic example is "newark airport" vs "newark liberty international airport"

issue defined here: https://github.com/pelias/pelias/wiki/Taxonomy-v1#sorting
related: https://github.com/pelias/api/issues/142

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked Taxonomy-v1 sorting section and the related pelias/api issue 142 to understand the existing category-weighting expectations. Then locate the API's ranking or sorting entry point; done should mean an agreed and tested way to rank records such as Newark Liberty International Airport above Newark Airport when appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.