You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2013/02/27 23:55:12 UTC

[jira] [Updated] (TIKA-1090) Improve Java Documentation for Apache Tika Metadata

     [ https://issues.apache.org/jira/browse/TIKA-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lewis John McGibbney updated TIKA-1090:
---------------------------------------

    Attachment: TIKA-1090.patch

The attached patch cleans up (and satisfies) my initial problem with this issue. My suggestion to add the Feed.java class has been dropped. Typically one will utilize some other existing vocabulary (already within Apache Tika) to represent fields their Metadata fields in a more consistent way. This is OK and I am happy with this.
So, now I realize that there is more work to be done in Nutch rather than here in Apache Tika.
                
> Improve Java Documentation for Apache Tika Metadata
> ---------------------------------------------------
>
>                 Key: TIKA-1090
>                 URL: https://issues.apache.org/jira/browse/TIKA-1090
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata
>    Affects Versions: 1.3
>            Reporter: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 1.4
>
>         Attachments: TIKA-1090.patch
>
>
> As I described on user@ here [0], I was not happy with the Javadoc for Metadata (as it was not explicit about what to replace the legacy Tika Metadata vocabulary with) so I therefore thought it was important to provide a documentation patch to make it more clear to devs/users wishing to build on the Tika Metadata functionality.
> This simple patch merely substantiates on the Java documentation for the Metadata class further explaining how the Tika API has changed. In addition other methods now are explicit about what we SHOULD now use. Finally, it also introduces a Feed.java metadata interface (which I can remove if unnecessary/unrequired) which merely introduces some consistent fields we would expect Rome rss/atom/feed parser library to obtain. The final Feed class is a legacy class from the Apache Nutch metadata package.
> I will work on the patch today and submit it here in due course.
> [0] http://www.mail-archive.com/user%40tika.apache.org/msg01156.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira