Month: May 2009

  • Testing! Testing?

    Today I got a very disappointing note in my inbox, from the US National Libraries RDA Test Project. I guess I’d call it a “ding” letter, and I have to say it was more than a bit surprising. I had volunteered to help with the testing, not by creating records, mind you, but in analyzing the records other people create. Given the fact that I’ve been the co-chair of the DCMI/RDA Task Group, done the major part of the work in registering the RDA schemas and vocabularies, and have been involved in building the XML schemas that will be the basis of much of the data creation for many early RDA implementations, I figured my experience might come in handy. But apparently not …

    Dear Diane: Thank you for your interest in the US National Libraries RDA Test project. The RDA Test Steering Committee regrets that you could not be selected as a formal test participant. Interest in the project was much greater than the Steering Committee originally anticipated, and it was necessary to select test partners from more than 90 applications. Every applicant had a great deal to offer to the project, and each was carefully considered. The Steering Committee based its final selections on the goal of ensuring that the RDA Test will reflect a cross-section of US cataloging agencies balanced by size, type of organization, OPAC and cataloging systems used, and areas of specialization in cataloging and collection development.

    The Steering Committee will share the methodology for the test on its Website at URL . If you are interested in conducting your own test of RDA, we encourage you to produce records following this methodology and to share the results with the Steering Committee during the test period.

    Thank you again for your interest in the RDA Test.

    So, exactly what are they testing that makes my knowledge and experience useless? Darned if I know. But I can’t get beyond the notion that the testing regime I see described on the website is pretty limited, and it’s hard to imagine what the results can really tell us, aside from the obvious difficulties people will encounter in attempting to cram a FRBR-based structure into any one of our current flat MARC-based library systems.

    Much more interesting, to me anyway, is the idea of what RDA records might look like in straight XML or RDF, without the necessity of the contortions involved in making it all “fit” into a MARC system. Without the layer of MARC contortion we might really be able to figure out whether catalogers could adjust to RDA and create FRBR-based records. It would be nice to think that some of the open source systems would find a way to play with these records and test some more forward-looking, rather than backward-looking implementation issues.

    Any volunteers for an alternate testing regime?

  • LCSH, SKOS and pre-coordinated headings

    This week, Karen Coyle wrote a post about LCSH as linked data: beyond “dash-dash” which provoked a discussion on the id.loc.gov discussion list.

    It seems to me that there are several memes at play in this conversation:

    LCSH and SKOS

    As Karen points out, LCSH is more than just a simple thesaurus. It’s also a set of instructions for building structured strings in a way that’s highly meaningful for ordering physical cards in a physical catalog. In addition, each string component has specific semantics related to its position in the string, so it’s possible, if everyone knows and agrees on the rules, to parse the string and derive the semantics of each individual component. The result is a pre-coordinated index string.

    These stand-alone pre-coordinated strings are perhaps much less meaningful in the context of LOD, but this certainly doesn’t apply to the components. I think what Karen is pointing out is that, while it’s wonderful to have a subset of all of the components that can be used to construct LC Subject Headings published as LOD, there’s enough missing information to reduce the overall value. As I read it, she’s wishing for the missing semantics to be published as part of the LCSH linked data, and hoping that LC doesn’t rest on its well-earned laurels and call it a day.

    Structured Strings

    Dublin Core calls the rules that define a structured string a "Syntax Encoding Scheme" (SES) and basically, that’s what the rules defining the construction of LC Subject Headings seem to be. It’s structurally no different than saying that the string "05/10/09", if interpreted as a date using an encoding scheme/mask of "mm/dd/yy", ‘means’ day 10 in the month May in the year 2009 using the Gregorian calendar. Fascinatingly, that same ‘date’ can be expressed as a Julian date of "2454962", but I digress.

    As far as I can tell, no one has figured out a universally accepted (or any) way to define the semantic structure of a SES in a way that can be used by common semantic inference engines, and I don’t think that anyone in this discussion is asking for that. What’s needed is a way to say "Here’s a pre-coordinated string expressed as a skos:prefLabel, it has an identity, and here are it’s semantic components."

    Additional data

    So…

    "Italy--History--1492-1559--Fiction"

    …is expressed in http://id.loc.gov/authorities/sh2008115565#concept as…

    @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
    @prefix skos: <http://www.w3.org/2004/02/skos/core#> .  
    @prefix terms: <http://purl.org/dc/terms/> .  
    @prefix owl: <http://www.w3.org/2002/07/owl#> .
    
    <http://id.loc.gov/authorities/sh2008115565#concept>
        skos:prefLabel "Italy--History--1492-1559--Fiction"@en ; 
        rdf:type ns0:Concept ;    
        terms:modified "2008-03-15T08:10:27-04:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> ; 
        terms:created "2008-03-14T00:00:00-04:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> ; 
        owl:sameAs <info:lc/authorities/sh2008115565> ; 
        skos:inScheme
            <http://id.loc.gov/authorities#geographicNames> , 
            <http://id.loc.gov/authorities#conceptScheme> ; 
        terms:source "Work cat.: The family, 2001"@en . 

    …and has a 151 field expressed in the authority file as…

    151 __* |a *Italy* |x *History* |y *1492-1559* |v *Fiction

    …which has the additional minimal semantics of…

    <http://id.loc.gov/authorities/sh2008115565#concept>
        loc_id:type "Geographic Name" ; #note that this is also expressed as a skos:inScheme property
        loc_id:topicalDivision "History" ;
        loc_id:chronologicalSubdivision "1492-1559" ;
        loc_id:formSubdivision "Fiction" ;
        loc_id:geographicName "Italy" .

    …and this might also be expressed as…

    <http://id.loc.gov/authorities/sh2008115565#concept>
       loc_id:type http://id.loc.gov/authorities/sh2002011429 ;
       loc_id:topicalDivision http://id.loc.gov/authorities/sh85061212 ;
       loc_id:formSubdivision http://id.loc.gov/authorities/sh85048050 ;
       loc_id:geographicName http://id.loc.gov/authorities/n79021783 ;
       dc:temporal "1492-1559" ;
       dc:spatial http://sws.geonames.org/3175395/ ;
       dc:spatial http://id.loc.gov/authorities/n79021783 .

    Making sure that those strings in the first example are expressed as resource identifiers is also something that I think Karen is asking for. (BTW, The ability to lookup a label by URL at id.loc.gov is really useful)

    I should point out that Ed, Antoine, Clay, and Dan’s DC2008 paper detailing the conversion of LCSH to SKOS goes into some detail (see section 2.7) about the LCSH to SKOS mapping, but doesn’t directly address the issue that Karen is raising about mapping the explicit semantics of the subfields.

  • Ready for change

    Friday I was in Hyde Park, NY, at the site of the Franklin D. Roosevelt Presidential Library and Museum, attending the NYLINK Annual Meeting. I’d been asked to come and talk about change in cataloging. NYLINK, formerly the SUNY/OCLC Network, is one of the struggling regional service providers that used to be the primary brokers for OCLC services for smaller libraries, and did most of the training for OCLC in the process. These organizations are now providing other kinds of services and training for a wide variety of libraries, and are still one of the best places for figuring out what working librarians are thinking.

    I was particularly impressed with how this day-long meeting was organized. After the welcome and logistics, two speakers—Liz Chabot from Ithaca College and Susan Currie from Binghamton University—got things off with a bang by proposing seven “what ifs”:

    … we stopped cataloging?
    … librarians individually and as a profession promoted, used and helped develop Wikipedia?
    … we accepted open source software as a way of being in control of the customer experience?
    … we required all library staff to have expertise using technology?
    … mistakes were expected and embraced—and librarians became the mistake masters?
    … we didn’t make our customers work so hard?
    … we let customers determine their loan periods?

    Meeting participants spent some time talking about these questions, in the meantime getting to know one another at their tables, and getting fired up about the topics. The morning speaker, Joe Lucia from Villanova University, then started off with this energized group, and did a great job putting the important issues in a more general perspective. He spoke compellingly about our plight in libraries and the parallels with newspapers, described changes in how people deal with linear text vs. Hypertext, and pointed out the work of R. David Lankes (a colleague of mine at Syracuse University), who talks about the “library as conversation.” Joe’s primary point in bringing together these threads is his contention that libraries are not in the “information” business so much as we are in the “knowledge and conversation” business. He talked very passionately about the library as a “commons” where knowledge and conversation happen with the active engagement of the library as organization, bringing students, faculty and others out into the open for exchanges of ideas, not just providing places for their solitary study.

    But of course it will be no surprise that I was most engaged with the question “What if we stopped cataloging?” I’m not sure that question is the right one, or perhaps just not specific enough. I might recast it as “What if we stopped cataloging the same old stuff?” By “same old stuff” I mean the secondary products of academic pursuits: books, journals, government documents, etc., the stuff that we have always cataloged. What if we began to catalog different stuff, the stuff we’re publishing ourselves, the podcasts we create of the talks given by our own faculty and those who visit us to discuss their research, the exhibitions we create out of our collections and materials borrowed from others, the primary materials our former faculty members have donated into our care—the things that we’ve always consigned to others (archivists, perhaps?) or not cataloged at all. What we have called cataloging, when it is not done for the first time, is these days for the most part consigned to staff who may not be catalogers, bought from vendors, or automatically claimed from larger databases to populate ours. Insofar as we have used these more efficient, more automated strategies, we have indeed “stopped cataloging.” What we haven’t done is modified our missions and our budgets to take more responsibility for these other often unique things that we have neglected, and as such we have been the instruments of our own demise.

    So as we hear the bemoaning of the profession of cataloging, and ourselves sometimes obsess about the “how” of the changes in our lives brought on by technology, financial distress, and various other pressures, we would do well to remember that behind all this, the mission of the institutions we call home is changing significantly, and we can’t answer those “how” questions without looking anew at those shifting missions.

    My presentation and Corey Harper’s came after lunch, and the group was exceptionally ready to hear what we had to say, thanks to the fabulous preparation provided by NYLINK, Joe Lucia, Liz Chabot and Susan Currie. I had some great conversations there, and on the ride home thought quite a bit about how proud I am to be a librarian, and the wonderful opportunities I continue to have to get to know some of the best people in the business.

  • On the Road at NJLA and the Five Colleges

    This week I’ve been on the road, doing presentations at the New Jersey Library Association meetings on Wednesday, and Five Colleges in Western MA Friday morning. I’ve been doing all this travel in the faithful MetadataMobile, increasingly an object of interest, amusement and (almost) veneration by those who have heard about her. It’s been a great trip, with wonderful audiences, and as always, I learn a lot about what’s on the minds of those in the trenches.

    I arrived later than I’d expected at NJLA, due to missing the exit I was supposed to use on the Garden State Parkway. I was very busy looking for a coffee and a rest stop, and it probably whizzed right by me. By the time I realized I was way too far down the Parkway, I decided to get off and use my newly acquired New Jersey Official Map to get me to my destination. I know, it’s very retro as a strategy, but maybe I was feeling that a little self-punishment was in order, or maybe I just needed to get off the big roads for a while.

    As a child of the fifties, my first stop was a gas station as I needed to gas up and figured I’d confirm my location on my handy-dandy map and get some advice on my route. I had forgotten that New Jersey doesn’t do self-service gas pumping, and I’d also forgotten that virtually all the NJ gas stations I’ve visited in the past decade are staffed by (and possibly owned by) persons from somewhere else. When shown a map and asked for directions, they invariably act like people who have been lately dropped into their current location from the sky with no idea how to locate themselves in the world they inhabit (pretty close to reality, probably). I knew pretty much where I was, but wanted to figure out how to get to a big secondary East/West road that would take me to where I needed to be. It was hopeless—these guys (they’re always guys) couldn’t even locate the town they were in on my map so I thanked them for their trouble and got back on the road. I ended up following my nose (and the MM’s internal compass, which tells me whether I’m going N, S, E, W or any rational combination thereof). Thankfully, in NJ if you go east you find the Atlantic eventually.

    It was a gorgeous day to be taking the long way, and I passed by what remains of the agricultural areas in NJ, including a whole bunch of horse farms (one was called “Due Process Stables” and you could pretty much guess how that was funded). I got to the conference venue in Long Branch (right on the beach) in time to take a nice walk on the boardwalk and decompress from those long hours behind the wheel.

    The program was about FRBR and RDA for real people, and Rhonda Marker from Rutgers presented first. Rhonda and I have presented together before, and generally have fun with it, since we sometimes disagree and are very open about it, to the general amusement (or maybe consternation) of the audience. We only had two hours, which wasn’t enough, but the audience was very receptive and had some good questions. The slides for this presentation are available here.

    From Long Branch, NJ, I pointed the MetadataMobile north, through the horror of Big Apple driving (BIG trucks!), though Connecticut and up to Amherst, Mass., for a confab with a group from the Five Colleges. This had been in the planning works for some months, but was made more interesting by the announcement a few weeks ago of some pending reorganization of technical services operations in the colleges in response to the same kinds of financial pressures being experienced everywhere. I’d been forewarned about this by the organizers of this session, and included some of the issues most relevant to the group in my presentation (though the slides, available here don’t always reflect this directly). My underlying point was that they were not, in fact, dealing with only one crisis—the financial meltdown—but two, if you include (as I do) the pending changes in how we do business as data creators and managers, changes that are absolutely necessary to avoid the continuing marginalization of our efforts to provide information to our users.

    One thing that impressed me about this group was that it included a number of the library chiefs, systems folks and others not part of the cataloging cohort that normally predominates in my audiences. This is good—very good, in fact—because it signals to me that the issues I talk about are being seen as crucial to the discussions around a change in mission and strategy essential to creating positive change over the longer term, not just arguing against cuts in budgets for the short term. But, like President Obama points out, the one-crisis-at-a-time approach doesn’t work in a context of multiple crises related to one another in fundamental ways. Attempting the financially necessary reorganization without a refocus on mission, in the face of the huge challenges we face in remaining relevant in the current information environment, is self-defeating at best, suicidal at worst. I spoke to one of the chiefs after the presentation, and he said that he wished his public services folks had been there, too, and I agreed. Certainly the demise of the library catalog as we know it will affect their work hugely, and it behooves us all to break down those barriers of specialization as we face issues of our own survival as information providers.

    What this also suggests is that the focus of the testing being done by the US national libraries cannot be limited to cost benefit analysis. If we fail to look at the issues of most importance to libraries, as the LC Working Group on the Future of Bibliographic Control certainly did, we risk our future entirely. Of course, in the current environment particularly, we need to pay attention to costs and efficiency as we move forward, but they cannot be our sole criteria for decision making.

    For those of you knitters among my readers, I also made a pilgrimage to Webs and spent a goodly portion of my speaker’s fees to support the local economy. It was a great, though at this point I’m going to have to do a “real” retirement sooner than anticipated to use up all the accumulated yarn and patterns I’ve amassed. Either that or recruit a chauffeur on these trips so I can knit on the way.