[
https://issues.apache.org/jira/browse/NUTCH-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172489#comment-14172489
]
Julien Nioche commented on NUTCH-1870:
--------------------------------------
Hi Albin
Could you please generate your patch against the trunk? see
[https://wiki.apache.org/nutch/HowToContribute#Creating_a_patch]
@author tags are not encouraged for contributions to Apache projects - don't
have a specific reference to any discussion on this but it has been mentioned
before
Apologies if I've missed the explanation before but why do you need an
indexingfilter as well as a HtmlParseFilter? If the extracted data are in the
parse metadata then the index-metadata plugin should be able to do the indexing.
Am I right in thinking that the selection of the rule is based on a regexp on
the URL? Could the mechanism be extended so that the selection is done via an
arbitrary metadatum? for instance if a document has a given key value in its
metadata, which could be set at injection or obtained from a source URL, we
would be able to select the extraction patterns based on it.
Thanks
> Generic xsl parser plugin
> -------------------------
>
> Key: NUTCH-1870
> URL: https://issues.apache.org/jira/browse/NUTCH-1870
> Project: Nutch
> Issue Type: New Feature
> Components: indexer, parser
> Affects Versions: 1.9
> Reporter: Albinscode
> Fix For: 1.10
>
> Attachments: xsl-parse-plugin.patch
>
>
> The aim of this plugin is to use XSLT to extract metadata from HTML DOM
> structures.
> | Your Data | --> | Parse-html plugin or TIKA plugin | --> | DOM structure |
> --> |XSLT plugin |
>
>
> The main advantage is that:
> - You won't have to produce any java code, only XSLT and configuration
> - It can process DOM structure from DocumentFragment (@see NekoHtml and @see
> TagSoup)
> - It is HtmlParseFilter plugin compatible and can be plugged as any other
> plugin (parse-js, parse-swf, etc...)
> This topic has been discussed on
> http://www.mail-archive.com/dev%40nutch.apache.org/msg15257.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)