[OAI-implementers] FW: OAI identifier resolver
Tue, 14 Oct 2003 09:10:05 -0400
Apologies for duplication. I sent the message below to this list yesterday
morning, but it looks like it never got delivered.
I've already received several suggestions for changes, but I'll wait until
this group has reviewed the current model before making changes.
> -----Original Message-----
> From: Young,Jeff
> Sent: Monday, October 13, 2003 10:02 AM
> To: OAI-implementers (E-mail)
> Subject: OAI identifier resolver
> As a result of discussion following Tom Habing's announcement of an
> Experimental OAI Registry at UIUC, I put together an alternative OAI
> identifier resolver. Details can be found at the service's web site at
> Here is the basic pattern for oai-identifiers:
> "http://purl.org/oai/" + <oai-identifier>
> For example (from the Virginia Tech ETD Repository):
> http://purl.org/oai/oai:VTETD:etd-06152001-152749 - default to the oai_dc
> Other metadataFormats are accessible by appending the metadataPrefix as an
> For repositories that don't use the oai-identifier scheme, the pattern is:
> "http://purl.org/oai/" + <repositoryIdentifier> + "/" + <identifier>
> For example (from DSpace at MIT):
> Note that I had to add an explicit metadataPrefix extension in this case
> so it didn't interpret the metadataPrefix extension as "1/659" due the
> period in the identifier.
> I also plan to add a ".POI" extension that will return the web resource
> from the first dc:identifier in the oai_dc record, but for some reason
> it's not working on the production server yet.
> There are only three repositories supported by this service
> dc), but the rest will be available when Tom's registry is harvestable.
> Comments and suggestions are welcome.
> Jeffrey A. Young
> Consulting Software Engineer
> Office of Research, Mail Code 710
> OCLC Online Computer Library Center, Inc.
> 6565 Frantz Road
> Dublin, OH 43017-3395
> Voice: 614-764-4342
> Voice: 800-848-5878, ext. 4342
> Fax: 614-718-7477
> Email: email@example.com