You are hereby invited to RepoCamp in Washington DC on July 25th.
RepoCamp is a one-day free and open event where folks who are
interested in managing and creating digital repository software and
their contents can gather and share ideas, innovations, trials
On Tue, Jun 24, 2008 at 10:48 AM, Ross Singer [EMAIL PROTECTED] wrote:
Theoretically you should be able to also pass the argument
record_type=dc or record_type=marc to give you dublin core or marc21,
but there seems to be a bug there. I'll fix that today.
Bah, this actually did work, I just
[ this discussion may be a bit too detailed for the general readership of
code4lib; readers not interested in the upcoming WC search API may wish to
Atom/RSS are simply the container formats used to return multiple items of
some kind --- I'm curious about what those items contain.
I'm one of the developers working on the WorldCat API. My take is that
the API is evolving and adapting as we learn more about how it's
expected to be used. We haven't precluded the addition of more record
metadata to OpenSearch responses; we opted not to implement it until we
In general, is there a reason to have different metadata formats from
SRU vs OpenSearch? Is there a way to just have the same metadata formats
available for each? Or are the demands of each too different to just use
the same underlying infrastructure, such that it really does take more
I too find this decision intriguing, and I'm wondering about its wider
implications on the use of RSS/Atom as a container format inside and
outside the context of OpenSearch as it relates to library systems.
I note that an OpenSearch description does not allow you to specify
type of the items
Actually, regarding this very point...
One of the outcomes of Jangle is that I'd like to create a registry
(like, say, a SKOS vocabulary) that defines an identifier for an
agreed upon record format. You point out that conneg doesn't work for
Atom or RSS payloads, but it wouldn't work, anyway.
Ed Summers wrote:
|As for Karen's question about the Internet Archive: it totally makes
|sense to host the data up there. But, I had to sign a scary license
|agreement from the UIUC Archives, which *almost* stopped me from even
|releasing http://catalog.sanfordberman.org ... Madeline can say for
On Tue, Jun 24, 2008 at 4:31 PM, Hahn, Harvey [EMAIL PROTECTED] wrote:
Same experience here. I responded directly to Karen:
See http://catalog.sanfordberman.org/ -- it refers to licensing from
the Univ of Illinois Archives. When the data first became available a
number of years ago, I
I'm not sure this addressing the criteria of the licensing. How would
you stop commercial purposes?
Say I work for a UK-based vendor that starts with a T (as hard as
that may seem) and I devise a script (or, even more crazily, have root
access to the server to the server that the Berman catalog
Security measures can be set in place to prevent
the scenario you describe.
Tagging systems (or pop culture cataloging) such as those
used by Amazon.com were consciously or unconsciously
inspired by Berman's work, but although they are dynamic
and current, they are simplisitic and
Wow, I'm coming into this thread late ...
To answer Godmar up-thread, Evergreen's OpenSearch service returns
data in more than 15 formats, including MARCXML and MODS. It was
actually the first ILS to do so (with the exception of Ross's Voyager
add-on), and also the first ILS to have an unAPI
Mail list logo