I'm writing a module that will allow "fielded" searching on CCK nodes. This is part of my "digial library content management system based on Drupal" project. I'll be demoing it at a conference in a couple of weeks, at which time I'd be happy to let everyone take a look. It's coming along nicely (battling with some stubborn "Headers already sent" messages, hacking through some theming issues, getting the drupal pager to work, etc.), but the hard parts, the indexing and boolean searching, work great. Basically, I iterate through all the fields in a CCK content type and index them on a field level. I ran this idea past one of the search.module maintainers and he said that approach was consistent with how the search_index table was intended to be used. I also want to add some administrative functions that allow you to configure your search forms in various ways, and doing so will take some time.
If you wanted to parse out certain fields from MARCXLM records, load them into fields in a CCK content type, and search on them, you could do it with the module I'm working on. You could then display the entire or partial MARCXML using XSLT. I don't plan on porting it to flexinode, however.
Reply
Drupal4libcamp
February 27, 2009, Darien Public Library, Darien, CT
This work is licensed under a Creative Commons Attribution- NonCommercial- ShareAlike 2.5 License.
Fielded searching
I'm writing a module that will allow "fielded" searching on CCK nodes. This is part of my "digial library content management system based on Drupal" project. I'll be demoing it at a conference in a couple of weeks, at which time I'd be happy to let everyone take a look. It's coming along nicely (battling with some stubborn "Headers already sent" messages, hacking through some theming issues, getting the drupal pager to work, etc.), but the hard parts, the indexing and boolean searching, work great. Basically, I iterate through all the fields in a CCK content type and index them on a field level. I ran this idea past one of the search.module maintainers and he said that approach was consistent with how the search_index table was intended to be used. I also want to add some administrative functions that allow you to configure your search forms in various ways, and doing so will take some time.
If you wanted to parse out certain fields from MARCXLM records, load them into fields in a CCK content type, and search on them, you could do it with the module I'm working on. You could then display the entire or partial MARCXML using XSLT. I don't plan on porting it to flexinode, however.