It actually looks to me like the OAI module provides both ends
of the service -- there's a Harvest.php that appears to be designed to pull in
external data and drop it into the index, and there's a Server.php that appears
to be designed to export data. I have no idea how far developed either of
these pieces is, but there's at least a seed there….
From: Till Kinstler
Sent: Tuesday, September 29, 2009 10:23 AM
Subject: Re: [VuFind-Tech] Extensible Catalog (XC) project - Metadata
Services Toolkit - release end October
On Tue, Sep 29, 2009 at 10:22 PM, Demian Katz <firstname.lastname@example.org>
Sounds like an interesting
tool. I should be starting on the record driver refactoring next week (if
not sooner); hopefully this will help with future OAI-PMH
implementations. I also notice there's already an OAI module under
web/services, though it is old and currently non-functional (the templates
never got moved into the theme folders, for one thing). Does anybody know
enough about the history of this module to know if it's this worth
I don't know anything about its history or if it does or ever did something
useful. But I remember that it implemented the data provider
("server") side of OAI, not the client part. So VuFind could act as a
OAI-PMH data provider. As far as I understand Eoghan, we need a OAI-PMH client
to use XC. But I haven't looked into that in detail.
The OAI-PMH protocol is quite simple (some HTTP requests, some XMLish output),
though it's kind of boring to implement the error handling fully and correctly
(at least on the server side).
If we only need to pull some data from a OAI-PMH data provider at display time
to show it (is that what you suggests, Eoghan?) implementation of the GetRecord
method and some parsing of the results should be sufficent. That's pretty
straightforward. Is XC providing a OAI-PMH data provider for authority data?
The bigger issues will be identifier and data related then (you need an
identifier for the matching authority record).
Good night from Seoul,