http://blog.meresco.org/2010/01/29/inbox-component/ What happened in the MERESCO community? Tue, 18 May 2010 22:04:18 +0000 hourly 1 http://wordpress.com/ http://blog.meresco.org/2010/01/29/inbox-component/#comment-12 How to scale up Meresco « MERESCO Fri, 02 Apr 2010 12:34:55 +0000 http://blog.meresco.com/?p=91#comment-12 [...] Approach B Extract the most demanding components from the server’s configuration and put these on separate machines. Reconnect them using the Inbox component. [...] [...] Approach B Extract the most demanding components from the server’s configuration and put these on separate machines. Reconnect them using the Inbox component. [...]

]]> http://blog.meresco.org/2010/01/29/inbox-component/#comment-4 Thomas Place Sat, 06 Feb 2010 22:06:49 +0000 http://blog.meresco.com/?p=91#comment-4 You don't mention that Meresco uses SRUUpdate for ingesting XML documents. This is also used by the Meresco Harvester that can send a metadata element of a OAI-PMH response as a SRUUpdate request to the Meresco server. This is a powerful mechanism also for non-OAI sources. Although we at Tilburg University have the inbox functionality for more than a year, our preferred way to connect non-OAI sources to the Meresco server is via SRUUpdate. Once you have written a SRUUpdate client you can adapt it for all kinds of (update) jobs. One application is selective deletes! For selective updates in the case of a OAI repository you can use the GetRecord request with such a SRUUpdate client. For enriching Meresco documents with extra information coming from external sources we also use SRUUpdate. What this shows is that Meresco is a flexible system that allows for different ways to do a job. You don’t mention that Meresco uses SRUUpdate for ingesting XML documents. This is also used by the Meresco Harvester that can send a metadata element of a OAI-PMH response as a SRUUpdate request to the Meresco server. This is a powerful mechanism also for non-OAI sources. Although we at Tilburg University have the inbox functionality for more than a year, our preferred way to connect non-OAI sources to the Meresco server is via SRUUpdate. Once you have written a SRUUpdate client you can adapt it for all kinds of (update) jobs. One application is selective deletes! For selective updates in the case of a OAI repository you can use the GetRecord request with such a SRUUpdate client.
For enriching Meresco documents with extra information coming from external sources we also use SRUUpdate.
What this shows is that Meresco is a flexible system that allows for different ways to do a job.

]]>