One of the challenging and rewarding aspects of open source software is building and sustaining the community that surrounds the software. It is challenging because people and institutions use open source software for a variety of reasons. For some, having the computer source code means that they are empowered to adapt the software to fit their needs. For others, contributing talent and budget to a communal effort – something arguably aligned with the general ethos of libraries – means that ultimately a better solution is created for their own users. Yet another group sees an open source solution as simply the best tool to solve a particular problem.
In preparation for the last webinar of the three-part series “Using RDA: Moving into the Metadata Future“, I’m reading again Karen Coyle‘s “Library Data in a Modern Context” — the first chapter of Understanding the Semantic Web: Bibliographic Data and Metadata. Right at the start she has a clear and useful definition of this thing we call “metadata.”
This week I sat in on the first of the three “Using RDA: Moving into the Metadata Future” webinars being hosted by ALA. This one was hosted by Karen Coyle with the title New Models of Metadata where she talked about library-specific efforts such asRDA and FRBR as well as the linked data effort in the wider world of information. There was a great deal of concern expressed in the chat window by participants about the future of cataloging, of cataloguers, and of MARC. The latter brought up memories of Roy Tennant‘s “MARC Must Die” declaration. My take away, though, isn’t that MARC is dead as much as MARC is a dead end.
One of the baffling elements I’ve found in discussions of the history of OCLC is that of its tax exempt status under Ohio law. The latest example of this comes from documents filed in the SkyRiver/Innovative-vs.-OCLC case that make disparaging remarks about how OCLC got its state tax-advantaged status. (The text of the remarks in those documents are included below.) I was curious about this a while back and so did some research on the topic. I had set it aside and forgotten about it until this latest lawsuit brought it up again. So, to set the record straight, here is at least one version — hopefully written from a neutral perspective — of what happened nearly three decades ago.
Within the span of a recent week we’ve had two views of the OCLC cooperative. In one we have a proposition that OCLC has gone astray from its core roots and in the other a celebration of what OCLC can do. One proposes a new mode of cooperation while the other extols the virtues of the existing cooperative. Both writers claim — independently — to “talk to librarians” and represent the prevailing mood of the profession. Can these two viewpoints be reconciled?
On September 9th, OCLC filed its first substantial response with the court to the antitrust lawsuit file by SkyRiver and Innovative Interfaces. And in a motion where OCLC requests a change of venue from the Northern District of California to the Southern District of Ohio — something seemingly mundane — they certainly pulled no punches:
This week I was at the Multiple Perspectives on Access, Inclusion, and Disability annual conference conference at the Ohio State University and was reminded again about the principles of Universal Design. The presentation was “Universal Design: Ensuring Access to All Learners” by Maria Morin from Project Enhance at the University of Texas — Pan American. Although she talked about Universal Design for Learning (encompassing assessments, instructional delivery and resource presentation), there was a point in her presentation that I snapped to Universal Design for Libraries.
Here were the two slides:
Universal Design for Learning is about Options!
Last month, the eXtensible Catalog (XC) project posted job openings for Java developers. These are short-term, grant-funded projects and, having been on the hiring side of that equation before myself, I know how difficult it is to get good people for a one- or two-year project. The XC posting is different, though, in one important way: it is possible to have XC buy out the time of a developer on staff for the time that the development is happening.
Jay Jordan’s remarks during the OCLC Update Breakfast and the discussion at the Developers Network table at that breakfast generated further fuel for my previous philosophical thoughts on “Who is a member of the OCLC Cooperative?” In the context of things like Developer Network API keys1 this question of who is a member of OCLC the cooperative and who is not meets the on-or-off, ones-and-zeros nature of computers. One can’t “kinda” have an API Key unless that capability is programmed into the software (or a human chooses to override the established rules for who has a key).