[
https://issues.apache.org/jira/browse/TIKA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314680#comment-14314680
]
Nick Burch commented on TIKA-1545:
----------------------------------
We have only a stopgap thing for now! The original discussion was to have
self-hosted docs which explained what each endpoint did, what parameters it
took, what it might return, and provided a form to let a user try the endpoint
out from their browser (including different formats).
It may not be the best example, but here's something vaguely like what we
talked about: http://www.theyworkforyou.com/api/docs/getMP
We may also want a friendly welcome page for the root, which would give people
a little intro before pointing them to to the endpoint docs
Sadly I think that the current thing might've been "good enough" to slow down
work on TIKA-1269... But I think that's what we really need!
> Create tika-server Frontend
> ---------------------------
>
> Key: TIKA-1545
> URL: https://issues.apache.org/jira/browse/TIKA-1545
> Project: Tika
> Issue Type: Improvement
> Components: server
> Reporter: Tyler Palsulich
> Assignee: Tyler Palsulich
> Fix For: 1.8
>
>
> The current server homepage only displays a list of available endpoints. I
> propose a front end which will allow a user to upload a file, select a
> dropdown of output format, check boxes of metadata/content, click submit, and
> view Tika's output.
> This will be a nice feature to have along with TIKA-1301. When a potential
> user asks what Tika does for [filetype], we can direct them to the VM so they
> can try it out.
> I'll upload a patch with a new endpoint which accepts a multipart/form-data
> input file. But, it's ugly... I'd prefer to make the call with Ajax. But, I
> don't know how to that with the current tika-server setup.
> A more complex, but pretty, example of something Tika should have is
> http://any23.org/.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
