Unsurprisingly I do remember this, and we're implementing something
similar at the moment for OAI.
However, couldn't you just XSLT the information out of an appropriate
record metadata schema that included at least the oai header metadata?
After the discussion, I'm not averse to the schema in the param, but how
would you have the schema in the explain information in such a way as to
make it clear it was a metadata schema for use with the extension, not a
regular schema? And vice versa, that you couldn't request the metadata
in MarcXML, even tho it's a schema in the explain response?
On Mon, 7 May 2007, LeVan,Ralph wrote:
>> Mr. Ralph -- are you there? Do you have a position on this? --Ray
> I have exactly this situation now.
> If you'll remember, Rob, Jeff Young and I developed an SRW profile for
> supporting OAI on top of SRW. It required that the server support a
> couple of indexes and a schema for returning OAI Header information.
> To make the process more efficient, we developed a way to return the OAI
> header in the response with the actual record (usually MarcXML). We
> return the data in the extraRecordData element.
> We request the header with a valueless parameter x-99-OaiHeader or the
> empty extraRequestData element <OaiHeader/>.
> The general case should be a request for metadata with a schema as the
> value of the parm. The schema should be one of the schemas specified in
> the explain record for the database.