|
From: | Sebastian Hammer |
Subject: | Re: [Koha-zebra] A few Zebra Questions |
Date: | Thu, 29 Dec 2005 15:55:10 -0500 |
User-agent: | Mozilla Thunderbird 1.0.7 (Macintosh/20050923) |
Joshua Ferraro wrote:
Oooh.. serious dream project. I have fantasized about this for years. But no, there is nothing built into Zebra today.Hi guys, Chris and I are brainstorming today over a few cups of coffee and a giant dry-erase board and we've come up with a few Zebra questionsthat will help out as we plan our next moves for the migration. So here goes:Does Zebra allow any kind of database replication, master/slave or master/master relationships? (or alternatively, are there methods to communicate between two or more Zebra servers?)
One somewhat obvious way to approach this would be using OAI-PMH.. the LoC is presently contemplating awarding us a little money to support an OAI server function in Zebra. It wouldn't require much, really, primarily a mechanism to select records based on an update time stamp, and the ability to preserve and optionally recall deleted records. Anything else could be written in a simple Perl or PHP frontend..
With that in hand, we would have a pretty simple basis for replicating databases in a master/slave relationship. Another option would involve using Z39.50 (or SRW) Update to actively update remote databases when new stuff comes in. That could be done instantaneously, and could even be built into the update/commit cycle so you really enforced a high level of synchronization.. the OAI approach might be a little more robust, though.
I think you're asking if Zebra can maintain a redundant external copy of a database in MARC format -- or at least a transaction log of sorts.. at present, there is no such option, but it would be possible to add.When updating a database with general record IDs does (can) Zebra also create a MARC file for that record?
Is there any foreseeable way to get around the speed issues with updating that would make it feasible to store status data quickly?There are lots of ways to work around that I am sure.. different complexities, different challenges, but I don't think any unsurmountable problems. I have to be careful not to entirely drop my programmer's hat in favor of my marketing hat, but really, it is primarily a matter of time.For instance, Chris wondered if we could delay the actual indexing process, but get the data in there for when the record is actually retrieved (then index in batch say every minute or so)?
What is the issue here -- the ability to use circulation status as a filter in bibliographic searching, or what?
--Sebastian -- Sebastian Hammer, Index Data address@hidden www.indexdata.com Ph: (603) 209-6853
[Prev in Thread] | Current Thread | [Next in Thread] |