[
https://issues.apache.org/jira/browse/TIKA-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994687#comment-15994687
]
Tim Allison commented on TIKA-1334:
-----------------------------------
>From [~tpalsulich] on the mailing list
{noformat}
I also like d3. In general, I think we are on the same page the best option is
a web based UI.
I see a few options to get data into the frontend:
1. Static JSON
2. JSON from a server (meaning the server runs queries (either built by the
client or the server)) 3. Load a local DB (meaning the client runs queries)
>From some quick searching, 3 seems like it has poor support. I could be wrong.
1 and 2 are clearly related. If we have a working application with static JSON,
changing it to use served JSON should be straightforward (from a Java server,
probably). Static JSON will be faster than live queries, but I don't know how
long the queries take. The polar project seems to hard code queries and provide
an interface to manually enter more.
Static JSON seems easiest to get started. What do you think?
{noformat}
> Add presentation layer for results of each run
> ----------------------------------------------
>
> Key: TIKA-1334
> URL: https://issues.apache.org/jira/browse/TIKA-1334
> Project: Tika
> Issue Type: Sub-task
> Components: cli, general, server
> Reporter: Tim Allison
> Attachments: static_stats.zip
>
>
> If I'm doing this, it'll probably be vintage mid-90s html. If someone with
> some .js kung-fu wants to take this, please do.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
