sgsinclair / trombone Goto Github PK

Number of tokens returned will be likely less than the limit when a stopList is used.
The tool uses int maxPos = documentStart+limit to determine when to stop searching, however this needs to be updated when one of the tokens in the stopList is encountered.

tool/util/Geonames.java is more recent but seemingly has less functionality

tool/corpus/Geonames.java is less recent

Prevents error reporting "Unable to load documentation" In case developer does not have JSDoc installed.

Several of the unit tests are failing and it seems to be related to character encoding.

When running the tests through JUnit they pass, however.

tool/util/Geonames.java is more recent but seemingly has less functionality

tool/corpus/Geonames.java is less recent

To reproduce:

1. Create a corpus with the following:
   http://shakespeare.mit.edu/1henryiv/full.html
   http://shakespeare.mit.edu/2henryiv/full.html
   http://shakespeare.mit.edu/henryv/full.html
2. Create a new corpus with:
   http://shakespeare.mit.edu/1henryiv/full.html
   http://shakespeare.mit.edu/2henryiv/full.html
3. Reload the initial corpus.

Should produce errors with the DocumentTokens, CorpusCollocates, and DocumentContexts calls.

table=[existing table id]
verify=[boolean – just verify, id returns empty if not there]
input=[tsv data]
inputFormat=[tsv]
columnHeaders=boolean
rowHeaders=boolean
columns=[array of columns indices (numbers) or headers (strings)]

Currently can only find the index if a singular XML file was uploaded.
Needs to be re-worked to support the case where multiple XML files are uploaded.

Need tests for:

• CorpusTermCorrelations
• DocumentTermCorrelations
• TableCorrelations