The end-of-year holidays are behind us and (in the northern parts of the northern hemisphere) the cold days of winter in front of us. What better time to bag it all and head to the warm(er) temperatures of San Diego, California for the . I mean — come’on — do you really want to dive into all of that work that piled up over the past week or so? (You say that even more work will pile up if you attend the meeting? Bah, humbug!) If you are going, I wholeheartedly endorse the new ALA Connect-based meeting planner. It is at times frustratingly slow, but chock full of ways to slice-and-dice meeting events that were not possible in the earlier version. (I’m going to put in a suggested enhancement that the iCal file export includes URLs to the meeting listing online; that would be immensely helpful.)
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.
The year is coming to a close, so that must mean that the midwinter meeting of the American Library Association is right around the corner. Yep, there it is — just two and a half weeks away in Boston. A conference in Boston in January — the rates have got to be cheap. 1 Given the fast approaching meeting, it is definitely time to strategize about how to tap into the pulse of library-land. Here is my plan so far. If you would like to get together in the spaces between meetings, or at the meetings themselves, let me know!
Ah, it is the beginning of September when thoughts turn to going back to school, the days turn a little colder (in the northern hemisphere) and the smell of lawsuit briefs is in the air. Well, okay — the latter might not be what you expect, but this is a special September, after all. Postponed from May, the deadline for filing comments in the Google Book Search settlement is coming up. And everyone is weighing in (“again” for some) on the details of the settlement. A couple of highlights.
Today was to be the deadline for objecting to, opting out of, and/or filing briefs with the court on the Google Book Search Settlement. That was the plan, at least, when the preliminary approval statement from the court was issued last year. That deadline changed, and that is part of a recent flurry of activity surrounding the proposed Settlement. This post provides a summary of recent news and an index of documents that you might want to read for more information.
The American Library Association (through the Association’s Washington Office and the Association of College and Research Libraries Division) and the Association of Research Libraries filed a brief [PDF] with the court in support of the Google Book Search Settlement while asking the judge to “exercise vigorous oversight” over details the settlement. In the 22-page amicus1 brief, the library associations say they do not oppose the settlement, but they do request that the courts provide strict oversight of the activities of Google and the Book Rights Registry. From page 2 of the brief:
The Settlement, therefore, will likely have a significant and lasting impact on libraries and the public, including authors and publishers. But in the absence of competition for the services enabled by the Settlement, this impact may not be entirely positive. The Settlement could compromise fundamental library values such as equity of access to information, patron privacy, and intellectual freedom. In order to mitigate the possible negative effects the Settlement may have on libraries and the public at large, the Library Associations request that this Court vigorously exercise its jurisdiction over the interpretation and implementation of the Settlement.
The brief then describes “concerns with the Settlement, and how the Court’s oversight can ameliorate those concerns.”
Panelists will share a variety of perspectives on community norms, policies, and best practices for accessing, using, and sharing the data that supports the discovery and delivery of library collections. What can libraries and the organizations that serve them learn from the open data movement and sites like Wikipedia? What principles and practices for shared data creation and maintenance will most help and strengthen libraries in the future? Panelists will also be addressing the changes in the OCLC Record Use Policy, particularly in light of the recent announcement from OCLC on the establishment of the Review Board of Shared Data Creation and Stewardship.
The panel is called the ALCTS Forum: Creating and Sustaining Communities Around Shared Library Data, and it will be on January 26th from 8:00am to 10:00am at the Colorado Convention Center, Korbel Ballroom 3C. Yours truly has been asked to speak on shared catalog data from the perspective of a library membership organization (OhioLINK) that provides consortial access to a large union catalog, licensed content, dissertations, and digital media. Also on the panel are:
First, kudos to the vendor that runs the ALA Meeting Planner website. They listened to suggestions and now include a way to download your event planner information to your desktop/handheld device using the iCalendar standard. It is available from the “Downloads and Printing” page of your meeting planner homepage. (You’ll need to sign in using the e-mail address listed on your ALA Annual Registration form plus the password “ala”.) Jump down to the end and select the “iCAL” button next to “Personal Itinerary” to download the iCalendar file.
Here is a map of official conference hotels and a link to download the KML file into Google Earth.
I’m somewhat disappointed by the display of the KML file through the Google Maps API. The KML file contains <address> tags, which in the Google Earth desktop application appears to enable the “Directions From” and “Directions To” options. It is entirely possible that I’m missing something in the KML file — it was created by exporting a folder of placemarks from the Google Earth application. The raw KML file, suitable for importing into Google Earth, can be downloaded from the link under the map.