[OAI-implementers] Requesting a part of a record possible wit
Wed, 21 Jan 2004 14:40:37 -0500
I like this idea too. Specifically, I'm thinking I could use this
information in association with the ERRoL service. Using the SRW/SRU example
Hussein gave, I could place a button for it somewhere on the OAI Viewer page
for the NDLTD repository (http://errol.oclc.org/ndltd.oclc.org.html). In
fact, there could be a whole column of buttons for the various services
specified in the repository's Identify response.
I could also use this information to configure the ERRoL service. For
example, the look and feel of the OAI Viewer for individual repositories
could be customized by specifying a different XSL stylesheet in a
Another example is that I am writing a service to allow people to create and
edit XML records in arbitrary XML Schemas. I don't want to enable this for
all repositories, so individual repositories could add a description element
for it along with the email address of the administrator where record adds
and changes can be sent.
I was thinking of using custom description schemas to define these things
for the ERRoL service, but if there is a commonly accepted mechanism, all
> -----Original Message-----
> From: Michael Nelson [mailto:email@example.com]
> Sent: Tuesday, January 20, 2004 11:53 AM
> To: firstname.lastname@example.org
> Subject: Re: [OAI-implementers] Requesting a part of a
> record possible
> with OAI-OMH?
> this is a great idea and deserves its own thread...
> for example, I've been meaning to add SRW to
> http://ntrs.nasa.gov/ in my
> spare time. Assuming that ever happens, it sure would be
> handy to "point"
> to other protocol interfaces.
> now all we need to do is come up with a pithy name for the
> container. "otherProtocols" is kind of bland. "associates"?
> "colleagues"? "family"?
> On Tue, 20 Jan 2004, Hussein Suleman wrote:
> > by now you have probably stopped reading this message, but
> if not, i
> > have one last suggestion: how about an "other_protocol" description
> > format for OAI-PMH Identify responses? does anyone else
> think it will be
> > useful to know what other protocols can be used to
> interact with a data
> > collection? for example, OCLC's ETD collection could list:
> > <description>
> > <protocol:protocol xmlns:protocol="..." xmlns:dc="...">
> > <dc:title>SRW</dc:title>
> > <dc:identifier xsi:type="dcterms:URI">
> > </dc:identifier>
> > <dc:coverage xsi:type="protocol:version">1.0</dc:coverage>
> > <protocol:baseURL>
> > </protocol:baseURL>
> > </protocol:protocol>
> > </description>
> > could this possibly be useful for discovery/advertising of
> services? it
> > is somewhat halfway between "friends" and WSDL and might
> already be done
> > - anyone have pointers? or thoughts in general?
> > ttfn,
> > ----hussein
> > hussein suleman ~ email@example.com ~
Michael L. Nelson firstname.lastname@example.org http://www.cs.odu.edu/~mln/
Dept of Computer Science, Old Dominion University, Norfolk VA 23529
+1 757 683 6393 +1 757 683 4900 (f)
OAI-implementers mailing list
List information, archives, preferences and to unsubscribe: