Author: Diane Hillmann

  • Making connections

    This past Friday I dug out my go-to-meeting clothes and made one of my occasional forays down one hill and up the other hill to my former place of work, Cornell’s Olin Library. The occasion was the monthly meeting of the CUL Metadata Working Group which I try to show up for when I’m not traveling. This month’s speaker was Sarah Shreeves, from the University of Illinois, Urbana-Champaign (UIUC). Now, I’ve known Sarah for some years, and have worked on a project or two with her, so this seemed like a perfect opportunity to dress up and get out of my cozy office for a morning to see what Sarah was up to. It helps that the weather is improving, this being pre-Spring in Ithaca (still largely gray skies, but mostly without the white underlay).

    Sarah’s presentation is described on a WG page devoted to her visit, though her slides aren’t up yet as I write this. She talked primarily about a project UIUC is working on with the University of Wisconsin, called BibApp. The project’s aims are focused around research and collaboration on college campuses, looking for ways to bring together experts, their output, and information about them. Sarah’s role at UIUC includes their institutional repository, the point person at UW is Dorothea Salo, a self-described “repository rat,” and the presentation made quite clear how BibApp provides important support for IR’s in general as well as alternatives to the clunky interfaces most of them come with.

    From my admittedly metadata-centric point of view the most interesting things Sarah demonstrated were the backend work they do with author name disambiguation and automating the determination of what can legally be deposited in the IR from the oeuvre of a particular author, based on the publisher of the item. Depending on the research community, these items may have metadata available from A & I providers, MARC metadata, or no metadata at all (book chapters and conference publications often fall in that last category). The project is developing a tool that can support the work of librarians or other trained staff in determining who an author with a particular surname and forename initial might be, using a combination of human and machine intelligence. Although it’s not authority work as we know it, once we get to a mashup phase in the new world of authorities, the data provided by this tool will be quite useful, based as it is on the occurrences in the publications themselves, as well as linkages to additional information on the author (his/her institutional affiliation, email address, etc.) There’s already a somewhat primitive XML output, but even as it flashed by (not on the presentation, but as part of the discussion) I could see some possibilities.

    In this application, being able to match the publisher name in the metadata with data about publisher policies to determine whether pre-prints, post-prints, author copies or all of the above can be legally deposited saves a great deal of time both for librarians and faculty. As Sarah was talking about this, I was struck by how clear a use case this was against traditional library practice of transcription of publisher information. I suggested this to Sarah and she agreed that they really needed standard forms, not transcribed data, to make this sort of tool function well. RDA’s approach is still focused on the idea that transcription is the best way to assure uniformity, but in my opinion that approach only provides the illusion of uniformity, and the number of LC Rule Interpretations for AACR2 on this point suggests that in a world where human resources will be spread thinner than ever it’s time to jettison transcription of important data elements. The alternative that we need to implement is to treat publishers as corporate bodies and control their names as we do other names, and this will certainly be technically possible in RDA, but is not what the guidance instruction tells catalogers to do.

    Another really nifty feature Sarah demonstrated was the analyses of publication patterns of different groups of researchers that were enabled by the tool once the publications themselves were available in one place. The BibApp tools are being tested using a variety of research groups, some science and others humanities, highlighting important differences between the cultures of these research areas. I was impressed by how sensible the approach of the developers has been, and how they appear to be using a nicely iterative approach to working through their results and keeping their goals in mind. In a world where university administrators need reminding of the importance of libraries and the work they do, this sort of project stands out like a beacon—meeting a number of promotional and marketing goals through a very librarian-ish organizational approach with some quick wins in the bargain.

    That said, this is not the ginzu knife that some may be looking for, and the developers are sensibly determined to keep it light weight and focused. Nice work, Sarah, and a very effective presentation as well.

  • Letting go

    Some of you may know that a few years ago (2005 actually, as I look at my files) I worked with the ALCTS Continuing Education group to set up a “Metadata Standards and Applications” workshop, as part of the series of workshops they were developing with LC funding. At the time, I was intrigued by the set of course series objectives I was given by the committee:

    • To equip catalogers to deal with new types of resources and to recognize their unique characteristics
    • To equip catalogers to evaluate competing approaches to and standards for providing access to resources
    • To equip catalogers to think creatively and work collaboratively with others inside and outside their home institutions
    • To ensure that catalogers have a broad enough understanding of the current environment to be able to make their local efforts compatible and interoperable with other efforts
    • To prepare catalogers to be comfortable with ambiguity and being less than perfect
    • To enable practicing catalogers to put themselves into the emerging digital information environment and to continue to play a significant role in shaping library services

    All these seemed really important to me, and I was eager to try and set up something to meet those objectives. At the time, the notion was that LC would hold rights to the work, and I would contract to deliver the workshop materials. It wasn’t a lot of money, but I was sensible both of the honor of it and the challenge. After a great deal of back and forth with the committee and others, the first workshop was held in July of 2006, as a “train the trainers session.” The idea, as in most of the other successful ALCTS efforts, was that a group of trainers would be able to spread the effort around, and provide a variety of face-to-face efforts for both general groups of catalogers and specialized groups. At the time, workshop organizers needed to work with LC CDS to arrange for materials to be printed for trainers and participants—but last year LC got out of the business of printing materials (and attempting cost recovery from the workshops) and made the materials available for free.

    I think I presented the workshop somewhere between 6-8 times, usually with another trainer (two full days is a long haul for one person, even one who knows the materials as well as I do). I’ve no real idea how many times it was presented by all the folks who were in the trainers group, but it was my understanding that it was one of the most popular workshops in the series. In fall of 2007 I did a full revision of the slides, and sent them to CDS, but I found out later that the updates I did were never integrated with the workshop materials. In April of last year I was contacted by one of the participants in an earlier workshop, who wanted me to present it to a group of Canadians in the fall. We agreed on dates and a co-trainer and everything was going along as usual when I got an email from someone I knew slightly at LC who’d taken over the management of their training efforts.

    At that point I was told that the materials had been entirely revised by two LC staffers (both of whom I knew) and that the version they’d created was now the “approved” version. I’d had no idea this was in the works, hadn’t been consulted or even informed, so needless to say I was pretty unhappy about this news. I was reassured that this was inadvertent, that everyone thought that someone else had “informed” me of this, but it seemed to me that if there had been a good faith effort to consult with me about suggested changes, the question of “being informed” would never have arisen.

    When I was able to view the slides, I was even more unhappy about the situation. Not only did they now have LC slide themes, but the whole thrust of the workshop had changed. There were many more slides about MODS, MADS and METS (accompanied by more LC examples), and a new emphasis on PREMIS (including what I felt was an unrealistically complex exercise). There were also errors introduced about OAI-PMH (that section was cut drastically), and misstatements about Dublin Core, and a number of other worrying changes. I told my contact at LC that I would not present the Canadian workshop with the “approved” slides but would update the slides I had to reflect some of the changes in those slides that I thought were improvements. Thankfully I had help from Rhonda Marker, who’d presented with me before and was booked for the Canadian adventure, and we finished a new improved version of the slides in time for the Canadian workshop. We tweaked them a bit more, and shipped them to LC.

    There were a few more interchanges, but it became increasingly clear that what was at issue was not the examples, or the specific content of slides, but a very basic difference of approach. My approach was not necessarily to provide solutions for librarians, but to survey the landscape with them and try to affect how they thought about their choices and how they make decisions. When I presented the workshop I spoke frankly about the advantages and disadvantages of the available metadata formats, and particularly how I thought they might hold up in the future. I tried to provide perspectives that were not just library perspectives on the world, recognizing that they were probably working with technical people with whom they had no shared language or frame of reference. It seemed to me that they needed to understand what was going on outside libraryland, and to think differently about how technologies being discussed in that world might affect their work.

    I didn’t see that in the LC slides. I was told that the changes made were in response to comments by other trainers and participants, but yet, the evaluations from the workshops I gave were quite positive, and this sense was confirmed by several other trainers I knew, who did the workshop frequently and had made their own modifications in the slides and exercises to suit their styles and experience (this was always fine with me, by the way). One statement in the back-and-forth between me and LC stands out—the LC revisers of the slides felt that the workshop should be more “practical,” which their version indeed was, if one bought into the notion that what librarians really needed was more about MODS, METS, MADS and PREMIS.

    As I pointed out to my contact at LC, I disagree pretty strongly with that approach. Librarians need to look beyond standards (whatever your definition of standards) created within the library community, based on the ways we’ve always done things in libraries. New standards are coming down the pike: RDA, FRAD, etc. Unlike MODS and MADS, these are based on the FRBR model, not the MARC model (if there is indeed such a thing) and have formal structures that can be used easily by libraries and by others outside libraries. We do our colleagues no favors by promoting solutions based primarily on how comfortable and familiar they seem, and what institution is responsible for maintaining them. Will MODS and MADS survive the transition to RDA, FRAD and FRBR-aware data? I don’t think so, and I can’t therefore recommend those solutions to librarians looking for answers to their digital project questions. As I said to my contact at LC:

    “[Librarians] need to be able to THINK about these standards in a broader context, ‘get’ the issues they present in an implementation environment, and understand how they can make decisions today that will still seem sensible five or ten years down the road.”

    If that’s impractical, so be it.

    So, the upshot is that I’ve asked that my name be taken off LC’s version of the slides, and I’ve made it very clear that they should take me off the trainers list too, because I won’t present their version of “Metadata Standards and Applications.” I’ve also told them that they are welcome to use any of the slides I’ve sent them for any version of the workshop. My slides will continue to be available on my website at http://managemetadata.org/msa_r2/ and I’m hoping to continue to develop them to include RDA and other new standards as they become available. So, for those of you planning to present the workshop, expect to be asked to agree to give the workshop as LC has revised it (I hear that the LC slide themes will be removed, but the content will remain the same) or you won’t be able to advertise it as a Cat21 workshop.

    I’ll be doing my workshop, or nothing; but that’s okay. I’ve got places to go, many interesting things to do, and I’m done arguing about this one.

  • Denver Midwinter: All RDA, all the time …

    Yes, it was laughable to imagine that I might blog from Midwinter—silly me. My schedule was insanely full and I didn’t even get to peek into the exhibit hall, much less visit and pick up some swag for the grandchildren. As things move along with RDA, and as I become even more convinced that despite its flaws we need to have it out and used, my conference program became even more ridiculously focused on anything RDA. So there I was at both CC:DA meetings, the RDA Testing meeting, the RDA Implementation meeting, and on, and on.

    I posted briefly before I left for Denver on the work Metadata Management Associates (me and Jon) will be doing with ALA Publishing in relation to the RDA Online product. Some of this will involve integrating the RDAVocab registered elements, roles, relationships and value vocabularies, with the online product, thus ensuring that catalogers using the online product and applications using the Registry output will be linking to and/or referencing the same information (no synchronization issues!) Other tasks involve building XML schemas so that those seeking to build data—whether in the tool or in another application—have somewhere to start. We’ll be working on other bits and pieces to enable support for those trying to see their way forward from where they are to a world where RDA with a FRBR foundation is the way we do description. This is a tremendously exciting project for us and it was nice to see that when I explained it to others they thought so too!

    The RDA Testing meeting, led by Beacher Wiggins, was an interesting one—more so than I had anticipated. The idea is that the effort will be led by LC, NLM and NAL, but it will be open and participants from a variety of venues (including library students and recent graduates) are encouraged to sign up. Beacher emphasized that testers will use the environments they have available, which for most means MARC systems, but if RDA Online can produce records as well, that’s an added opportunity, particularly for systems eager to figure out how these records might behave in newer systems. Testing will last about six months and include a training phase, an active record creation phase, and an assessment phase. After that, the three national libraries will make individual “go” or “no go” decisions. There will be a website at some point, most likely a subset of the website of the LC Working Group on the Future of Bibliographic Control.

    There were a lot of questions about this testing effort, only some of which were asked or answered at the meeting. One of my concerns (which was too fuzzy and formless to ask at the meeting) has to do with the usefulness of testing how much time it takes to create a record under the old regime (AACR2 and MARC21) vs. the new regime (RDA and MARC21? or RDA and the RDA schemas and tools?)—you see part of the problem here. The deck seems pretty stacked towards the old and familiar, despite some attempts to create more balance by ensuring that some of the anticipated participants—the library students and recent grads primarily—will have as little experience with the old regime as they do with the new one. In all cases there will be “subjective” assessment solicited from participants as well as the “objective” results (the time invested in record creation). Part of the plan is that there will be a 20-30 item list of resources to be cataloged, and most participants will do one regime or the other (not both) for a particular resource, with hopes that aggregation of a large-ish number of results will provide a more reliable measure. I’m not sure the “timing test” is going to be particularly useful, given the number of uncontrollable variables likely to be introduced along the way—particularly in whatever technical environment is used—but I’m sympathetic with the notion that looking for a useful objective test in this situation is extremely challenging. It’s obvious to me that we’ll learn something from the objective and subjective portions of the testing, but whether what we learn is going to be clear enough to support either option with sufficient clarity for those who prefer evidence-based reality is quite another story.

    Given the fact that the testing results are likely to be subject to various interpretations and caveats, it’s hard to imagine how any of the national libraries could justify a “no go” decision, and what that would actually entail, if one or more might be inclined in that direction. One hears rumors, which naturally can’t be attributed, that one or two are so inclined but it’s something I’m really curious about. Would a “no go” decision be something like “no go until 2011” or “we’re sticking with AACR2 and MARC21 until Hell freezes over,” and how long would that be supportable? Two years, five years, maybe? It all depends on how long and how messy one thinks the transition would be, and how many would be inclined to lag far behind the early adopters waiting for some undefined
    tipping point. I tend to think that there will be enough of the early adopters, particularly in the open source development community, that by the time the “go”/”no go” decisions are made, the “go” decision would be almost inevitable. But I’m an optimist on this, as I’m told fairly frequently.

    Of course, the timeline for testing is dependent on RDA Online being released on time (3rd quarter, 2009) complete with vocabularies. I’m an optimist on that, too, which is a good thing, since some of it depends on me continuing to work relentlessly on some of my task list. More on that topic in other posts …

  • Collaboration between ALA Publishing and the NSDL Registry

    Some of you will already have seen the blog post by Patrick Hogan on the ALA Tech Source blog. This is an exciting new collaboration for us, and in some ways represents the culmination of the DCMI/RDA Task Group efforts to register the RDA Elements, Roles, and value vocabularies. We figured that seeing the vocabularies in the Registry would highlight the importance of the formal representation of those vocabularies, and lead to good ideas for embedding them into actual products of use to libraries. This is certainly what seems to be happening.

    Because this announcement came out so close to Midwinter, much discussion on the implications of this collaboration will happen in the context of RDA programs, meetings and hallway chats. I will certainly be reporting on some of those discussions from Midwinter or shortly thereafter.

    Stay tuned.

  • The XC Project White Paper–well worth reading …

    … and I say that not just because Jon and I have been working with the Project on their metadata planning. It’s an excellent paper, and we’re delighted it’s out, so we can tell people about it, and encourage them to read it and talk about it. We’ve been talking up the XC Project as one that has been doing important work and moving forward in ways that reward our close attention. But until now we’ve found it hard to find something to which to refer interested parties, given that so much about what XC has been doing has been happening under the surface of the pond. Now we won’t have that problem. Go look at the paper here.

    Jennifer generously mentions the inspiration of our ideas—as reflected in one of our grant proposals (which wasn’t funded and isn’t publicly available). We’d like to point out that many of the ideas in the proposal are available in previously published papers, all of which are linked from this site.

    Takeaways from XC

    Jennifer rightly and effectively presents the practical decision points in the XC project and documents them well. But there are bigger issues underlying those decisions, and it’s important to note how they fit into the larger task of building services in an environment as fluid as the one in which we find ourselves.

    “It is also important to understand that the XC Schema represents a purely practical rather than a theoretical approach to using metadata. While much interesting work is taking place in the library community to develop theoretically consistent metadata frameworks, models and carriers, the process used to develop the XC Schema should not be confused with these start‐over‐from‐scratch‐and‐do‐it‐right approaches. In some ways, the XC Schema represents exactly the opposite. For XC, we have attempted to manipulate and make use of the metadata in various schemas that is available to us, and to use this metadata in a way that it can be shared with others. While ours is not a theoretical approach in itself, we believe that the work that we are doing can inform the work of those who are developing more theoretical approaches to the future of library metadata. Our experiences should provide a reality check regarding the feasibility of retrofitting legacy metadata into a new theoretical framework. Much of the effort needed to retrofit library metadata for use in new applications alongside metadata that originated in other schemas is likely to require considerable experimentation. The XC Schema is designed to embrace and facilitate that experimentation.”

    Despite Jennifer’s emphasis of the practical solutions (and the fact that she has a notion of experimentation that is foreign to most librarians), there are some important theoretical underpinnings that she illustrates in the paper, and I wanted to hit on a couple that I think are important.

    The benefits of “dis-integration”

    It’s ironic that libraries have been urging their vendors for years to integrate their platforms better, and now we’re taking a quite opposite approach. Jennifer nicely describes how this works in XC, and the rationale behind those decisions. Many in libraries have come to the conclusion that discovery services needn’t be bolted to data management services, but XC goes several steps further, and unbolts data management from the ILS as well.

    “Dis-integration” is critical in bringing libraries out of the current environment of tightly bound library systems built on MARC and depending only on one another for data. Libraries today have too many silos of data for that strategy to endure: IRs, projects of all kinds, commercial partnerships, etc.

    Iteration vs. Perfection

    I was talking to a colleague new to libraries recently and describing how data was moved from one platform to another in the days when I was still working in academic libraries. Back then, we spent almost a year planning the “migration” from NOTIS to Voyager, and had contractually specified two test loads of our data into the Voyager test system we had up. These loads were then tested extensively, using specifically chosen test conditions and records (we had our own test plan, which was extremely detailed and fine tuned—we didn’t trust the vendor at all). After each load we would specify changes that had to be made before we could do another test load. The third load was the real one, it was final, and all the data had to be as perfect as we could make it, as we had no other chances. For months before the loads we had students sitting in front of computers making changes we couldn’t make programmatically and programmers slogging through the ones we could, knowing that it would take years to re-create the knowledge and tools to do them in a new system. They did the last changes about 20 minutes before the data was extracted for the “real” load. Stress, anyone?

    Consider the difference in XC. The normalization and transformation services are independent, they maintain their own data stores, and they’re designed to operate independently. Data services can be tweaked as experience and changed goals dictate, and data can be moved through the services any number of times, until the result is optimal, without interruption of any user delivery services at all. It’s an ideal strategy for an environment where nothing is stable, change is perpetual, and nobody can afford to wait until things settle down (they may never, you know).

    The XC strategy also supports the construction of an environment where many entities can build usable services and the expansion of overall service capability (and the cost of creation and maintenance) can be shared broadly.

    Taking the Leap

    One of the most important things that Jennifer’s paper illustrates is how libraries can make the leap from legacy data and systems into the future of library data. A lot of people are scared by this — they figure that there’s no way to make the leap unless we know more, standards are more complete, agreements are made. XC has provided real leadership here, by showing the value of jumping in and trying things out. They are showing far more leadership than the institutions (you know who they are) we have always depended upon to lead us forward.

    The only possible response to this effort is close attention and engagement. Take a look at the supporting documentation Jennifer provides, engage her in conversation about this work, and take inspiration from her willingness to try out new ways of doing things.

    We’re all very proud of you Jennifer—keep up the good work!

  • LCSH.info–gone but not forgotten

    The library blogosphere is reacting with shock [1, 2], anger [3], and disappointment [4, 5, 6, 7] at the news that LC has asked (as in “ordered”) Ed Summers to take down his wonderful experimental LCSH.info service. It’s not entirely clear why they did this, and Ed has been carefully circumspect about the reasons. LCSH.info was a project that Ed had accomplished largely on his own initiative, and despite the fact that he certainly had some important support within the institution for building it, he too readily takes responsibility for not gathering the broad institutional support that appears to be a necessity for sustainability at LC. Still, it’s easy to speculate that others were embarrassed by it (as in “embarrassed that Ed could do it, and yet there’s still no official service”), particularly given the fact that the domain was not “loc.gov.”

    LC has been “planning” (or so they say) to create just such a service since well before the Working Group on the Future of Bibliographic Control but we’ve seen no real evidence of it, except for what Ed has done. I was one of the people who spoke to that group during its fact-finding year, making the point that the vocabularies that LC manages for the library community (LCSH, LCNAF, LCSAF, etc.) should be available as web services for the benefit of the that community (I was assured then that such plans were afoot.) LC could have wisely allowed Ed to maintain the site until such a service was in place and then Ed could have made a simple change that would have redirected lcsh.info URIs to the official service, and all would have been well. Instead, LC has let the world know that its management is technically and politically clueless as it destroys, without even an official announcement, a service that many organizations, regardless of disclaimers of its experimental nature, had welcomed and some had come to depend on. This had roughly the equivalent impact on the confidence of the Linked Data community in LC that letting Lehman Brothers fail had on the investment markets.

    Although LC frequently cites the legal necessity to do cost recovery on the vocabularies, their poorly-supported subscription services are a constant source of annoyance for those who must rely on them, and if they were really expecting to recover significant costs it’s probable that the group that supports that effort would be adequately staffed, which it isn’t. (This same lack of adequate support was the likely reason that the ALCTS continuing education workshops are now freely available, but that’s another story.) In short, we’ve seen little evidence that there are serious efforts to replace these outdated services with the web services that the Working Group and the library community have called for—except, of course, the late LCSH.info service.

    I’ll make the point again that I made to the Working Group in 2007—these are vocabularies that were not created solely by LC—particularly the Name Authority File (LCNAF) which has seen significant investment by the library community through the NACO Project (Name Authority Cooperative, please note), and the Series Authority File (LCSAF) now being built entirely by the community since LC unilaterally withdrew from the creation of series authorities in 2006. It was that decision, clearly made without adequate consultation with anyone outside LC (or many within—I happened to be visiting a colleague there a day or so after the announcement, and most of the staff were surprised, too), which resulted in the furor that led to the creation of the Working Group in the first place. But obviously, lessons were not learned from that debacle, and we’re back at the barricades, frustrated yet again.

    Contrast this with the recent post on the LC blog (posted on 12/11) announcing the report on the Flickr Pilot, one of the most innovative projects LC has done in a very, very long time. The report, ironically entitled “For the Common Good” (summary available) describes the overwhelmingly positive response to the project, and how LC used the information provided by viewers to enhance their information on the photographs. Most telling is this snippet from the report on the project taken from the LC staff newsletter and included in the blog post:

    “The popularity and impact of the pilot have been remarkable,” said Michelle Springer, project manager for digital initiatives in the Office of Strategic Initiatives, who said total views reached 10 million in October. The site is averaging 500,000 views a month, she said, adding that Flickr members have marked 79 percent of the photos as “favorites.”

    “The report recommends that the Library of Congress continue to participate in The Commons and explore other Web 2.0 communities.”

    Clearly by “other Web 2.0 communities” the writer could not mean the library community, which has been stymied for far too long by LC’s reluctant and too often less-than-competent leadership, and are still some distance from being a “Web 2.0 community.”

    What we see here is an institution with no coherent strategy for moving forward, despite a year long study of the issues, and clear recommendations for action. This is an institution where decisions are still being made by one hand that the other hand may not know about or have been consulted about—decisions that are ill-considered and fray LC’s credibility and its relationship with the rest of the library community (not to mention the Semantic Web community). This decision may well draw attention away from the other supposed library leadership institution—OCLC—caught making its own self-serving decisions without reference to its members real needs and interests, though members pay for the records that make the monopoly possible.

    As the New Year fast approaches, perhaps we need a resolution that says: “Stop expecting the 8000 lb. Gorillas to lead us; start leading ourselves.”

    [1] Jenn Riley
    [2] Tim Spalding
    [3] Karen Coyle
    [4] Andy Powell
    [5] David Bigwood [Corrected]
    [6] Richard Wallis
    [7] Dan Chudnov

  • Hearing Voices

    As I mentioned in my first blog post, I’ve been doing a regular column for Technicalities, entitled “View from a Parallel Universe” for the past couple of years. It’s been useful, and I’ve enjoyed it, but clearly the kinds of things I like to talk about need, um, a less leisurely publication schedule (I just received the Sept./Oct. Issue, including a column I wrote over the summer). I’ve generally put my columns up on Cornell’s eCommons IR soon after I submit them, primarily to avoid forgetting that last step. Anyway, once it goes on eCommons it gets indexed and people find it, then sometimes blog about what I’ve said. I’ve tried to wait until the piece comes out in print to say anything about it myself, but as the publisher is again pretty seriously behind, and I’ve sent in my resignation as a columnist, it’s time to roll my eyes and give up the illusion that it’s not “out” yet.

    As Karen Schneider pointed out on Free Range Librarian, my last column (entitled “Getting There”), includes some concerns I have about how OCLC’s new record reuse policy, coupled with their silence about plans to implement RDA, constitute an additional risk for libraries planning to implement RDA. It’s best read after reading the various blog posts about the policy, especially Karen’s, a gold star of a blog post indeed.

    I think we’ve been seriously let down by the institutions that we’ve relied upon to lead us, provide services to enable us to share information and increase the efficiency and usefulness of our individual efforts. I don’t think most of us have fully internalized this yet; we still expect these institutions to live up to their ideals, be exemplary community members, and use the brainpower of their staffs to chart a course that we can understand, respect and rely on. We’ve tended to be far too passive about this, in my opinion, and the chickens are coming home to roost.

    Unlike some others who’ve noticed that the changes in our technology environment have been leading inexorably to serious strains in the cooperative sharing environment built up over the decades, I’m feeling moderately optimistic. The worst thing we could do is cling unthinkingly to the comfort and warmth of the familiar, and not look clear-eyed into the issues emerging from these strains and changes. I don’t think we’ll ever again be as tightly coupled as we were when we only shared information amongst ourselves and we looked for efficiencies in our own workflows to keep us viable within our own institutions.

    Looking ahead, we’ll have to be more actively involved in looking for solutions to our problems instead of sitting back and waiting for someone else to come up with them so we can continue to be followers. We’re seeing some of that happening already, as new players develop open source software, push for open linked data solutions, forge connections with the Semantic Web communities, etc.

    Let your voices be heard on these issues.

  • Show me the data!

    Maybe it’s just me, but I like to be able to look at data “in the raw,” without some developer deciding for me what I’m allowed to see, and how I’m allowed to see it. There was an old story I used to tell about visiting a vendor booth at ALA Exhibits some years ago, where a marketing guy got me extremely irritated by not getting why I wanted to see a naked MARC version of some record he was using to illustrate a point he was trying to make. The punch line of the story was that I would characterize his reaction to the request as making me feel like I’d asked to see child pornography. The line always got a laugh, particularly in highly geeky librarian circles (which meant something quite different 10 or 15 years ago, but never mind).

    The point was, of course, that in order to evaluate what a system was doing with your data, you had to be able to look at the underlying data, and follow it through whatever process was in place to manipulate or use it in some way. Of course, “naked MARC data” really meant “scantily clad MARC data,” because few of us really spent much time with unformatted MARC, in whatever flavor our system used, though I remember on many occasions being shown marked up printouts of NOTIS EBCDIC, and working with a programmer to figure out what was wrong and how to fix it.

    I was reminded of this when hearing a developer (who shall remain nameless) say recently that “of course you’d never show anyone the FRBR structure” in an RDA based system. “Why the hell not?,” I responded (though perhaps the response was in my head and I was actually more polite—reports vary). There was a condescension in that comment that made me bristle, and I remembered the stories of why the early BALLOTS system (which I used for a mercifully short time) didn’t use MARC tags. The icky mnemonics that BALLOTS substituted were there because some genius decided that librarians (mostly women, of course) would never be comfortable with numeric tags. I don’t know whether the story is true, but it sure fits with the sexist attitudes of the time.

    It’s a bit depressing that this sort of thing keeps coming up. Now that I’m older and even crankier than I was when I first encountered this attitude, I have even less patience with the idea that I might want to be protected from angle brackets, namespaces and whatever it is that is the is the special purview of the people who program. Show me the data—I can handle it.

    [Disclaimer–this isn’t about you Jon!]

  • At NELINET on Friday …

    Yesterday I did a long program for NELINET, entitled “Trepidation or Anticipation?: The Future of Cataloging and Catalogers.” This topic has been a theme of mine for some time, and I’d been invited to do this program after doing a similar, though shorter, one at the Massachusetts Library Association in the spring. The response to the initial announcement was gratifyingly strong, and we ended up with an audience of about 55, including one logged in from Missouri.

    I admit to coming into these sessions with an expectation that I’m going to have to win over people to the “anticipation” side of things—I suppose some of that derives from the skepticism I still hear online (a few loud voices predominating, I will admit). The group was quick to reassure me that they weren’t by any means as resistant to the changes washing over us as I had anticipated—they “got it,” were ready to hear what they had to do to make it happen. They were a great audience, asked good questions and listened to the answers, then asked some more questions. But I’m going to have to change my approach somewhat, I can see that.

    I was interested to hear from one participant that it was the reference librarians in her shop who were the most resistant to change. Every time something new was added to the catalog, be it book jackets, tags or reviews, the front desk folks wanted it eliminated—deemed it “confusing.” I’d never heard this, and questioned her after the session—did she think this was an anomaly in her library or more a wide spread phenomenon? She didn’t know, but noted that it was generally those who’d been around the longest who were the most resistant. As someone having a birthday ending in a zero in a few weeks, I wasn’t happy to hear that (though sadly not surprised).

    One of the participants questioned me about Heidi Hoermann’s presentation to the OLAC/MOUG Conference in Cleveland this past September. This presentation, which predicted the death of RDA and the rebirth of AACR2, took the lists and the library blogosphere by storm when it first hit Slideshare. Though I’ve also criticized the JSC publicly myself, and don’t necessarily disagree with many of Heidi’s points, I think she’s way off base concluding that because of the acknowledged flaws, RDA is dead. I find it disturbing that someone who’s teaching the next generation of librarians has so thoroughly missed some of the important work going on around RDA (particularly the work of the DCMI/RDA Task Group, which I’m co-leading), and then focuses primarily on the failings of the JSC process in concluding that RDA is dead. I admit to occasionally getting far too adamant when commenting on this particular point of view, but it disturbs me greatly.

    I’m wondering if this change I’m starting to see—from trepidation to anticipation—has implications for how we think about training catalogers for RDA. I’m quite sure that, before we train, we need to prepare catalogers for the training itself by giving them a more general introduction to what has changed about their mission. I’m finding that as I do these presentations, I’m starting to see what works, and what doesn’t. I’ll try to keep posting on this because I think it’s critically important that we not make too many simple assumptions about how this training ought to proceed, and miss the boat entirely.

  • Daniel Pitti on the EA*

    One of the nice things about being “retired” (even practice “retirement”) is that I get to work at home most of the time. There are few things that lure me to the Cornell campus these days—lunch with friends, maybe a lecture now and then—but I almost always go to the forums of the CUL Metadata Working Group. These started a few years ago and have been a godsend, both for those of us who have something to say (I’ve presented multiple times) and those of us who have something to learn (all of us). Like most such efforts, there’s some overhead in the form of a committee that schedules speakers, manages a small budget, etc., but the result is well worth it. Marketing efforts for the forums extend well past the library and often bring audiences from the campus IT organization, the computer and information science folks, and other orphans lodged in various departmental digital efforts.

    This month the speaker was Daniel Pitti, Associate Director of the Institute for Advanced Technology in the Humanities at the University of Virginia. I’ve known Daniel since the first Dublin Core meeting in 1995 (when he was working at Berkeley), so was not going to miss the opportunity to hear him talking about where archival description was headed.

    As advertised, Daniel gave some background about the EAD (Encoded Archival Description) as well as the EAC-CPF (Encoded Archival Context – corporate bodies, persons, and families). EAD is based on the the traditional archival finding aid, and focuses on the provenance-based description of archival resources where all records by a single created are treated as one unit. After setting the stage, Daniel spoke about the design of “post- finding aid” archival description systems, describing both the environment within which archival description is created and maintained and the possible published forms of the description that can be searched, rendered, and enhanced by users. I was interested, and pleased, to note that work on this post- finding aid world is based very much on a future I recognize, with a vision based both on what’s happening in libraries as well as what’s going on in the archival community. In a world where tectonic shifts are occurring in both areas, and the focus of library missions are shifting visibly towards the primary materials living in archival collections, this is a VERY GOOD THING.

    One of the interesting themes of Daniel’s presentation was “re-imagining description and access.” Librarians may notice the similarity to RDA: Resource Description and Access, and I suspect this is not an accidental echo. The analysis that he described, and the direction that archival description seems to be headed, bodes well for both archivists and librarians—I came away with hope that the trajectory of both efforts will result in the ability for descriptions created by either to be available to users without the necessity of the kind of mediation now required. Not without blood and angst, but perhaps within our lifetimes!

    Daniel also described the EAC-CPF, intended to provide a formal method for recording the description of record creators. I asked how this work correlated with similar efforts going on in libraries—FRAD, for instance. Daniel suggested that the inter-community dialog ought to start happening at this level, with the description of people. The first step in this has already happened, of course, with the inclusion of “Families” in RDA—a direct steal from archival description–but there are many steps yet to be taken.

    With RDA and the wonderful possibilities for bringing the archival and library communities closer together swirling in my mind, I was struck by one of Daniel’s final points, where he noted that the community was now thinking of a two-pronged approach to the post- finding aid world: permissive on the whole but with less permissive possibilities, which would tend over time to move things forward. This is surely an approach that has been discussed in the RDA world, but not yet well articulated, in my view.

    Daniel’s presentation is available on the CUL Metadata Working Group space on Cornell’s eCommons.