[OAI-implementers] OAI identifier resolver

[Xiaoming Liu]

On Mon, 13 Oct 2003, Young,Jeff wrote:

> 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
> http://purl.org/oai.

Two comments:

-- If URL takes the format
http://purl.org/oai/<metadata-format>/<oai-identifier>, it will make it
much easier to parse the special format identifier like hdl:1721.1/659,
the program will know whole part after "metadata-format" is
oai-identifier.

-- I wonder if it's useful to assign repository ID by hashing
the baseURL, this will make it possible to develop applications without
prior agreement on unique ID of repositories.

For example, the baseURL of DSpace (http://hpds1.mit.edu/oai/) can be
hashed to 2D0DA5560CAFBA3912A522345ECA4271 by MD5 algorithm. If both POI
and UIUC resolvers use this algorithm, the same repository ID can be
generated without prior agreement.

xiaoming


>
> 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
> entry
>
> Other metadataFormats are accessible by appending the metadataPrefix as an
> extension:
>
> http://purl.org/oai/oai:VTETD:etd-06152001-152749.oai_marc
>
> 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):
>
> http://purl.org/oai/hpds1.mit.edu/hdl:1721.1/659.oai_dc
>
> 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
> (http://alcme.oclc.org/oai/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc
> ), but the rest will be available when Tom's registry is harvestable.
>
> Comments and suggestions are welcome.
>
> Jeff
>
> ---
> 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
> www.oclc.org
>
> Voice:	614-764-4342
> Voice:	800-848-5878, ext. 4342
> Fax:	614-718-7477
> Email:	jyoung@oclc.org
>
>
> _______________________________________________
> OAI-implementers mailing list
> List information, archives, preferences and to unsubscribe:
> http://oaisrv.nsdl.cornell.edu/mailman/listinfo/oai-implementers
>
>