SFX uses a proprietary mechanism to trigger fetch that is not part
of the OpenURL standard. The usefulness of this mechanism, however,
motivated the very rich fetch functionality in the 1.0 version of the
standard- if you care at all about interoperability you should avoid
the SFX trigger mechanism.
COinS recommends not to use ContextObjects with fetch (by reference
metadata) because it is thought that deverse agents will not be able
to deal with them; however, link server systems with full Z39.88
implementations should have no problem with them.
On Sep 28, 2007, at 11:59 PM, Tom Keays wrote:
> I'm certainly no expert, but my understanding is that you have to
> embed the extra authors into a call (a "fetch" in the SFX lingo) using
> a private identifier at the end of the OpenURL string. It's more
> complicated than that, of course, since there has to an sid included
> in addition to the pid and, at least in the SFX-biased documentation,
> this so-called "fetch" operation is intended to be done using z39.50
> or html-based (REST?) calls to a dataserver determined by the source.
> Pretty messy, huh?
> The upshot is that multiple authors aren't directly supported in COinS
> because a COinS url is by design generic and therefore can't know
> about how to deal with the specific sid and pid requirements of a
> However, I would think Umlaut ought to be able to handle it since it
> has SFX at its core.
> On 9/28/07, Jonathan Rochkind <[log in to unmask]> wrote:
>> Can you tell me how to legally include more than one author name
>> in an OpenURL context object? I've been a bit confused about this
>> myself, and happen to be dealing with it presently too.