Koha is the first open-source Integrated Library System (ILS). In use worldwide, its development is steered by a growing community of libraries collaborating to achieve their technology goals. Koha's impressive feature set continues to evolve and expand to meet the needs of its user base.
Why ‡biblios?
A rich internet application
Though browser-based, ‡biblios has a very rich user interface and takes advantage of JavaScript toolkits like YUI, ExtJS, Google Gears for local storage of bibliographic records.
Built-in metasearch
Much of cataloging consists of copy-cataloging and so ‡biblios ships with built-in metasearch capability using a web services layer built on the Pazpar2 federated search library. Users can set up and perform cross-database searches on any Z39.50 targets.
Built around library standards
The ‡biblios record editor currently supports MARC21/MARCXML records and utilizes a plugin architecture to easily allow expansion to other formats such as MODS, Dublin Core, etc.
Library Standards Compliant
Built in support for MARC21, MARCXML, Z39.50
Free and Open Source
‡biblios is available under the terms of the GPL software license, which ensures free and open access to use, modification and redistribution.
Google Librarian Central - Article 12/2006 - 3
Download a PDF of this article
When I interned at Google last summer after getting my MSI degree, I worked on projects for the Book Search and Google Scholar teams. I didn’t know it at the time, but in completing my research over the course of the summer, I would become the resident expert on how universities were approaching Google Scholar as a research tool and how they were implementing Scholar on their library websites. Now working at an academic library, I seized a recent opportunity to sit down with Anurag Acharya, Google Scholar’s founding engineer, to delve a little deeper into how Scholar features are developed and prioritized, what Scholar’s scope and aims are, and where the product is headed.
-Tracey Hughes, GIS Coordinator, Social Sciences & Humanities Library, University of California San Diego
BASIC LIBRARY LIST
OUR GOALS:
The Basic Library List contains a list of books in the mathematical sciences recommended for college, high school, and public libraries. It is designed to provide students with introductory sources that might not be part of their curriculum; to provide reading material that is collateral to regular courses; to provide faculty with reference material that is relevant to their teaching; and to provide appropriate references for students in disciplines that use the mathematical sciences.
Originally issued in print form in 1965, 1976, and 1992, the Basic Library List is now being revised and updated by the Committee on the Undergraduate Program in Mathematics (CUPM). The version currently on-line is the 1992 edition, supplemented by full text search capabilities. Updates will be made regularly in the future.
"Under the terms of the agreement, articles
by UC-affiliated authors accepted for
publication in a Springer journal beginning in 2009 will be published
using Springer Open Choice with full and immediate open access. There
will be no separate per-article charges, since costs have been factored
into the overall license
This table contains DML bibliographic items from various repositories. # # Coding is as follows: # ASCII based (ISO Latin 8859-1 extended) # Every line starting with a '#' is a comment # # the list of items from any repository is preceded by lines like the following: # # nick: <repository nickname, usually short or acronym> # name: <repository name> # addr: <repository web address> # comm: <any comment concerning the actual repository # # After that, the bibliographic items of that repository are described by: # # item_title: <name or title of item> # item_years: <year(s) published or covered> # item_url: <web address of content page> # item_type: <journal|multivol|book> # (possibly other colon separated pairs, first component should begin with "item_") # item_end: <optionally some comment like a counting number...> # This last line ends any item entry. # # Some items do contain commented metadata for later use. # # comment lines like #--------------------------- or similar # could separate entries from different repositories
Libraries do something they call "name authority control". For most people in IT, this would be called "assigning unique identifiers to names." Identifying authors is considered one of the essential aspects of library cataloging, and it isn't done in any other bibliographic environment, as far as I know.
A Creative Commons license is inappropriate for cataloging records, precisely because they are unlikely to be copyrightable. The whole legal premise of Creative Commons (and open source) licenses is that someone owns the copyright, and thus they have the right to license you to use it, and if you want a license, these are the terms. If you don’t own a copyright in the first place, there’s no way to license it under Creative Commons.