Save the Libraries – With Open Source
For some in the world of free software, libraries are things that you call, rather than visit. But the places where books are stored – especially those that make them freely available to the public – are important repositories of the world's knowledge, of relevance to all. So coders too should care about them alongside the other kind, and should be concerned that there is a threat to their ability to provide ready access to knowledge they have created themselves. The good news is that open source can save them.
The story begins even before RMS had his idea about the benefits of hackers sharing code, back in 1967, when the Online Computer Library Center (OCLC) was created:
OCLC was founded in 1967 by Fred Kilgour, a pioneering Ohio librarian, with a simple idea: Instead of having every library in the country separately catalog a book -- laboriously entering its title, author, and subjects in just the right format -- why not have one person enter the cataloging information, upload it to a central computer, and then let everyone else download a copy from there?
The kinship with free software and many collaborative content projects like Wikipedia is evident. But the OCLC's WorldCat has not followed the same development path as Stallman's GNU project:
Today [WorldCat] has around 50 million book records. But OCLC, the group that owns and operates it, has been a different story. It started small -- a little office in Ohio, a set of membership dues to share the cost of running the servers. But OCLC's control passed from librarians and academics to business people (its senior executive comes from consulting firm Deloitte & Touche). They realized they had a monopoly on their hands and as costs for running servers have gone down, their prices have gone up. They charge you once to get your records added to WorldCat and charge you again to get them back out and charge you a third time for a whole series of additional fees and services.
And these prices are high. A friend who runs a small public library with around 5000 cardholders was asked to pay $5400 to contribute his records and $700 to get records out, plus a whole series of "User Support" and "New Member Implementation" fees -- all far more than he could afford.
Clearly, the original kinship with GNU has long gone: now, users are expected to cough up not just to use WorldCat's records, but even to contribute. In other words, WorldCat has moved to the Microsoft model, where you have to pay for the program, and also for support in order to file bug reports to improve the program.
As the rest of the post quoted above explains, the situation looks like it is going to get even worse. In particular, it seems that it is going to get harder to export bibliographic data without constraints to other catalogues, including free alternatives such as Open Library.
The open source community has been here before, when the communally-created CDDB database was bought and the terms governing its use were modified, essentially making it hard to export data to other, free alternatives – just as is happening in the world of libraries today:
Things changed dramatically when the open CDDB.com server was bought by a company that wanted to make money from the contributions that users had made. The index file created by the Internet community could no longer be copied. Patents were obtained and granted. A large public outcry resulted, and led to the start of several projects to create an Open Source competitor for the commercial CDDB.com (now Gracenote).
In other words, the open source community simply routed around the damage by not submitting data to the closed CDDB, and by supporting instead free alternatives like Freedb and MusicBrainz, both of which are thriving.
Against this background, an obvious solution to the libraries' dependence on OCLC's central repository of bibliographic information is to start up an open equivalent along the lines of Freedb and MusicBrainz: basic hosting costs are now small, and altruists willing to run mirrors would doubtless start popping up given that the benefit to the community as a whole is so great. Users will rapidly switch their contributions to a truly free database that all can access, and this will soon surpass any legacy system, which will, in any case, find itself cut off from the community it has hitherto depended on (and taken for granted).
Unfettered access won't be the only way that users benefit. As has become evident in recent years, releasing large quantities of primary data for free allows all kinds of innovative secondary uses to be developed, some of which can be exploited commercially – but without needing to close off the primary materials, or charge for them. As a rich and diverse ecosystem arises, users will gain new tools and capabilities that simply were not possible with a locked-down database, and companies will gain a host of new business opportunities.
What's striking about the current discussions swirling around the OCLC saga is that they are being conducted in something of a vacuum, despite the fact that open source has a rich store of relevant experience that librarians could usefully refer to. The only problem is that little of it is to be found in books.
Glyn Moody writes about openness at opendotdotdot.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide