Roy, do you have an answer in mind?
To me my project it's the content that is open, which is why it's worth the
hurdles. Once you 'crack the nut' you can grab metadata, scans, and
derivatives and ingest, parse, recombine, remix...as we've done for BHL.
Access to OCA content may not be
I concur. The content is open; and the OCA's use of MARC is open... I
think they're waiting for the community to chip in the means and
mechanisms to support whatever open APIs or protocols are deemed useful.
We built a free Z39.50/SRU service based on a crawl through their text
collection,
But why are there hurdles?
Karen G. Schneider
On Wed, 27 Feb 2008 07:29:57 -0600, Chris Freeland
[EMAIL PROTECTED] said:
Roy, do you have an answer in mind?
To me my project it's the content that is open, which is why it's worth
the hurdles. Once you 'crack the nut' you can grab metadata,
I see it as open it the way that google books is not.
But, a huge part of being open is the provision of *access* and so having
easy, documented APIs (in the way that google often does) would make this
a whole lot easier to leverage.
Still, it's a good thing and I'm pleased to have the
On Feb 27, 2008, at 10:58 AM, Bill Erickson wrote:
Can someone point me to the demo links from the XForms fro Metadata
Creation presentation?
Michael Park's work is documented at:
http://dl.lib.brown.edu/its/software/metadata/
Winona has a blog entry with links at:
Hi Bill,
If you have any questions just hunt me down. I'd be more than happy to
answer any questions.
-Mike
-Original Message-
From: Code for Libraries [mailto:[EMAIL PROTECTED] On Behalf Of
Bill Erickson
Sent: Wednesday, February 27, 2008 7:58 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject:
