Changing from a plugin to a standalone CLI application

[jzonthemtn]

Changing from a plugin to a standalone CLI application.

[wrigleyDan]

I left comments regarding pipeline names in the scripts.

I tested calculating judgments with Chorus and got a bunch of errors connected to the JSON structure and fields of the UBI events and queries. I did some local changes and fixed the findings but I think it makes sense to look at them together to make sure we make changes in the right place (here vs Chorus vs the specification vs the UBI JS client).

Other findings:

• Running the query set generator with a querySetSize of 5 resulted in 6 queries in the query set.
• Running a query set reported a successful run (Query set run complete: ...). However there were no calculated metrics stored.

Let's have a look together.

[jzonthemtn]

• Running the query set generator with a querySetSize of 5 resulted in 6 queries in the query set.

Found and fixed this one.

[jzonthemtn]

• Running a query set reported a successful run (Query set run complete: ...). However there were no calculated metrics stored.

I got the metrics indexing now. I had that part removed for a bit. (doh)

[wrigleyDan]

Nice work!

I had to make a few changes to the data model and with the last run I only saw judgments of value 0. Might be data related (the calculation is correct, the event data I have is just rubbish), might be something in the code (the calculation should give us something else for the event data). I'll have a closer look in the next review.

[wrigleyDan]

One last request, a renaming request. Other than that: My brief test worked. I tested functionally (=does everything compile and run without errors?)

I got all 0s for all judgments (and as a consequence also for the search metrics) but again, that's something that may well be data-specific that has nothing to do with the implementation.

I'd do these test outside of this PR that really is meant to move from plugin to standalone app.

[wrigleyDan]

LGTM