Thanks for this sweet workaround and all my apologies for the delay. > You can use a workaround: prepare necessary metadata in a HtmlParseFilter, > which has access to the full DOM tree, and put it into ParseData.metadata. Using the surrounding page's metadata to pass data about the outlinks sounds like a *very* nice workaround to me. Would adding one metadata per Outlink make sense? These metadata could be removed in ScoringFilter.passScoreAfterParsing (I guess...). Their number should also be limited using db.max.outlinks.per.page. . Their number should be limited using Wouldn't there be ugly consequences of adding "so many" metadata even temporarily?
> ... HtmlParseFilter which has access to the full DOM tree Is it through the DocumentFragment object that is passed to HtmlParseFilter.parse? Thanks, Best regards, vinsil -- View this message in context: http://www.nabble.com/Custom-outlink-scoring-%280.8%29-tf2227127.html#a6187329 Sent from the Nutch - User forum at Nabble.com.
