3 ms·
Could you please elaborate on what you mean by "dynamically figure out where the results are"? Or how to go about doing it? #Edit. I see your first link sorta
by zo1 12y ago
Could you please elaborate on what you mean by "dynamically figure out where the results are"? Or how to go about doing it?
#Edit. I see your first link sorta answers that. And correct me if I'm wrong, but when I went there, it seemed that the library caters more towards automatic searching + paging, rather than extracting results?
- logn 12y agoIt handles extraction too, trying to find where the results are and then extracting individually the title/summary/url/date. To elaborate on the general approach I used, it was to take each node in the web page and get stats about all of them (e.g., position on page, amount of freetext, etc) and plug those stats into a neural net. I worked on a different project some years ago that took the approach of looking for repeating tag patterns in the page, focusing especially on structural tags (as opposed to ones that are purely for formatting). Another possible approach might be to just plug the whole result page into something such as Boilerpipe (https://code.google.com/p/boilerpipe/ https://code.google.com/p/boilerpipe/) and look at the set of urls in the text block it identifies.