[CODE4LIB] OR09 Workshop / Tools for Repositories - Microsoft Research the Scholarly Information Ecosystem

2009-04-30 Thread Eric Lease Morgan
[Forwarded upon request --ELM] (apologies for cross-postings) Colleagues, Microsoft Research will be hosting a workshop at the Open Repositories '09 meeting in Atlanta, GA on from 1-6pm on Thursday, May 21st (https://or09.library.gatech.edu/workshops.php). A preliminary description below,

Re: [CODE4LIB] registering info: uris?

2009-04-30 Thread Ross Singer
So hey, I'm nobody wanted to see this thread revived, but I'm hoping you info uri folks can clear something up for me. So I'm trying to gather together a vocabulary of identifiers to unambiguously describe the format of the data you would be getting in a Jangle feed or an UnAPI response (or any

Re: [CODE4LIB] Recommend book scanner?

2009-04-30 Thread Erik Hetzner
At Wed, 29 Apr 2009 13:32:08 -0400, Christine Schwartz wrote: We are looking into buying a book scanner which we'll probably use for archival papers as well--probably something in the $1,000.00 range. Any advice? Most organizations, or at least the big ones, Internet Archive and Google,

Re: [CODE4LIB] Recommend book scanner?

2009-04-30 Thread Ethan Gruber
How good are the two-camera apparatuses for scanning things other than books? The thing about the Google and Kirtas scanners is that they are not particularly recommended for dealing with fragile books or otherwise special collections materials. The University of Virginia Library is still using

Re: [CODE4LIB] Recommend book scanner?

2009-04-30 Thread William Wueppelmann
Erik Hetzner wrote: At Wed, 29 Apr 2009 13:32:08 -0400, Christine Schwartz wrote: We are looking into buying a book scanner which we'll probably use for archival papers as well--probably something in the $1,000.00 range. Any advice? Most organizations, or at least the big ones, Internet

Re: [CODE4LIB] registering info: uris?

2009-04-30 Thread Ray Denenberg, Library of Congress
From: Ross Singer rossfsin...@gmail.com Except that OpenURL and SRU /already use different info URIs to describe the same things/. info:srw/schema/1/marcxml-v1.1 info:ofi/fmt:xml:xsd:MARC21 or info:srw/schema/1/onix-v2.0 info:ofi/fmt:xml:xsd:onix What is the rationale for this? None.

[CODE4LIB] One Data Format Identifier (and Registry) to Rule Them All

2009-04-30 Thread Ross Singer
Hello everybody. I apologize for the crossposting, but this is an area that could (potentially) affect every one of these groups. I realize that not everybody will be able to respond to all lists, but... First of all, some back story (Code4Lib subscribers can probably skip ahead): Jangle [1]

Re: [CODE4LIB] One Data Format Identifier (and Registry) to Rule Them All

2009-04-30 Thread Ray Denenberg, Library of Congress
Thanks, Ross. For SRU, this is an opportune time to reconcile these differences. Opportune, because we are approaching standardization of SRU/CQL within OASIS, and there will be a number of areas that need to change. Some observations. 1. the 'ofi' namespace of 'info' has the advantage that

Re: [CODE4LIB] One Data Format Identifier (and Registry) to Rule Them All

2009-04-30 Thread Peter Noerr
Some further observations. So far this threadling has mentioned only trying to unify two different sets of identifiers. However there are a much larger number of them out there (and even larger numbers of schemas and other

Re: [CODE4LIB] One Data Format Identifier (and Registry) to Rule Them All

2009-04-30 Thread Jonathan Rochkind
Crosswalk is exactly the wrong answer for this. Two very small overlapping communities of most library developers can surely agree on using the same identifiers, and then we make things easier for US. We don't need to solve the entire universe of problems. Solve the simple problem in front of

[CODE4LIB] job posting: interface programmer, University of Michigan

2009-04-30 Thread Morse, Jeremy
Please forward to anyone who may be interested in this position. This position is also listed in U-M jobs site ( http://www.umich.edu/~jobs/ ) under posting #30698. ### Scholarly Publishing Office University of Michigan University Library Interface Programmer The Scholarly Publishing Office