Scope of UMIL Facets
- Dominant language
- Python
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
To develop a better approach to indexing, I was wondering: what is the overall scope/goal of the facet wants to be implemented in UMIL? I can see, and have also been thinking about, some possible facets:
Instrument-level:
- HBS hierarchy #86, #414
- Contributions from UMIL users to Wikidata?
Instrument name-level:
- Include/exclude aliases #358
- Select languages to search from #429
- Include only verified labels/aliases?
- Include only labels with Wikidata sources?
I think having more instrument name-level facets would exponentially increase the time and storage required.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading issues #86, #414, #358, and #429, then compare the instrument-level and instrument-name-level facet options listed here. Done means documenting an agreed UMIL facet scope and goals, including the time and storage trade-offs, before implementation is planned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100