From: Brian G. <bdg...@pi...> - 2006-11-29 18:45:21
|
When harvesting sites I notice that you seem to not store the Full Set information, particularly that they are not stored in a separate database table. Since I've been requested to list the setName instead of just setSpec can you suggest where in your harvesting code I could put code so that I could populate a table that contained simply the dataprovider id, setSpec, setName so that we could easily identify the sets available per archive? I've seen in the code where you harvest the sets (Partitions) but for a different reason. I'd like to take that a step further and store the set information if at all possible. Since I'm not very familiar with your harvesting code instead of writing my own routines separate to your code do you have any code in the project that would allow easy access to the setName and setSpec already so that I don't have to reinvent the wheel? I would of course contribute any changes I make back to you so that others can use this if wanted. Any hints would be appreciated. Thanks, Brian Gregg. -- +--------------------------------+------------------------------+ | Brian D. Gregg | | | Systems Analyst | | | University Library System | | | University of Pittsburgh | e-mail: bd...@pi... | | 7500 Thomas Blvd. | voice: 412-244-7507 | | Pittsburgh, PA 15208 | fax: 412-244-7515 | +--------------------------------+------------------------------+ | Member: | | ASNP - Association of Storage Networking Professionals | +---------------------------------------------------------------+ |