I am assigning myself this task. I want to give back to all those that give. I know you are working very hard and your efforts are very much appreciated.
One of the issues with getting started in nutch/drupal is learning to use the nutch-site.xml. I am going to write a patch that includes the editing of that file using the Drupal interface and possibly allowing for inserting directly from the nutch-default.xml as code snippets with a small 'library' of property tags.
Take a look at the attached file. Feedback welcomed.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | nutchsitexmlmenu.patch | 1.25 KB | broncomania |
| #11 | nutchsitexml.patch | 3.99 KB | broncomania |
| nutch-site.jpg | 192.19 KB | maxmmize |
Comments
Comment #1
broncomania commentedYo, that's cool! Just make it simple. thumbs up. Where is the code?
Comment #2
maxmmize commentedI will be pushing it up here within a week. I wanted feedback while I was at it because law school midterms are coming up in three weeks and I will be out of the game a bit starting here shortly until they are over.
Comment #3
robertdouglass commentedInsofar as we want to be editing files from within Drupal, I think the interface shown is highly superior to the text area -> runbot -> write file workflow that currently exists. In other words, if we go this route (which I can see the need for) can we also do it this way for seed/urls and the regexp filters?
One of the hard things about nutch is knowing how to enable/disable plugins, and then what files to edit in order to configure them. I suppose this is a step towards baking that domain knowledge into the Drupal module which will be helpful to some people.
On the other hand, these problems are sometimes best addressed with documentation - which is sorely lacking in the nutch world, and maybe we should just be teaching people how to do this configuration?
Comment #4
maxmmize commentedIndeed, the nuts and bolts is lacking. I am not sure how much you want others to start dredging through the current documentation. If nobody is opposed I guess after I get these two things handled a good project while I am studying for my midterms would be to collect everything we have into a rtf file and then reorder it, re-engineer and re-format it to make it more clear on what path a new person should follow.
That way we can all discuss the changes, agree and have them implemented. A basic restructuring on what we have will give us a better idea of what we need.
But yes, the interface is huge if we plan to develop a local nutch/solr community. You figure for every 100 or so people, one will actively participate and grow the community.
Comment #5
maxmmize commentedSorry, figuring out CVS was too much during Real Property class...and Robert wasn't up yet or I would have bugged him.
Add to nutch.module line 71 add a new tab: nutch.module version // $Id: nutch.module,v 1.3 2010/09/30 11:21:31 dstuart
then add this to the end of nutch.admin.inc // $Id: nutch.admin.inc,v 1.1 2010/04/11 23:40:26 dstuart Exp $
I promise I will figure out CVS sometime after midterms or get with another Drupalite on Skype to work with me to get it into a format you all prefer.
Comment #6
broncomania commentedCool, is working after setting the right write permissions to the nutch-site.xml file.
Frank
Comment #7
maxmmize commentedCan you port it for me?
Comment #8
broncomania commentedWhat do you mean with port? Making a patch of your code?
Comment #9
maxmmize commentedYeah sorry, can you make a patch, I guess Dave would port it if he thought it was something to useful.
Comment #10
broncomania commentedSure I can try. Will post it the next days here.
Comment #11
broncomania commentedSo here is the patch. Hope it works
Comment #12
broncomania commentedAh I forgot the module file patch.
Comment #13
avpadernoI am closing this issue, since Drupal 6 isn't supported anymore.