You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Document's could be TextAnalysis.StringDocument and Corpus could be TextAnalysis.Corpus?
This would mean KeywordSearch complements TextAnalysis by providing fuzzy-matching capabilities its StringDocument types and Corpuses of StringDocuments.
It would also mean that it's easy to do other types of analyses (provided by TextAnalysis) beyond keyword searching on documents loaded into this library, since they would already be TextAnalysis.Corpuses.
Currently, we allow attaching arbitrary NamedTuple metadata to our documents or corpuses, which I use for storing document UUIDs and corpus UUIDs. This maybe could be upstreamed to maintain the functionality.
Document
's could beTextAnalysis.StringDocument
andCorpus
could beTextAnalysis.Corpus
?KeywordSearch
complements TextAnalysis by providing fuzzy-matching capabilities itsStringDocument
types andCorpus
es ofStringDocument
s.TextAnalysis.Corpus
es.This would be for the future (not the 0.3 release I want to get out soon).
The text was updated successfully, but these errors were encountered: