CentreForDigitalHumanities / CentreForDigitalHumanities/Textcavator
Term frequency visualisation is unclear about search fields
- Dominant language
- Python
- Stars
- 12
- Forks
- 3
- Avg merge
- 3d 3m
- Merged PRs (30d)
- 9
Description
Currently, the term frequency visualisation will:
- ignore everything except text content fields
- ignore stemming
However, this is not communicated to the user. I had actually forgotten about the first point myself.
Re. that choice (excluding metadata fields, even if they are included in the query), this was implemented in part because the People & Parliament group requested it, but there were also technical reasons (https://github.com/CentreForDigitalHumanities/I-analyzer/pull/761).
The second point is just a shortcoming, I'm not sure if it's a regression or we just never got around to it.
In any case, this could be addressed by adding a "count frequencies in: X" element like the neighbouring words visualisation has.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the term frequency visualisation and compare its menu with the neighbouring words visualisation, which already shows a “count frequencies in” element. Done means the term frequency UI clearly communicates that it uses text content fields and does not apply stemming, using the proposed wording or an equivalent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100