Ok, it was ridiculously easy to just take that function and put it into a module and activate it. For some reason, calling it a "module" was daunting. The search hook should be easy now too - thanks.
I definitely will try out search_attachments for all of our pdfs.
As far as searching individual elements - this has to go for MARCXML records too, right? You're going to want to search and create views by author, title, subject, etc., right?
The main place that XSL hurts is in processor time. Drupal won't work on a page for more than 30 seconds, so I generally can't transform more than 200 documents at a time, which is a problem if I want to sort all 15,000 of them by zip code.
MySQL obviously wins here, if I stored zip codes in a zip code field, I could SELECT count(*) and GROUP BY and be done with it.
But I'm not ready to give up on the XML yet, however stubbornly. My sense was that you wanted to keep MARCXML around also, yes?
Now that I've written a "module" and have seen it's not so scary, it might make sense to create a separate search index, at least for the fields I want to use in views.
Reply
Drupal4libcamp
February 27, 2009, Darien Public Library, Darien, CT
This work is licensed under a Creative Commons Attribution- NonCommercial- ShareAlike 2.5 License.
neat
Ok, it was ridiculously easy to just take that function and put it into a module and activate it. For some reason, calling it a "module" was daunting. The search hook should be easy now too - thanks.
I definitely will try out search_attachments for all of our pdfs.
As far as searching individual elements - this has to go for MARCXML records too, right? You're going to want to search and create views by author, title, subject, etc., right?
The main place that XSL hurts is in processor time. Drupal won't work on a page for more than 30 seconds, so I generally can't transform more than 200 documents at a time, which is a problem if I want to sort all 15,000 of them by zip code.
MySQL obviously wins here, if I stored zip codes in a zip code field, I could SELECT count(*) and GROUP BY and be done with it.
But I'm not ready to give up on the XML yet, however stubbornly. My sense was that you wanted to keep MARCXML around also, yes?
Now that I've written a "module" and have seen it's not so scary, it might make sense to create a separate search index, at least for the fields I want to use in views.