Here is the kicker: if the library charges a fee for printing (and how many libraries can allow users to print for free?), then they are required by Section 4.8(a)(ii) of the Agreement to charge users for the printing. Google will collect the money on behalf of libraries and pass it on to the Registry. Google has agreed to pay the cost of the printing for the first five years or $3 million, whichever comes first.

New York Philharmonic Archives seeks a Digital Archivist Project Manager to supervise the entire process of digitizing 1.3 million pages of content and the implementation of the institution's Alfresco digital asset management system making these documents available to researchers world-wide through the internet. This is a three-year grant-funded project but there is the possibility that this assignment would extend beyond that period. This position is based in the Archives and interfaces heavily with the Information Technology department.

An alpha prototype of JHOVE2 is now available. JHOVE2 is a tool for the characterization (i.e., identification, validation, feature extraction, and assessment) of digital objects that is used for digital library and digital preservation purposes.

Reporting to the Programmer Analyst III in Library Access Integration Services, the Programmer Analyst is responsible for the design, development, testing, installation, and maintenance of Library web and database applications and analyzes the technical needs of staff, faculty and readers, and develops proposals to acquire or develop the tools to answer those needs.

NSLC functions as the key library nationally for collecting information resources and providing information services in natural sciences, inter-disciplinary fields, and high tech fields, for the researchers and students of CAS and for the researchers around the country. It also conducts services such as information analysis, digital library system development, scientific publication (with its 14 journals), and promotion of sciences. It also operates the Archives of CAS.

NSLC has a staff over 470, building areas more than 80,000m2 [square meters], and a collection about 11.5 million items

The U.S. Department of Justice has submitted a brief to the U.S. District Court for the District of Minnesota supporting the $1.92 million statutory damages award that Jammie Thomas-Rasset must pay for illegally sharing 24 songs ($80,000 per song).

MOAI has some interesting features not found in most OAI servers. Besides serving OAI, it can also harvest OAI. This makes it possible for MOAI to work as a pipe, where the OAI data can be reconfigured, cached, and enriched while it passes through the MOAI processing.

More specifically MOAI has the ability to:

Harvest data from different kinds of sources

Serve many OAI feeds from one MOAI server, each with their own configuration

Turn metadata values into OAI sets on the fly, creating new collections

Use OAI sets to filter records shown in a feed, configurable for each feed

Work easily with relational data (e.g. if an author changes, the publication should also change)

Simple and robust authentication through integration with the Apache webserver

Serve assets via Apache while still using configurable authentication rules

Members of the University of California's Academic Council and the chair of the Academic Senate’s Committee on Libraries and Scholarly Communication have submitted a letter about the Google Book Search Copyright Class Action Settlement to the U.S. District Court for the Southern District of New York.

Here's an excerpt:

We have three main concerns about the proposed settlement agreement. First, to maximize access to knowledge, prices should be reasonable. Unfortunately, the proposed settlement agreement contains inadequate checks and balances to prevent price gouging and unduly restrictive terms for purchasers of books and institutional subscribers. Second, the agreement does not contemplate or make provision for open access choices that have in recent years become common among academic authorial communities, especially with regard to out of print books. The settlement agreement only contemplates that authors would monetize their books and related metadata through the Book Rights Registry (BRR). This is especially worrisome as to the millions of out of print, and likely orphan, books. Third, the agreement contemplates some monitoring of user queries and uses of books in the Book Search corpus that negatively impinge on significant privacy interests of authors and readers and undermine fundamental academic freedom principles.

Thanks to everyone who sent me messages regarding the possibility of starting an electronic journal. There was a very favorable response to this idea, and I am willing to give it a try.

The Public-Access Computer Systems Review will contain short articles (1 to 7 single-spaced pages), columns, and reviews. PACS Review will cover all computer systems that libraries make available to their patrons, including CAI and ICAI programs, CD-ROM databases, expert systems, hypermedia systems, information delivery systems, local databases, online catalogs, and remote end-user search systems. All types of short communications dealing with these subjects are welcome. Articles that present innovative projects in libraries, even those at an early stage of their development, are especially welcome. Proposals for regular (or irregular) columns will be considered on an ongoing basis. There will be a section for reviews of books, journal articles, reports, and software. As a style guide, use Kate L. Turabian's A Manual for Writers (5th edition). If you are in doubt about whether your topic falls in the purview of PACS Review, consult my article: "Public-Access Computer Systems: The Next Generation of Library Automation Systems." Information Technology and Libraries 8 (June 1989): 178-185.

The initial editorial staff of the PACS Review will be as follows:

Editor: Charles W. Bailey, Jr., University of Houston

Editoral Board: Nancy Evans, Carnegie Mellon University
David R. McDonald, University of Michigan
Mike Ridley, McMaster University
R. Bruce Miller, University of California, San Diego

The PACS Review will come out on a regular schedule. I will determine the schedule based on the interest you show in submitting articles. If desired, authors can retain copyright to their works by notifying the editor. The logistics of distribution of the Review will be worked out at the release of the first issue. Either individual articles will be sent as PACS-L messages [PACS-L was a LISTSERV mailing list] or a table of contents will be sent and users will retrieve articles from the file server (at this point we do not have full documentation for the file server aspect of PACS-L). The PACS Review will have a volume and issue enumeration. It will be paginated.

I hope PACS Review will be timely, lively, and thought provoking. I hope that it will complement the PACS-L conference, potentially resulting in a unique interaction between formal and informal electronic communications. I welcome your contributions to this experimental electronic journal. Please send all articles to me at LIB3@UHUPVM1. Your contributions will determine whether this journal gets off the ground or not. Let's see if electronic publishing of library journals has a future!

The first issue of the PACS Review was published in 1990 and the last in 1998, for a total of 42 issues.

Cloud computing is the delivery of scalable IT resources over the Internet, as opposed to hosting and operating those resources locally, such as on a college or university network. Those resources can include applications and services, as well as the infrastructure on which they operate. By deploying IT infrastructure and services over the network, an organization can purchase these resources on an as-needed basis and avoid the capital costs of software and hardware. With cloud computing, IT capacity can be adjusted quickly and easily to accommodate changes in demand. Cloud computing also allows IT providers to make IT costs transparent and thus match consumption of IT services to those who pay for such services. Operating in a cloud environment requires IT leaders and staff to develop different skills, such as managing contracts, overseeing integration between in-house and outsourced services, and mastering a different model of IT budgets.