True, but sad.
Sent from Eric Hellman's iPhone
1-862-596-0116
On Dec 8, 2008, at 2:20 PM, Karen Coyle [EMAIL PROTECTED] wrote:
Eric Hellman wrote:
Yep. There's no URI for LCC. You could put LCC in the subject field
of a
dublin core profile metadata format ContextObject. But it's not
Even if there was a URI for LCC, I wouldn't put it in rft_id unless an
individual LCC uniquely identifies a particular manifestation--I don't
_think_ it does, I think two books can share the same LCC? But I guess
not when you include all the trailing 'cutter'-type numbers?
At any rate, there
The Google Book Search Bibliography, Version 3 is now
available from Digital Scholarship.
http://www.digital-scholarship.org/gbsb/gbsb.htm
This bibliography presents selected English-language
articles and other works that are useful in understanding
Google Book Search. It primarily focuses on
I'm looking at Amazon's Mechanical Turk, https://www.mturk.com/mturk/welcome
to automate checking the page order of 11,000 scanned books (some were
scanned backwards by a long out-of-business vendor).
Does anyone on the list have experience using Mechanical Turk? This is a
time sensitive project
I used MTurk for a data gathering project recently. Turnaround time is
great: within a few hours. You can set params to only accept people
whose rejection rate is 5% or less or what not (95% acceptance rate is
the default) to weed out the riffraff. Pretty cost effective.
My instructions were
On 9 December 2008, Jonathan Rochkind wrote:
... I think two books can share the same LCC? But I guess not when you
include all the trailing 'cutter'-type numbers?
Not in the same library, but there's nothing to stop two different
libraries from having the same call number for two different
