A little advice

[dvzhang]

Thanks for the excellent work!
And I have a little advice~
when the size of searched data is about 1G, it takes lot of time to transmit the results.
Maybe, we can use dynamic web page.
when I click "next page", the data of next page's results are transmitted.

[BeckySharp]

sounds like a great idea, I am just not 100% sure how i'd do the javascript half of the changes (If you bravely peek at the source code you'll very obviously be able to tell that i was figuring out js as I went...!)
That said, I WELCOME PRs if you want to help...! And maybe I don't need to do anything fancy, just send a diff slice of results and refresh... I guess I'd manually display the position in the results list instead of relying on the table library to do it......
else, perhaps @gcgbarbosa can help in his limited spare time bc he's great? :)

[BeckySharp]

@dvzhang also -- in the meantime, in terms of workflow, if you're mostly working on the rule dev, you can use the webapp with a smaller index (i.e., a subset of your index of interest), and when you think you have the rules you want, you can do something more like the code in Example.scala with your rules and your corpus, exporting the extractions as json or json lines...?

[dvzhang]

@dvzhang also -- in the meantime, in terms of workflow, if you're mostly working on the rule dev, you can use the webapp with a smaller index (i.e., a subset of your index of interest), and when you think you have the rules you want, you can do something more like the code in Example.scala with your rules and your corpus, exporting the extractions as json or json lines...?

hahaha, that‘s right! I can use the the code in Example.scala with my rules. But I have some friends whose major is linguistic. They also want to use Odinson.
So if you are interested in this advice, and have spare time, maybe you can do something. if not, I'm happy to do some help in next week.