CentreForDigitalHumanities / CentreForDigitalHumanities/Textcavator
Remove `indexed` option on corpus fields
Open
code quality
good first issue
- Dominant language
- Python
- Stars
- 12
- Forks
- 3
- Avg merge
- 3d 3m
- Merged PRs (30d)
- 9
Description
In the Times corpus, there are multiple fields which have `indexed=False` set. This effectively means they will be skipped in the indexing process, while the information related to them is still read from the source files, slowing down indexing unnecessarily. Should we delete these fields? Or is there still a reason to keep them around?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.