Category: Futures

  • Babies, Bathwater, and Old Broads

    A few years ago, I wrote an article for a collection of writings in honor of Tom Turner, a talented metadata librarian at Cornell who sadly died too young. That article, “Looking back—looking forward: reflections of a transitional librarian” (Metadata and Digital Collections: Festschrift in honor of Tom Turner), although it meanders around a bit (she said after reading it over for the first time in a couple of years) is a pretty good view of where my head has been these past couple of decades. A lot has happened, and I’ve been lucky enough to have been in the thick of a lot of it.

    One question that occasionally comes up is about what was in that kool-aid I drank that caused me to jump ship from many of the traditional library ways of thinking to something quite different. There’s not a simple answer to that. It was a combination of things, certainly, but perhaps best expressed towards the end of the article:

    “In October of 2004, I attended a panel presentation where three experts were asked to inform library practitioners by providing “evaluation” information about a large Dublin Core-based metadata repository. It was, in a small way, yet another version of the blind men and the elephant. The first presenter provided large numbers of tables giving simple numeric tallies of elements used in the repository, with no more analysis than a relational database might reveal in ten minutes. The second provided results of a research project where users were carefully observed and questioned about what information they used when making decisions about what they were given in search results—i.e. useful data, and a good start on determining the usefulness of metadata, but with no attention paid to the metadata that was used behind the scenes, well before any user display was generated. The third presenter, a young computer scientist, relied almost entirely on tools developed for textual indexing, and, concluding that the diversity of the metadata was a problem, suggested that the leaders of the project should insist that all data providers follow stricter standards.

    These presentations seemed sadly reflective of most attempts to approach the problems of creating and sharing metadata in the world beyond MARC. Traditional libraries built a strong culture of metadata sharing and an enormous shared investment in training and documentation around the MARC standard. The MARC development process codified the body of knowledge and practice that supported this culture of sharing and collaboration, building, in the process, a community of metadata experts who took their expertise into a number of specialized domains. We clearly are now at a critical juncture. Moving forward in both realms, traditional and “new” metadata requires that we understand clearly where we have been and what has been the basis for our past success. To do that we need much better research and evaluation of our legacy and current models, a clearer articulation of short term and long term goals, and a strategy for attaining those goals that is openly endorsed and supported by stakeholders in the library community.”

    Looking back, I’m not sure I can exactly pinpoint the moment when we stopped thinking clearly about the road ahead, but until very recently, it sure looked like we had. It was probably somewhere around the time when it seemed like RDA would never be finished in our lifetimes, and that even if finished, would be too much like AACR2 to even consider implementing. Somewhere around that time, CC:DA drafted a ‘no-confidence’ memo to the JSC, and I showed Don Chatham (ALA Publishing) a late draft of it while he was at the DC-2006 conference in Mexico. At that meeting, a few of us suggested to Don that it might be a good idea to have the JSC get together with DCMI and see what could be done, which ended up being the ‘London Meeting’ of five years ago that changed the conversation significantly. This spring a five year anniversary celebration was held in London, where a big part of the discussion was about just how big that impact was, in terms of where the library community is today. As usual, nothing like a good crisis to get things moving.

    It will be no surprise to readers of this blog, but I spend a fair bit of time thinking and talking about what comes next, and some of the focus of that question, particularly lately, has to do with MARC. A big part of the problem of answering that “what’s next?” question is that we tend to use ‘MARC’ to refer not just to the specification but as a stand-in for traditional practices and library standards as a whole, and this muddies the conversation considerably. What too often happens is that the ‘good stuff’ of MARC, the semantics that represent years of debate about use cases and descriptive issues, doesn’t get separately, or properly, discussed. Those semantics ought really to be seen as a distillation of all those things we know about bibliographic description, tested by time and generations of catalogers, and very much worth retaining. How we express those semantics needs to be updated, for sure (many are already expressed in the RDA vocabularies), but differentiating between baby and bathwater is clearly a necessary part of moving ahead.

    One of the things about the library community that few outsiders understand is the extent to which “the library community” has developed a culture of collaboration–to the extent I’ve never seen anywhere else. Librarians collectively build and contribute bibliographic and name authority records, subject and classification proposals, participate (passionately) in endless debates about interpretation of rules and policies, and most remarkably–write this stuff up and share it extensively, asking for comments (and most often getting them). Participating in other communities after having been part of the one built by librarians is very often a frustrating thing–my expectations of participation are clearly too high.

    A great example of how this works is NACO (Name Authority Cooperative Project), for those who participate in building and maintaining good authority records. In my days as Authorities Librarian at Cornell, I helped increase Cornell’s participation in the program by a significant amount, an accomplishment of which I’m still quite proud. Recently I noted a new post to the RDA-L list about some PCC (Program on Cooperative Cataloging) committee work around authority records:

    “The PCC Acceptable Headings Implementation Task Group (PCCAHITG) has successfully tested the programming code for Phase 1 in preparation for the LC/PCC Phased Implementation of RDA as described in the document entitled “The phased conversion of the LC/NACO Authority File to RDA” found at the Task Group’s page …

    The activities of this group display some of the important characteristics of successful community activity: the goals are clearly stated, and timelines spelled out; assumptions are tested and results analysed; conclusions and recommendations are written, explained and exposed for comment. This particular activity is noteworthy because it is a collaboration between the Library of Congress and a group of PCC member institutions, and is Phase 1 of a set of planned activities designed to move cooperatively built and maintained authority data into compliance with RDA.

    As for the old broads? I was recently reminded of this wonderful quote from Bette Davis: “If you want a thing well done, get a couple of old broads to do it.” So true, so true …

  • If We Were Asked

    If we were asked (as we sometimes are) what we’d like to see develop as a result of the BibFrame effort, the emphasis in our answer would have both technical and social aspects.

    First, given the technologies developing in several different places and considering what we can do now to bring Linked Open Data into our somewhat closed world, some concrete suggestions: We have the ability to share metadata expressed not just in a single common ‘vocabulary’, but to share it using many different vocabularies, expressed and distributed using RDF, OWL/RDFS, RDFa, Microdata, and other tools; we have methods of specifying the use of these ‘semantic’ building blocks (DC Application Profiles and emerging provenance specifications from W3C and DCMI) that allow machines to use, process and distribute data in ways that do not require a central enabling node; and finally, we have technologies and strategies in place to map between existing and prospective metadata schemas that flatten the fences between communities quite thoroughly.

    This is the post-MARC world of library-related metadata, where the format native to our metadata is no longer its most important characteristic; there’s no lossy crosswalking requirement to transform data to serve different needs; and there are fewer (eventually no) barriers to sharing. The tremendous value that MARC represents–the semantics built over many decades in response to an enormous corpus of use cases (all of which are fully documented on the MARBI site)–continues to be vitally important as we move into a different arena. But the mid-20th century requirements that dictated the MARC syntax, and the constricting consensus model that has been required to maintain it, no longer apply to the current and future requirements of the global library community.

    The usual caveats apply here–some of these technologies aren’t entirely ready for prime time, but in the world we live in, ‘finished’ is more likely to be used for something defunct rather than a goal for standards and tool development. The areas we’re personally most familiar with (no surprises here) are the complementary domains of vocabulary management and mapping. The first of those is up and running (although the ‘continuous improvement’ engine is going full bore) as the Open Metadata Registry; the second, mapping, is an important interest of ours and has generated papers, articles, and presentations (see below for a selection), not to mention the usual plethora of posts to blogs (including this one) and discussion lists. We believe that the OMR and mapping capabilities under development work together to enable legacy data to shift into the open linked data world efficiently, effectively, and with a minimum of loss, in the process enriching the useful data options available for everyone.*

    Often overlooked in the glitter of technology is the possibility of pulling together the communities that were torn asunder as a result of past technical limitations (and other reasons). In our common past, the library community built their data sharing conventions on a platform based on the consensus use of AACR2 and MARC. Some library communities–law and music the most prominent–were willing to compromise in order to work within the larger library community rather than strike out on their own. Others, like the art library and museum community and the archivists, did make the break, and have developed data standards that meet their needs better than the library consensus was able to do. But those specialized standards have resulted in yet more silos, in addition to the huge MARC one.

    If the intent is to ‘replace MARC’ (as it is at some level), it’s about re-placing MARC and its built-in limitations from the center of our world back into the crowd, where it becomes one-among-many. Also a value in that shift is the ability to expand the data sharing environment MARC enabled a half century ago to a broader community of interest that includes museums, publishers, and archives. Meeting the goal of dissolving those silos and making our data easily understandable and reusable in a host of ways will help initiate that ‘Web of Data’ we’ve been anticipating for many years. As Eric Miller explained so well in his Anaheim BibFrame update: by moving towards a linked data world we actually look well beyond the Library/Archives/Museum worlds by definition–it’s a very big world out there. But by collaborating with the LAM community as a whole to get there, we reap a great many benefits, not the least of which are perspectives that are much broader in some significant ways than ours. Limiting our view merely to a ‘MARC Linked Data Model’ might be an important beginning step, but it falls short of where our vision needs to extend.

    And the fact is that MARC will not be going away for a long time, if ever. There will be a lot of variation in how the transition is done by libraries, depending on institutional support, short term and long term needs, and existing partnerships. The process of moving MARC into the linked data world has already started. RDA and its RDF vocabularies was a start, as is the development of a complete RDF version of MARC, located at http://marc21rdf.info. Several years worth of pre-conferences, presentations and discussions, at ALA and beyond, have prepared the soil for these changes. But we need a plan, and some concrete steps to take–steps that include the groups who have been working in the trenches without a great deal of support, but making progress regardless. The BibFrame effort needs to be more than a playground for the technologists, because in most instances, the technology is not what’s holding us back–it’s the institutional inertia and the difficulties of finding ways forward that don’t pit us against one another. The plan we need balances the technical and social, the quick-win with the long-term momentum, and the need for speed with the public discussion that takes time and builds buy-in.

    What we have in our sights is an opportunity to reverse the long term trend towards balkanized metadata communities and to make the future one for which there are fewer fences between, and more data exchanged among these three communities with obviously similar challenges and interests. We think the time has come to use the vastly changed technology environment to do that.

    *It would be too easy for a response to this post to be in the form of “Oh, you’re just tooting your own horn here,” and indeed we are in some measure doing that. But we do this work because we believe it’s important. We don’t believe it’s important merely because it’s what we do. We believe in the value of the work we’ve done and will do, and we see a great deal of relevance for it as part of the BibFrame discussions.

    Selection of papers, and presentations:

    Jon Phipps’ presentation on mapping at ALA Anaheim
    A Reconsideration of Mapping in a Semantic World / Gordon Dunsire, Diane Ileana Hillmann, Jon Phipps, Karen Coyle
    Gordon Dunsire’s presentation at the recent London meeting “RDA, 5 years on”

    Post written by Diane Hillmann and Jon Phipps.

  • Good Grief

    Like most people who do blogging (whether regularly, or sporadically like I do), I keep a list of ideas for posts, which I often add to, but less often write up. I’ve been a very poor blogger recently, and it’s not because nothing is going on, LOTS is going on. Perhaps it’s more that I’m waiting for some point where I could nail something down, and that moment seems not to be arriving. But one of my notes caused me toI re-read a post I did over a year ago, and look at some of the other parts of that interview with the three luminaries at that ALISE program. I ran across a comment Janet Swan Hill made when asked about lessons learned from the last transition to AACR2 :

    “So I … think … the loss of independence, the loss of autonomy is one of the largest themes that I have seen. Another huge theme that I have seen in that period of time is we are still undergoing a period of grieving, I think, for the fact that we are learning that we have to put up with good enough.”

    I agree with Janet’s insight—I see that kind of grieving frequently (most often displayed as anger) coming up in the cataloging venues of our profession. I sympathize, actually, much more than I often articulate—I’m far more likely to display frustration instead. But I think the problem lies in our definition of quality—we’ve put ourselves in a box where according to our deeply held notions of what quality is, we can never again achieve anything we can be proud of, because the world won’t pay for that particular kind of quality control anymore. All of us as human beings want to be appreciated for what we do, to achieve mastery in the area of work we’ve chosen, and somehow, many think it’s not possible to do that anymore in the world we see coming.

    This is not entirely an illusion. The reality is that the old world where we built and maintained by hand our catalogs for users who needed our work to find the resources they required is gone, never to return. In fact, studies suggest that many of the newer users don’t understand the catalog at all, and use it infrequently, if ever. Certainly, because most libraries still have catalogs and still create information for them, it may be possible to maintain the illusion that there will always be catalogs, and therefore, there must always be catalogers to maintain them. We do all this work on computers, isn’t that enough?

    Well, no, unfortunately it’s not enough, because we’re still creating catalogs and catalog cards, despite the computer technology we use today to create catalog records. But though I can understand the dismay about that disruptive fact, it seems to me that there’s plenty to look forward to. Make no mistake, with that forward looking vision there are still humans—well-trained and competent humans—continuing to pay attention to quality in their data, although using different techniques and certainly fewer human resources. Far too often the changes we see coming are translated in our brains as the death of quality in our world, but I don’t think that’s the case. How we define, measure, and assure quality will change, no doubt about it, but first we need to think realistically about what it means.

    If we’re lucky and we do a good job figuring all this out, it will be ‘good enough.’ I would contend that ‘good enough’ was always the best we had on offer—there was never perfection, not ever. I remember when I was still working at Cornell, having routines that were run after every data load, to catch the known typos and other problems (some of which we’d created ourselves). Given how our catalogs were structured, this was important work, and made a difference to our users.

    I can remember, too, during the many moons I spent on MARBI, that there were many discussions about whether or not the definition or structure of a particular field or subfield could potentially be misinterpreted or misused. My colleague Paul Weiss was particularly likely to argue that we should prevent people from doing such things, and one year I got a baseball cap with ‘USMARC Police’ stitched across the front that I would throw across the table when he started up that argument yet again. My point was that there was no MARC Police, and we’d better give up any fantasy that anyone would be on the enforcement end of good practices. (Although I recently noted that there’s a musical group called ‘Marc Police’ out there). More globally, there are no data police, so instead of pretending and wearing our baseball caps to prove they exist, we need to figure out some useful strategies for this new world we’re venturing into.

    Consider, if the changes we’re talking about come to pass (and I believe they will), we’ll have statements instead of records, much less text, more batch improvement strategies, and to go along with that, different ways to measure quality. I wrote some of this up with my colleague Tom Bruce a few years ago, and it’s available here. The big message is that we need to change the conversation about quality and talk about it in an entirely new way. Quality is not about eyeballs trained one-by-one on individual records, but about new methods, new tools, and new attitudes. We will certainly need to use both our computer resources and our human resources more intelligently and flexibly, to share what we learn (whether effective or not), and to work closely with other collaborators in our endeavor—particularly the developers and coders who know more about what computers can do (and how to do it), than we do.

    But I do keep my ‘USMARC Police’ cap in my office, just in case I ever need to throw it again.

  • Fine Wine and Old Fish

    Recently I retweeted the following:
    “nice quote “your data ages like fine wine, whereas your software applications age like fish” in @mattwall’s http://j.mp/o8zsQG (via @edsu)”

    Since then I’ve been thinking about the important lesson encapsulated in those less-than-140 characters, and how we’ve not really internalized this lesson in LibraryLand, no matter how many times we’ve migrated data. I remember many years ago, when I was working in the Cornell Law Library in the catalog card era, we were told by a university official that in case of fire, everyone should grab a shelf list drawer or two and head out the door. We were pretty stunned by this instruction, but they’d worked it all out—that catalog was the biggest investment the library had, and the only way to re-create it after a fire (if for nothing else than to determine the insurance to be paid for all those lost books), was via that shelf list.

    Although a lot has changed since then, and most of those catalog cards were long ago recycled as scrap paper, the data they contained is (are?) still around, and still powering the online catalogs at Cornell. The catalog card drawers themselves were part of an ancient (and esthetically pleasing) piece of furniture, rescued from Boardman Hall, which was torn down in the 1950s to make way for Olin Library, a move many believe was a terrible mistake (Olin is the only modern building on Cornell’s Arts Quad). But I digress.

    Like most libraries Cornell used OCLC’s services to create catalog cards, not paying much attention to the data being created as part of that process until well down the road. Also like many, Cornell actually had a clutch of ‘holding libraries,’ physical spaces associated with particular schools and programs, each creating what was effectively it’s own database via OCLC. But unlike most, Cornell bit that multiple-records bullet early and when the data was loaded into NOTIS, there was only one iteration of a bibliographic record, with all the local ‘holding libraries’ attached to it. A mini-version of OCLC’s ‘master record’, is one way to look at it, I suppose. It was a sensible, if not particularly popular move, and we all had occasion later to thank our lucky stars we had crossed that bridge as a group, rather than as individuals, when we saw the headaches our comrades were coping with.

    My last data migration for Cornell was the one that moved data from the old NOTIS system to Voyager, and it was a year-long project that, if nothing else, reaffirmed my biases towards standard data. Although, like everyone else, we had some standard data (MARC bibs and authorities) and a lot of non-standard data (acquisitions and circulation), the bibliographic portion was, we agreed, the most important part, because everything else ‘hung off’ that bib record. Clearly, the data remained where our investment lay—by the end we weren’t even installing new versions of NOTIS in all the modules we used (and the ones we did install turned out to be mistakes). NOTIS was very old fish indeed by the time we moved to Voyager, and Voyager now, like most of the so-called ‘new generation’ of integrated library systems based on relational databases, is fast becoming a pungent geriatric fish as well.

    Enough of looking back (interesting as that can be). The questions now revolve around how different we think our future will look. Will we continue to use/reuse our considerable legacy of data to build the services we want moving forward? If so, what are the steps we need to take, to transform our legacy data to RDA or any other more modern packaging for our data? We have a large number of value vocabularies as well as the MARC 21 schema we still rely on, which we will need to consider part of that plan for re-use.

    I’ve seen a lot of ‘new rules for data’, but these are mine:
    –Data should be able to be encoded in a variety of ways, to suit a variety of functions, uses, and systems
    –Data should be managed at a granular, statement level, but also be available in a variety of record ‘formats’ (with records being understood as primarily an on-the-fly method of aggregating data for a variety of downstream users)
    –Although current data is expressed mostly as text strings, data improvement strategies will be designed to change most of them to URIs as soon as practicable.
    —Data definitions and specifications will be easily available on the web, allowing mapping to be simpler and easier to tweak

    And the most important rule:
    —Never, never make data decisions to fit the system flavor of the month, and ‘out’ any system that degrades our data as the price of functionality

    This is not to say that the transition of our old data to what we need for a newer environment is going to be seamless, lossless or even easy. It will be none of those things. But I would contend that it’s not rocket science either, and we’d be well advised not to indulge in needless hand-wringing until we’ve explored the issues more fully. Stay tuned …

  • What is the Change that is RDA?

    I’m supposed to be writing a paper (as part of a team and as designated herder) but like most people I have strategies for avoiding such tasks, not necessarily in ways that are entirely useless, just useless in the context of a particular deadline. In this instance, I’ve been listening to an interview of Janet Swan Hill done last summer at ALA Annual and now available on a website called “Gathering our Stories: Developing a National Oral History Program of Retiring/Retired Librarians”.

    It’s definitely worth listening to the interview—Janet has been present for many of the important moments in the collective past of most catalogers in this country, and her viewpoint is always worth listening to. This is not to say that I always agree with her—I don’t always, and in particular I don’t agree with her position on RDA. Some of that disagreement arises from the fact that she, like most catalogers (and far too many library administrators), thinks of RDA as the successor to AACR2, the cataloging ‘rules’. I, on the other hand don’t care at all about the rules (there, I’ve said it, are you all happy now?) Instead I see the potential of RDA elsewhere: in the vocabularies specifically, and not incidentally in the revolution they represent in the way we envision our future in metadata. Put more succinctly, it’s not what we say, but how we say it, that makes RDA a big leap forward.

    But Houston, we have a problem. Janet defines it very well (quotes from the transcript accompanying the video interview above):

    “I suspect that we will go ahead and implement RDA, uh, after I retire. (Laughter) I suspect that many libraries will not implement it because one of the things that proponents of RDA are most eager to say is “Oh, it won’t make that much difference. Your old records will be compatible with the new ones.” So a lot of libraries are going to listen to that and say so why should I implement the thing.”

    People, this is a huge problem for us. It’s a REVOLUTION we’re talking about with RDA, not just shifting the deck chairs on the Titanic, and it has little or nothing to do with the rules. And yes, it will cost us something to implement, but the ridiculous testing regime initiated in part because Janet (yes, this Janet) convinced the LC Working Group on the Future of Bibliographic Control to include a recommendation that work on RDA be suspended, will not help us determine whether or how we should implement RDA.

    If I sound frustrated, it’s because I am. For most of the past few years, as the RDA Vocabularies have been developed, the marketing effort for RDA mounted by the JSC and ALA Publishing has been wholly focused on the guidance text and the RDA Toolkit. Only very recently have the vocabularies and their value been included in the educational efforts that have been mounted nationally and internationally around RDA. [See the ALA Webinars coming up for evidence of change.]. The small, cranky group that developed the vocabularies has gotten even crankier as a result, but there are days when I worry that without better understanding of what RDA represents, our efforts will be too little, too late. As we all wait for the result of the Testing Theater effort (see this previous post for my opinion on that) it seems less and less likely that a clear message will emerge from that confused process, and we definitely need a clear message from those most librarians still consider the leaders of the US library community.

    The most recent cause for concern has been the draft ‘PoCo Discussion Paper on RDA Implementation alternatives‘. The beginning portion ended with literally the only sentence in the problem statement portion of the report that I could easily agree with: “In any scenario PCC must adapt to a hybrid environment.” But the question is, will that hybrid environment be facing backward or forward? And the question not asked in the report, but definitely assumed: in that inevitable hybrid environment, what would be the role of an organization such as PCC? The current value of the PCC is built almost entirely on the consensus-based environment of the past, where agreements on basic functionality of cataloging records emerged from a common necessity to provide a standard ‘floor’ below which efforts to rein in costs should not sink. But is that value the same in the future environment? Based on this report, it seems clear that the thinking of the writers of the discussion paper is still deeply embedded in the past, and they see the future as an entirely problematic extension with few opportunities for libraries or users in the change that RDA represents. “Perpetuating the hybrid environment long term will have a negative (and costly) impact on our catalogs and on all areas of bibliographic control.”

    It seems very clear from the issues presented in the discussion paper that the negative view of the future stems from the lack of understanding of what will actually need to change to enable libraries to fully implement RDA, and what that change offers us at this critical time for libraries. A real RDA implementation, with the benefits already under extensive discussion in the library community, cannot, CANNOT, actually happen in a MARC environment with the inwardly focused assumptions in evidence in the discussion paper. This is not to say that documentation, training, protecting our legacy in terms of our MARC records and authority files are not rightfully topics that we ought to be discussing, but those discussions need to happen with fuller understanding of the environment we will be working in as we move our focus to the web, and away from our current catalogs. [See Karen Coyle’s TechSource reports here and here for a great start in understanding what we need to do.]

    At the end of its paper, the Task Group proposes the following:

    “Recognizing that there is a cost associated with choosing a direction that is different from the US national libraries, recognizing that PCC institutions will face a hybrid environment, and recognizing that there is a value to the PCC in member contributions from either rule set, the PCC should formally adopt RDA, regardless of the outcome of the US RDA Test, and the decision of the US national libraries, but it should set no time limit on implementation of RDA by PCC institutions.”

    I heartily agree with this conclusion, and I say to the Task Group—tell us how we can help you consider some options that don’t stop with the unsustainable assumption of cramming RDA into MARC. Persuade us that moving to RDA is something we should embrace. Because the route you seem to outline can’t result in success, and libraries need successful paths, as well as correct decisions.

  • Meeting in the Middle

    At my keynote at Code4Lib a few weeks ago [recorded here about 90 minutes in], I got a good laugh when I equated the continuum that catalogers and programmers inhabit to that described by Kinsey in his famous discussion of sexuality. Since then, perhaps as a response to my presentation and Eric Hellman’s at the end of Code4Lib there seems to have been a resurgence of the conversation that comes and goes, particularly on cataloging blogs and discussion lists, about whether catalogers should learn to code and thus, perhaps, shift their personal position on the continuum I was describing (though probably not on Kinsey’s).

    Some examples of this discussion can be found here and here.

    To be honest, I get a little frustrated by these conversations, mostly because I think they miss the point about what it is that both catalogers and programmers bring to the table. Far too often, the conversation devolves to: ‘Why can’t you be more like me?’ I frankly don’t think that point makes any more sense now than it did some decades ago when the same arguments were made in support of all librarians learning to catalog. It’s not that I’m trying to discourage librarians, particularly the cohort at the beginning of their careers who see technology as a big part of their futures, from delving more deeply in the mysteries of code. Those who see the value and have the opportunity to learn should take advantage of that, just as more programmers working in the library sector should be exploring the history and culture of knowledge organization in libraries [A good place to start: The Intellectual Foundation of Information Organization, by Elaine Svenonius. Cambridge, MA : MIT Press, 2000]. Note that I didn’t say ‘cataloging’, because it’s more than that, just as what programmers do and how they think is only partially about coding. Whatever we can do to move ourselves closer to the middle of that continuum, to understand more about how technology works under the hood, and more about how library data was organized and created over the last century or so, the better we’ll be able to work together to solve the problems we see limiting our forward progress. For me, it’s about respect and understanding, which may or may not include emulation.

    I’m perfectly willing to admit that some of my irritation with the argument that learning to code is necessary for librarians is that I don’t know programming at all, and the likelihood that I’ll learn to program at this stage of my life is similar to the likelihood that I’ll grow a few more inches (in a vertical direction, mind you) before I shuffle off this mortal coil. I don’t think my lack of programming knowledge has impeded me in learning what I need to know about the technology that interests me and has been the focus of my career for the last 15 years or so. In fact, one of the compliments I received a few years ago from a programmer is one I particularly treasure: he told me that I thought like a programmer. It will surprise nobody that I have no idea what that really means, but I took it as a compliment, and it was certainly meant as one.

    I’m far more interested in learning more about ontologies, knowledge and vocabulary management, and information architecture, and it seems to me that this is an area where the significant gaps in librarian knowledge affect our ability to envision our future and make it happen. For the most part, we have some basic understanding about vocabularies but it’s almost entirely built on MARC (mine certainly was a few years ago), and that’s not going to help us much moving forward. This area is not, in my experience, one where programmers have either interest or knowledge, but it’s a natural extension of the path librarians are already headed down.

    According to Myers-Briggs, I’m an ENTJ, and aside from learning the interesting categorizations of people that is a big part of Myers Briggs, my take-away from the workshops I attended was that there’s no good-better-best kind of personality or approach for any particular profession, task or team. Particularly for a team, what you want is diversity, not a group that thinks all one way. I’ve never forgotten this point, and still think it’s the key to any of our endeavors. I think the Code4Lib model is a terrific one for getting our heads together and figuring out how to move forward, and I hope to continue to look for ways to get more catalogers to attend and think about how they might contribute, as well as airing these issues in their own venues. (And many thanks to the programmers who show up regularly at ALA!)

    Aside from my strong feeling that there are other, more significant gaps in our knowledge than coding, there are two additional aspects of this ‘librarians-should-be-coders’ discussion that really worry me: first is that it will discourage those who don’t have the opportunities to learn coding from learning what they need to know to understand the technology that drives our world, well enough to participate in the change we need. My second big concern is that we’ll start focusing again on the ‘why can’t you be more like me’ instead of remembering that we need the skills and understanding of a broad range of librarians and technologists to get where we need to go, not just the ones who have been convinced that coding is the best way to prove their enthusiasm and commitment to moving ahead.

  • What DCMI Should Be Doing

    One continuing theme of the recently concluded DC-2010 is that of the perpetual search for consensus on what the hell DCMI should be doing. I know this continual search for identity is a common phenomenon with this sort of organization, as it is for the human adolescent hovering around the age of 15 years. Like with the teenager, it should be seen as a healthy thing, and as most of us older than 15 know, it pretty much goes on for the remainder of life.

    For me the conference was preceded by a half day DCMI Advisory Board meeting, where one topic was the revision of the DCMI mission statement as well as the perennial topic of the conferences and how the conference series can be optimally funded and continued, and what exactly is its value for the organization. As usual, there was not much consensus, either at the beginning or the end of the discussion, though it must be said that the conference itself probably shifted some opinions about the value proposition. Generally the AB meeting has been scheduled after the conference, with the idea that this shift in perspective is a good thing for sparking discussion, but for logistical reasons the meeting was held prior to the conference this year.

    As it turned out, this change in placement of the AB meeting was unfortunate, given that Mike Bergman’s keynote on Friday morning contributed some important outside opinion to that basic question of mission. (Mike’s post about the keynote is here.) The fact that Mike arrived in time to sample a good chunk of the conference and to talk to a variety of participants gave his opinion the credibility that only exposure to the culture of the organization and the personalities that affect that culture can bring to a keynote. It was clear to me, in talking to him during the conference, that his view of DCMI was not the insider view of a contentious, financially strapped and sometimes dysfunctional organization, but instead one that included recognition of the experience, knowledge and potential there as well. In a nutshell, Mike Bergman was telling us that DCMI’s role in the emerging linked data world was critical, and should be focused primarily on expanding the presence of useful semantics available to the the web world, closing the ‘semantic gap’ he sees limiting the growth of linked open data.

    Later in the day, my task was to lead a discussion of the work of the DCMI/RDA Task Group, of which I’m co-chair with Gordon Dunsire. Gordon and I had both prepared slides for that meeting—mine covering the history and work of the task group, what we’d learned, and what remained, and Gordon’s covering the related important work he’d been doing in parallel with IFLA. I’ve been frustrated for some time with the lack of attention and traction we’ve received for this important work, both from DCMI and the Joint Steering Committee for the Development of RDA (JSC). We have found ourselves at the stage where DCMI is waiting for JSC to make some statement about the work done (in the form of approval), and the JSC is waiting for DCMI to endorse the Task Group’s assertions made about the work done and its usefulness for the Semantic Web—or at least this is the way it seems from the point of view of the co-chairs. It’s as if both groups are standing opposite one another in a middle school gym, the ‘boys’ and the ‘girls’ waiting for someone to move towards the middle. Nobody seems to want to make that first move, and though in the case of the TG, each conversation with representatives of both parties seems to be positive, resolution of the concrete issues moves at a frustratingly glacial pace.

    But as I spoke about this work to various people, continuing to think about the ongoing conversation about what the role of DCMI should be, particularly in the context of Mike’s keynote, it struck me that the DCMI/RDA Task Group was in some sense a model for what DCMI could do to fulfill the role Mike saw for us in the world. In essence, the TG came into being because Don Chatham at ALA Publishing took the initiative to bring DCMI and the JSC together, where the DCMI message was “How can we help?” The rest is history, but we seem not to have learned from that how powerful that simple question is, and where it could lead. DC-2010 brought a number of new communities to the conference, representing a variety of groups interested in moving into the wider web world of information, but lacking in-house knowledge and skills necessary to make progress. Helping them move forward requires much more than attracting them to the conference and talking to them in the hall or after tutorials. We need to offer more concrete help, like we did for the JSC, and move the knowledge and experience that the DCMI Community has assembled into the broader world of information.

  • Jenn Riley on RDF

    Ten days or so ago I took some time out to listen to a webcast by Jenn Riley, ‘RDF for Librarians’, which was well worth the effort. Jenn has been worth watching for a long time, and she’s done us all a service by putting out her slides and a bibliography as part of this effort. All these, plus a recording of the presentation, can be found at: http://www.dlib.indiana.edu/education/brownbags/ [I should note here that I’ve had trouble accessing the recording, and Jenn and her IT folks are trying to figure out why, but you may not have the same difficulty I had.]

    The topic Jenn chose for this presentation is one that has challenged many of us who have been trying to talk about standards developing outside of libraries, like RDF, to traditional librarians. Jenn keeps her eye on the prize throughout, building on what librarians know in order to bring them across the great divide to an understanding of RDF, without getting bogged down in the technical language of the standard itself. She manages to cover a great deal of territory in the presentation, including such difficult topics as blank nodes, graphs, literals, the differences between XML and RDF, and the differences in terminology between the library world and the RDF world. Anyone who is interested in this topic, or has attempted to teach it, should take a look at this presentation and Jenn’s slides.

    I was especially appreciative of Jenn’s message about all of us being ‘part of the process’ of the library transition to these new standards—and the fact that she included our RDA work as an example. It’s sometimes difficult to feel recognized as ‘at the table’, representing the interests of libraries, while being largely ignored by the big kahunas of libraryland. Jenn reminds us that each of us a responsibility to lead, and not to wait around for the usual parties to do that for us, and she doesn’t just talk the talk, she’s walking the walk.

    Thanks Jenn, and I’m looking forward to seeing you at DC-2010 and talking with you about those thorny issues that still challenge us!

  • Reading Tea Leaves

    Among the ongoing efforts with potential to change the range of options available to libraries, I would count the evolving Lyrasis organization among the most interesting, if not, certainly, the most visible. In the past few months, the organization has launched some interesting initiatives, among them a ‘partnership’ with OCLC, in the form of an “ … agreement that will provide increased consulting, education and engagement programs for WorldCat and new cooperative Web-scale library management services” and another with SkyRiver to provide cataloging services (press release available as pdf from the Lyrasis front page). Among other things, these strategic partnerships put Lyrasis in a challenging position regarding the SkyRiver/III lawsuit against OCLC, but I’m sure they’ll manage to navigate those dangerous shoals, given the careful path they’ve chosen so far.

    I recently became aware of the report of their Library Director Summit on the Future of Cataloging, held on May 26, 2010, with a summary made available recently. I’m of two minds about the summary–on the one hand it’s hard to argue with the notion that if you’re in any kind of business, and have customers, it’s good to ask them about what you ought to be doing. On the other hand, I keep remembering Henry Ford’s statement that if he had asked his early customers what they wanted, they would have told him: “faster horses”. Providing some balance between what libraries tell them about their needs, and building in the leadership to provide for needs that are not yet expressed by their customers, will be key to their survival in the volatile environment of change we live in now.

    Peppered in the summary report are some statements that give one hope that Lyrasis might be asking some of the right questions as they look for a business plan that will take them where they need to go, and to avoid being an organization operating primarily in the foamy wake of the big players. For example, the first bullet under “What Still Needs to be Cataloged?” says:

    “Cataloging records for basic English-language monographs are commodity items. Many libraries already outsource much of this work through vendor-supplied, shelf-ready cataloging (e.g., PromptCat, YBP). As records have become commodities, libraries question why they are still paying premium prices, especially when many records are available and shared freely on the web via Z39.50.”

    Much as I agree that the current record sharing market does treat catalog records as commodities, that way of thinking doesn’t get us anywhere we really want to go, witness the Study of the North American MARC Records Marketplace by R2 Consulting to the Library of Congress this past fall (for my take on it, see this post). That report argued for more remuneration for LC, and put everyone else, particularly those using Z39.50, in categories with labels like ‘opportunistic.’

    More on cataloging costs comes later in the summary, where the lack of transparency about costs and pricing is aired (familiar to those reading the conversations on the SkyRiver suit playing out on various library lists) and an interesting correlation is made between the current subscription pricing model used by (presumably) OCLC and the pricing model for high-cost ejournal subscriptions. I say presumably because like the gorilla in the kitchen, the entity looming over the discussion is named only in one recommendation at the end.

    Further along in the summary, the diminishing role of the catalog as a discovery tool is acknowledged, as well as the continuing need for the catalog as an inventory management tool. Interestingly, the decreasing value of the “global union catalog” is also acknowledged:

    “While the union catalog function was important in a print-based environment, it is no longer the key resource it once was in the book-dominated world. Once the metadata is available and harvestable, it does not necessarily have to be housed in and served from one central repository to make the content accessible.”

    Resource sharing is addressed again later in the report, along with the unfortunate fact that resource sharing and catalog record acquisition are often intertwined. That said, the section on resource sharing seems a bit obscure to me, partially because that’s one of the few library arenas in which I was never involved during my checkered career in libraries.

    Reading this summary, it’s necessary to read between the lines to glean much about the tenor of the conversations. The rewards for that effort are the glimpses of movement on the part of the organization and its customers on these important issues. That they’re only glimpses is unfortunate. While I can certainly recognize the need for Lyrasis to be circumspect–their survival depends to some extent on not making powerful enemies–I’d love to see these issues aired more publicly, with less dancing.

    Shifting the Conversation

    After the emphasis above on the good news, there are a few places where the conversation has clearly not yet shifted sufficiently from the old thinking. One of these areas is the perennial question of ‘record enhancement’ which is here discussed in the old context of ‘record perfection’ rather than the newer context around the improvement of data to provide greater value to users. This is unfortunate, particularly since the comment on ‘harvestable’ data earlier in the discussion might have led one to hope that some of the library linked data efforts had percolated up to the director level.

    Another area in the report where discussion clearly needs to shift is in the notion of what’s to be done with the cataloging staff when we’ve changed how we look at cataloging? What are we to make of this?:

    “A whole generation of catalogers is at retirement age. Some describe themselves as “depressed” because they believe they will never be replaced, that this is “the end of our profession,” and libraries are “undoing their life’s work.” Nonetheless, one library reported that recently it had intentionally hired two new catalogers because its believes it is still valuable to have a cataloging-articulate perspective and voice within the library. The new librarians hired to fill this role are described as being more tuned into how to bring the users in to interact with the catalog and have a more external (user-centered) viewpoint than previous generations.”

    Well, now I’m depressed. As someone who’s been speaking (and writing) on this topic for years to anyone who will listen, let me say that any library who is not now engaged in exploring what their catalogers need to know to make an effective transition to a new environment is not just missing the boat, but leading the way down the deep, dark path that will be where libraries who think change is not inevitable will be going when it’s no longer possible to dodge the bullets. Directors–do you have anyone else on your staff, besides the catalogers, who is capable of thinking about your catalog records as data, and not just catalog records? If you do, consider yourselves lucky, and please, treasure them. If you don’t, start investing in some training for those catalogers, because you’ll need them and their expertise, no matter what happens and no matter what external services you see in your future. Trust me on this. Oh, and if you think that anyone will be able to persuade your users to interact with the catalogs you have now, I have a bridge you might be interested in purchasing for your front lawn.

    Now that I’ve gotten that off my chest, on to the rest of the summary. I admit to a bit of confusion on the first point under “What Should be Done Concerning Cataloging of Local Digitized Collections?” The point is well taken that libraries are not now able to measure the value of their digitized collections to researchers generally and that usage data is missing on how researchers find these collections to start with, but there are a couple of sentences embedded in the first paragraph of that section that left me scratching my head:

    “Libraries gave strong support for the idea to develop a scholarly “impact factor” that measures the value and return on investment of digital collections. Such a factor may require data to be embedded within the metadata for these collections.”

    I think I keep pretty good track of what’s going on in the world of metadata, both within and outside libraries, but what is meant by ‘ … data to be embedded within the metadata …”? Are we talking about licensing, viruses, or what?

    The recommendations on the last page, couched as answers to the question “What Can Lyrasis Do To Help?” seem like the most conservative outcomes one could imagine for what may have been (hope springs eternal) some pretty interesting conversations. How about at least one game-changer in there, like:

    * Lead. Explore ways for libraries of all kinds to participate in the data revolution happening around them, sometimes referred to as library linked data.

  • Sex, Drugs, and Rock & Roll

    As one who entered college in 1966 and experienced the sixties from the front lines, I sometimes wonder how I got to be so old and stodgy. I particularly think of this when I pass plate glass windows while walking on the street and glimpse my reflection in them. Who is that gray-haired old broad in the window? It’s always a shock, despite the fact that I’ve been gray-haired for a very long time, and demonstrably growing old at the same rate as everyone else.

    I’m sure some people reading this are laughing at the self-characterization “stodgy,” given that in some quarters I know I’m thought of as a very radical library ex-cataloger with unfortunate tendencies to disparage the status quo and suggest outlandish changes to how things are done in libraries. I suppose I use the “stodgy” bit to suggest that it isn’t necessarily the case that I believe we have to throw out everything we’ve done in the past in pursuit of new approaches. I do a lot of evangelizing on this point, both because I think it makes change less frightening, and because I believe we know a lot more than we think we do about what needs to change, we just have trouble separating that knowledge from the familiar and comforting packages we know so well. We’ve been distributing our knowledge in those packages for a long time, and it’s human nature to stick with what we know when we’re challenged. After all, in our early days as a species, we learned to eat the familiar stuff because we knew it wouldn’t kill us. Those who preferred the new and unfamiliar invariably ran into trouble, and often failed to pass on their genes. Our genes come from the people who knew that the new stuff could kill you.

    My own experience with change has been a mixed bag, certainly. When I was in college I worked for the campus radio station (I was a TV-Radio major). Because I had radio experience in high school, I got a “job” immediately in my freshman year, doing a program called “Dinner Date” which utilized only a certain narrow set of recordings (then on vinyl only, of course). I was supposed to play only instrumentals in the genre that we now refer to as “elevator music.” I tried, in vain, to shift the playlist a bit over to slightly jazzier stuff, bossa nova, and suchlike, but that didn’t go over very well with the then powers-that-were. (I should point out that in those days women weren’t allowed to read news because our voices didn’t have the proper authority—but that’s another story). The mission of the show was to provide quiet background music for people who might be eating their dinner, the music also interspersed (and this was not explicit, but we all got it) with a sexy female voice to keep people coming back. This was an interesting time to be doing educational radio–which was what we were supposed to be doing–before NPR and public radio, when there was a distinct boundary being maintained between commercial and non-commercial radio which didn’t have anything to do with the presence or lack of advertising. Rock and roll, which was what we all wanted to play instead of the classical music leavened with a bit of folk, jazz and elevator music on the side, was not allowed.

    Our Music Director at that stage, in charge of our quite extensive library of recordings, was a fellow who rather blindly followed the practices of the past, and as part of his job he reviewed all new records that flowed in on the gravy train of freebies provided by record companies. As he reviewed, with the use of a sharp tool, he rendered unplayable all those tracks unsuitable for the mission of the station at that time. After his tenure, a real musician became the Music Director, and he put a stop to that practice, but in the meantime, the station and its music collection was permanently disabled. When the station began to change (it’s now an NPR station specializing in Jazz) their collection of recordings was almost unusable. (Now that I think of it, this strategy reminds me of the practices I railed against in my early days at Cornell, where catalogers were told to delete MARC fields that the library then had no use for, which subsequently had to be laboriously re-done when fashions changed.)

    I’ve been reading Karen Coyle’s “Understanding the Semantic Web: Bibliographic Data and Metadata,” (Library Technology Reports, Jan. 2010) both because I want to comment on it more fully in this space and because I’m preparing for a class I’m teaching in the Spring quarter at the University of Washington (more about that later). Since I loaned my paper copy to Jon and won’t get it back until Friday, I’ve been limited so far to reading the first chapter, “Library Data in a Modern Context,” which is available online, and includes in its closing paragraph the following:

    “The need to change does not mean that what you are doing is wrong. Instead, it often means that something in your environment has changed, something that you cannot control.”

    This strikes me as a critically important point. Looking back I can see that much of our conversation about what is happening in our environment, and what needs to be part of our change strategy, is being heard as blame: “You’re doing this all wrong.” And that’s simply not true—if you don’t believe me that where we are makes perfect sense if you understand the ‘why’ of it, read that first chapter. Karen has a wonderful way of explaining things (one that I envy, I have to say), and she does a great job in taking the reader from the nineteenth century and Panizzi to the present day, and it all hangs together. It’s clear that we’ve been responding appropriately to the change in user needs and technology, and I for one think we can do it again, once we move beyond the blame game.

    I get a lot of questions about how and when this change will happen—nobody really wants to be on the bleeding edge of some of this, nor to they want to be left behind, but the effect of all the strategic planning seems to be that we are all teetering on the verge of some tipping point we can’t quite see clearly. “What’s it going to take?” they ask, and I have to be honest, I don’t know. Maybe the smartest thing would be to just declare that we’ve passed that tipping point and stop waiting for somebody else to take the first plunge. Maybe if we could get everyone to read Karen’s report (the printed version can be ordered from ALA directly), as well as to look for the February issue, which will also be Karen’s work, we’ll have the courage to make a move in the right direction. Hope springs eternal (and perhaps that’s the ‘drug’ referred to in the title!).