tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Judge (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-944) Extend tika-server API to be consistent with tika-app CLI
Date Sun, 01 Jul 2012 17:02:42 GMT

    [ https://issues.apache.org/jira/browse/TIKA-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404769#comment-13404769

Jason Judge commented on TIKA-944:

I'm not sure if you need more specific details, such as suggested paths, but please say if
you do. Obviously I'm not qualified enough to see the complete scope of what Tika is capable
of, so don't want to stomp over any paths that would be more suited to other functionality.
> Extend tika-server API to be consistent with tika-app CLI
> ---------------------------------------------------------
>                 Key: TIKA-944
>                 URL: https://issues.apache.org/jira/browse/TIKA-944
>             Project: Tika
>          Issue Type: New Feature
>    Affects Versions: 1.1
>         Environment: Any
>            Reporter: Jason Judge
>              Labels: exposed-functionality, tika-server
> The tika-server API (web service) provides a limited set of functionality compared to
the tika-app command-line version. Notable things missing are:
> 1. Language recognition.
> 2. Output in various formats (JSON for metadata, XHTML for the extracted text).
> Those are the two main things that would be useful to me, but ideally the server should
be able to provide all the functionality that the command-line app does, taking the command-line
as the model to follow.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message