From commits-return-5709-apmail-oodt-commits-archive=oodt.apache.org@oodt.apache.org Wed Aug 28 18:59:00 2013 Return-Path: X-Original-To: apmail-oodt-commits-archive@www.apache.org Delivered-To: apmail-oodt-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A6E72106D1 for ; Wed, 28 Aug 2013 18:59:00 +0000 (UTC) Received: (qmail 98670 invoked by uid 500); 28 Aug 2013 18:58:58 -0000 Delivered-To: apmail-oodt-commits-archive@oodt.apache.org Received: (qmail 97918 invoked by uid 500); 28 Aug 2013 18:58:56 -0000 Mailing-List: contact commits-help@oodt.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@oodt.apache.org Delivered-To: mailing list commits@oodt.apache.org Received: (qmail 97319 invoked by uid 99); 28 Aug 2013 18:58:56 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Aug 2013 18:58:56 +0000 Date: Wed, 28 Aug 2013 18:58:56 +0000 (UTC) From: "Rishi Verma (JIRA)" To: commits@oodt.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OODT-652) New TikaCmdLineMetExtractor MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OODT-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752731#comment-13752731 ] Rishi Verma commented on OODT-652: ---------------------------------- Hey Chris, The configuration file is expected to be a plain old Java properties file. So, just key=val type of entries. An example is attached. The extractor is basically just using the org.apache.oodt.cas.metadata.extractors.MetReaderConfigReader class to load a properties file. I was thinking we want a configuration file for two reasons: 1. When using this extractor in conjunction with OODT Crawler, a 'ProductType' must be specified somehow in order for the product to be ingested. Placing the product type in a config file is one way. Do you have any other possible methods to do this via OODT Crawler? I'd be very curious to hear! 2. Sometimes we want to place configurable metadata that is ingested with every product. The config file supports this need. What do you think? Thanks! rishi > New TikaCmdLineMetExtractor > --------------------------- > > Key: OODT-652 > URL: https://issues.apache.org/jira/browse/OODT-652 > Project: OODT > Issue Type: New Feature > Components: metadata container > Affects Versions: 0.6 > Reporter: Rishi Verma > Assignee: Rishi Verma > Fix For: 0.7 > > Attachments: OODT-652.rverma.08-27-2013.patch.txt > > > Often times, we want to ingest a product and have some basic metadata automatically extracted from it without much effort. The Apache Tika project has great features supporting the detection of and extraction of metadata associated with a product to this effect. The purpose of this issue is to integrate these metadata extraction capabilities of Tika, so that OODT can easily leverage and make use of them. > At a minimum, this issue seeks to: > * Incorporate and use Tika's 'parse' method to extract metadata automatically > * Include the text content (if any) of a document inside a new metadata element dubbed 'content'. This will be useful for lucene and solr based free-text searches -- 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