Category: Futures

  • Onward!

    One of the things Jon and I still talk about (despite our putative retirement), is how to pass on to the newer generation what we’ve learned over our years working in the vocabulary, data maintenance and data aggregation spaces. Of course, we’ve written or co–written quite a few papers and articles, and most continue to be read and cited (or so ResearchGate tells me), and as well we have significant numbers of presentations and slides available freely.

    Jon sometimes tries to convince me that in the age of AI and waning interest in metadata and vocabularies, particularly in non-library research venues, our time of relevance has passed. He may be right in some respects, but I’m not convinced that’s true in libraries. And the Open Metadata Registry, still alive and quietly kicking, is still being used by an interesting variety of vocabulary nerds. I checked today and noted that there’s a NASA Name Authority vocabulary still in active development as of last week (I haven’t checked to see whether the developers have been active during the partial government shutdown or not).

    Recently, I worked on the NISO effort to describe the state of the vocabulary world and one of our main discoveries was how few of the tools developed over the past few years are still functioning. Most were developed using research funding, notoriously time limited (one or two years is common). What’s left is an array of commercial products (difficult to determine how effective they are, though they’re certainly costly), and the OMR, which we’ve been supporting since our NSF funding dried up in 2008. We had funding from ALA Publishing for some of that time, and we’re still working on a beta version of the OMR.

    We’d like to find out whether there’s any interest out there in figuring out what can be done, in the non-commercial realm, to determine what the needs are–in libraries particularly, but also in other institutions–for continuing a service like the OMR, and what might be strategies to continue it (or something similar) into the next decade or so.

    Ultimately an important question is whether formal RDF vocabulary management matters in a data world dominated by Machine Learning, fragmented by the low bar set for publishing ‘Linked Data’ and the ongoing ‘format wars’ in the library community. Vocabularies matter when definitions are clearly expressed and mechanisms are provided to align heterogeneous metadata across divergent datasets. Definitions and alignments have to be maintained over time — all data has a lifespan of utility. Too often data is released into the wild of the internet without any thought to how it will be consumed and how it will be maintained. Ongoing vocabulary maintenance is crucial to future-proofing public datasets. Or is it all just too hard, given the pressures of funding and the more immediate worry of whether you’ll still have a job next week?

    Given the burgeoning of podcasts on anything and everything, we’ve considered whether that might be a way to get some interesting conversations going (maybe even interviews, which are my favorite kind to listen to). Or we might just up the effort to continue blogging (thus cementing our reputation for persistence!) Do mention some topics that interest you, whether for the blog or (possibly) a podcast. Comments welcome in the comment section of this blog, or on Twitter, at @Metadata_Maven or @jonphipps.

    Discuss!

  • Whither CC:DA?

    Back in the old days (Feb. 2014, to be exact), I published a blog post entitled: “Wake Up Call for CC:DA”, written during an excruciating conversation at the tail end of a CC:DA meeting at Midwinter 2014. As part of that I recommended that CC:DA change its focus:

    “What we need here is to change the conversation, and no group is more qualified to do that than CC:DA. To do that it’s absolutely necessary that its membership become more knowledgeable about what is now possible in automating metadata creation. Without that kind of awareness, it’s impossible to start thinking and discussing how to focus less of CC:DA’s efforts on that part of the cataloging process which should be done by machines, and more on what still needs humans to accomplish. There are several ways to do this. One is by dedicating some of CC:DA’s conference time to bringing in those folks who understand the technology issues to demonstrate, discuss, and collaborate.”

    There were no comments to that post (not much of a surprise), but in the years since, change has been forced on CC:DA as a result of the RSC’s push to change RDA from the Anglo-American focus of the past to one more international and multilingual. This has changed CC:DA’s status from the 800 lb. gorilla whose discussions went directly into the ears of the RSC (then the JSC) to a cranky corner of the RDA peanut gallery. The Europeans, many of whom are actually using RDA, have taken center stage, leaving the Americans to cope (or not) with BibFrame (characterized by some across the pond as just another remnant of America’s colonial aspirations).

    Like most change, that’s the bad news and the good news, depending on your point of view. Mine (again no surprise) is that this shift is the good news, or will be when the CC:DA community decides to make it so. IMO, the usual CC:DA conversation, most often focused on the ‘rules’, has resulted in keeping back the American discussions of what the future looks like for the metadata community. Europe is far ahead of us, having been relatively powerless to change the guidelines, and has instead been focused on learning more about the data models they need to know about to evaluate what they do now and how that needs to change. There has been far more experimentation and implementation in Europe than we’ve managed in the U.S. (the BF distraction is part of that) and as they have developed much more sophistication in their thinking.

    So what should we do to change that? Some possibilities:

    1. Start talking about what metadata should or could be for our present and future, whether creation, evaluation, distribution or improvement. Figure out what we know and don’t know and how we can learn what’s going on in the metadata world outside libraries and how we can apply that knowledge in libraries.

    2. Set up a working group or committee to take that discussion and develop a curriculum for CC:DA with the intention of building up skills and understanding to spread around, within and beyond CC:DA, as well as throughout the cataloging community (which desperately needs leadership in this area).

    3.Determine who within ALA and allied organizations can participate and assist, by preparing reading lists, developing and/or linking to existing materials, and leading discussions (both f2f and online). Eventually we’ll need to set up a variety of strategies for supporting and expanding these opportunities.

    This is clearly not part of the current remit of CC:DA, and the budget does not yet exist for this kind of effort. Clearly there will need to be partnerships and allies for an effort like this, but we’re already behind, so let’s get started.

    [I plan to make a proposal to CC:DA to start talking about this, so watch this space.]

  • The Vocabulary Management Mess

    Announcement: The vocabulary management mess needs your attention.

    In 2013 I wrote a couple of posts critical of some updating practices LC was using in its id.loc.gov services. The first post focused on the relators vocabulary, and how change was handled within that vocabulary.

    The follow-up post dealt with the unacknowledged gaps in the LCSH service on id.loc.gov.

    So, here we are almost three years later, and not much has changed. I went back through the examples in pt. 1, and the issues pointed out there are still exactly as noted three years ago. For those three years there have been many discussions about linked open data, but the vocabulary infrastructure needed to support LOD is still largely not ready for prime time.

    And it’s not as if nobody’s been thinking about solutions. We wrote a paper about how versioning management ought to work in vocabulary services, but it seems to have been overlooked by even the large established services. It’s hard to avoid the conclusion that there just hasn’t been much recognition of the problem we were trying to solve. Trust me, it’s a real problem, and a very big one at that. It’s not just local, or attached to one institution–we’re talking about an international problem, one that could delay the uptake of linked data far longer than we’d like.

    For users of vocabularies, the absence of vocabulary services (aside from simple lookup and basic file download) are a large impediment to the actual use of LOD. How does a creator of bibliographic data–who we’ve been encouraging to use vocabularies–actually use those vocabularies to manage their overall data needs over time? By downloading files and examining diffs every week (month, quarter, year)? Remember when we had to cruise websites to find out when a new software update was available? We’re at that stage right now in vocabulary management, and not making progress towards a service environment that will actually support the use of vocabularies in data.

    To think about ‘how big’ the problem is, consider how many vocabularies occur regularly in instance data: ISBD, FRBRer, RDA, schema.org, DC Terms, etc. When terms in those vocabularies change, how do those managers of instance data know what has changed? Should they be expected to just leave the old data as is, or send it to the cleaners every year or so? Proper vocabulary management practices can be a big part of the answer–the machine-assisted answer.

    So, what’s to be done?

    Just about 10 years ago, LC initiated a Working Group on the Future of Bibliographic Control, complete with blue ribbon membership and a broad remit to look around and suggest a path for re-imagining what they and other libraries were facing as they worked towards a different future. Full day hearings were held in three locations across the US and these events drew so much interest that the streaming capabilities set up for the sessions were overwhelmed. I testified at one of those hearings, and–I’m sure you’re surprised–spoke about the value of vocabularies in this brave new world.

    But the amazing thing was the level of interest and engagement of the library community in the issues discussed by the WG. I’m not sure I’ve ever seen anything like it, before or since. For a while there, every time I was asked to present at a meeting, the WG report was the desired topic. Literally everyone was talking about it–the community clearly recognized the importance of the effort and wanted to be part of it.

    We definitely need something like that again–a place to bring together the community and its experts, to state the problems and brainstorm the solutions. Let’s call it a ‘Library Vocabulary Summit’, for the moment, and roll the possibilities around in our heads. We’d need funding, leadership, and marketing to make it happen. Let’s ALL talk! (Preferably around a large table, face to face, with a relevant agenda).

  • Why Do We Undervalue Maintenance?

    I ran across a really interesting article last week, and the points it makes have been rocketing around my head as I consider what’s broken (and why) in the small world many of us live in, not to mention how we can fix those broken things. I’d really recommend taking a look at it: “Hail the maintainers: Capitalism excels at innovation but is failing at maintenance, and for most lives it is maintenance that matters more”, by Lee Vinsel & Andrew Russell.

    The gist of the authors’ point–that we overvalue innovation and undervalue the maintenance of our existing technologies–is one that ought to resonate particularly with librarians, especially those of us who have toiled in the world of catalogs and the maintenance of same.

    “The most unappreciated and undervalued forms of technological labour are also the most ordinary: those who repair and maintain technologies that already exist, that were ‘innovated’ long ago. This shift in emphasis involves focusing on the constant processes of entropy and un-doing – which the media scholar Steven Jackson calls ‘broken world thinking’ – and the work we do to slow or halt them, rather than on the introduction of novel things.”

    One of the things that struck me in this article was the connection the authors made between ‘innovation’–associated with high tech activities primarily seen as the male domain, and ‘maintenance’, the ‘women’s work’ of the age of technology.

    “We can think of labour that goes into maintenance and repair as the work of the maintainers, those individuals whose work keeps ordinary existence going rather than introducing novel things. Brief reflection demonstrates that the vast majority of human labour, from laundry and trash removal to janitorial work and food preparation, is of this type: upkeep. This realisation has significant implications for gender relations in and around technology. Feminist theorists have long argued that obsessions with technological novelty obscures all of the labour, including housework, that women, disproportionately, do to keep life on track.”

    The authors make the point that these skewed values resonate throughout our society. Notice how boring most people consider the maintenance of our physical infrastructure–roads, bridges, pipelines, etc. Of course, most of us agree that there needs to be more of it, and more resources aimed in that direction, but ho hum, talk about it in any detail? Not on your life.

    For those of us considering the data infrastructure to support the rebuilding and expansion of the data sharing that libraries have done for many decades, we see the same thing. The Open Metadata Registry (OMR to those of us who prefer to speak in acronyms), now too often dismissed as ‘old technology’, is a case in point. Back in 2004 when we received funding from the National Science Foundation, there weren’t many people thinking about data ‘infrastructure’–particularly for vocabulary data, but we were. Back in the day, we often talked about the OMR in the context of the plumbing beneath sidewalks and buildings. Few of us who are not plumbers think about plumbing — we all assume that it’s there, but is rarely a topic in non-plumber gatherings until something critical breaks, or a community is systematically poisoned.

    And even plumbers innovate, in ways that few of us understand, much less think about. The water debacle in Flint, Mich. has brought up the problems of old pipes, but not many discussions go beyond that. In the world of vocabulary management, the OMR has been building and maintaining vocabularies for well over a decade now, and we know a lot about it. In particular we know where improvements should be made, and how OMR services can best support the activities needed by the folks building instance data. We’re also thinking about how to better sustain the effort over time.

    But the OMR was built to work within an environment where there are many such services, supporting other communities looking at the same changes ahead that we see in the library data environment. For lots of reasons, that array of services hasn’t come about, though we see activity in the structural metadata world–new formats, old formats morphing, etc.–effort almost entirely devoted to semantic churning, not services. Much effort is being put into creating and publishing Linked Open Data, but very little consideration is being given to how that data will need to change over time and how the entire plumbing infrastructure of publishing and consuming that data must support the need for ongoing maintenance of both the data and the public and private vocabularies that describe that data.

    [This is the first of two posts, the second proposing some ways to move forward]

  • Why You Should Come to the Jane-athon

    I know many of you are puzzled by this event, so do take a look at a rundown of the plans on the RDA Toolkit Blog.

    Not so surprisingly, we were inspired by the notion of a hackathon, but it had to be focused on something other than computer code and application building. All of us have heard conflicting opinions about whether RDA can be fully functional, whether FRBR works and will benefit users, or whether it’s just all too complicated. The big gap in addressing these questions has been the challenge in doing something hands-on instead of the usual sage-on-the-stage doling out large piles of handouts. There are still realities that need to be recognized, as we take a hands-on look at RDA and build some real RDA data.

    First of these realities is that RDA has been in development for a hell of a long time, and the rules (the part that gets the most attention, and some think really IS the whole of RDA) started out as AACR3. As one who’s been watching this space (from the outside and the inside) since the beginning, I can confirm that the the notion of AACR3 is a historical artifact, nothing to do with what RDA has become.

    I’ve been ranting and railing for years (too many to count) that RDA must be more than rules. And it is–see the RDA Registry for evidence of that. This leads me to the second reality: all of us are learning as we go. The first iteration of the RDA Vocabularies, developed by the DCMI/RDA Task Group after a famous meeting in London in the Spring of 2007, were never published. The published version, much improved, was released early in 2013 along with the new RDA Registry. The learning-by-doing was happening in a lot of other standards-focused groups: IFLA and W3C for example. FRBR, an essential part of the RDA model, was evolving along with RDA, and that fact led to a couple of interesting compromises, still working themselves out.

    I can promise you that the Jane-athon will reflect all of those realities, and in addition build out the community familiar with the lessons yet to be learned. There won’t be any papering over of gaps, downplaying of issues, or anything like that. At the Jane-athon we will demonstrate that building real RDA records in the context of FRBR is not a future dream, it’s happening now. What you will see as a participant is the reality–the ability to work within a FRBR flow, to import MARC records and see the system map them into FRBR constructs, to create links with NAF information, and view the results as a tree that highlights the relationships.

    Perhaps most important, we want to have fun with this. There will be no quizzes, no grades, no transcripts. That’s why we chose to focus on two sets of materials with great potential to benefit from a FRBR-based approach. Early in the day you’ll walk through the business of creating cataloging for Blade Runner resources (original book by Philip K. Dick), translations, film, etc. After that we’ll turn the group loose on Jane Austen (with some made-ahead basic data). After the flurry of data creation, we’ll be looking at the results, highlighting issues that come up, and not incidentally, getting some feedback from the participants about the tools, processes, and the beta-Jane-athon in its entirety.

    We know (and welcome the fact) that not everyone attending will be a cataloger, much less all that familiar with RDA. There will be a place and a role for everyone who wants to learn more, and to dig in and get their hands [virtually] dirty. There is no need to cram for this event, or to study the RDA rules or cataloging before you come. If you want to get a bit familiar with RIMMF before you come, by all means take a look at the site, download the software, and play. The only requirement is an open mind and some excitement about the possibilities (some trepidation is okay too).

    Once you have registered for ALA Midwinter in Chicago, you can sign up for the Jane-athon.The Jane-athon is already available as a paid addition of the full registration for ALA Midwinter in Chicago.

    Please feel free to use the comments portion of this post to ask questions, or use the RDA-L list to bring up questions and concerns.

    We hope to see you there!

  • Late to the party?

    In my post last week, I mentioned a paper that Gordon Dunsire, Jon Phipps and I had written for the IFLA Satellite Meeting in Paris last month “Linked Data in Libraries: Let’s make it happen!” (note the videos!). I wanted to talk about the paper and why we wrote it, but I’m not just going to summarize it–I wouldn’t want to spoil the paper for anyone!

    The paper, “Versioning Vocabularies in a Linked Data World”, was written in part because we’d seen far too many examples of vocabulary management and distribution that paid little or no attention to the necessity to maintain vocabularies over time and to make them available (over and over again, of course) to the data providers using them. It goes without saying that the vocabularies were expected to change over time, but in too many cases, vocabulary owners distributed changes in document form, or as files with new data embedded but no indication of what had changed, or worse: nothing.

    We have been thinking about this problem for a long time. Even the earliest instance of the NSDL Registry (precursor of the current Open Metadata Registry, or OMR, as we like to call it) incorporated a ‘history’ view of the data, basically the ‘who, what, when’ of every change made in every vocabulary. Later on, we added the ability to declare ‘versions’ of the vocabularies themselves, taking advantage of that granular history data, for those trying to manage the updating of their ‘product’ in a rational manner. Sadly enough, not very many of our users took advantage of that feature, and we’re not entirely sure why not, but there it was. Jon has always been frustrated with our first passes at this problem, and after Gordon and I discussed the problem with others at DC-2013 last year, and my rant about the lack of version control on http://id.loc.gov came out, it seemed time to think about the issue again.

    At that point we were also planning our own big time versioning event: the unpublished first version of the RDA Element Sets were about to make their re-debut in ‘published’ form, reorganized, and with new URIs. Jon was also working on the GitHub connection with the OMR underlying the new RDA Registry site, working in a more automated mode as planned. He and Gordon and I had been discussing a new approach for some time, based on the way software is versioned and distributed, which is well-supported in Git and GitHub. So, as we drove back from ALA Midwinter in Philadelphia in January of last year, Jon and I blocked out the paper we’d agreed to do with Gordon on how we thought versioning should work in the semantic vocabulary world.

    Consider: how do all of us computer nerds update our applications? Do we have to go to all sorts of websites (sometimes, but not always, prompted by an email) to determine which applications have changed and invoke an update? Well, sure, sometimes we do (particularly when they want more money!), but since the advent of the App Store and Google Play, we can do our updates much more easily, and for the most part those updates are ‘pushed’ to us for decisions on whether we want to update or not, we are told in a general way what has changed, and we click … and it’s done.

    This is the way updates should happen in the Semantic Web data world, increasingly dependent on element sets and value vocabularies to provide descriptions of products of all kinds in order to provide access, drive sales or eyeballs, or support effective connections between resources. Now that we’re all reconciled to using URIs instead of text (even if our data hasn’t yet made that transition), shouldn’t we consider an important upside of that change, a simpler and more useful way to update our data?

    So, I’ll quit there–go read the paper and let us know what you think. Don’t miss Gordon’s slides from Paris, available on his website. Note especially the last question on his final slide: “Is it time to get serious about linked data management?” We think it’s past time. After all, ‘management’ is our middle name.

    Note: As of this week the video of Gordon’s presentation in Paris is now available.

  • Why Are We Waiting for the ILS to Change?

    A few days ago, while catching up with list traffic on RDA-L, I stumbled on a conversation between two librarians that got me thinking. They were talking about the myriad of changes in their ILS’s designed to make MARC usable with RDA. It’s a topic I still see a lot of on the lists, and it always makes me grind my teeth.

    One reason for the dental destruction is that invariably the changes are small and niggly ones, the sort that make life annoying for those catalogers trying to apply RDA in a world still defined by MARC-based systems. It’s hardly news that those systems are often inflexible, but that’s primarily because they were built to supply services in an environment where data sharing was very centralized, change happened no more frequently than every six months, and everyone was prepared and in sync by the time records started flowing containing updated structure. This world is either gone or on its last legs, depending on your perspective.

    What I saw underlying that conversation was the assumption that the only way change could happen was if the ILS’s themselves changed; in other words if the ILS vendors decided to lead rather than follow. The situation now is that system vendors say they’ll build RDA compliant systems when their customers ask for them, and libraries say that they’ll use ‘real’ RDA when there are systems that can support it. This is a dance of death, and nobody wins.

    For years I’ve been telling librarians that they need to bug their vendors about this state of affairs, but I’m not sure there’s much of a future in that strategy, given that most of the librarians are not yet able to tell the vendors what they want in any detail, and the vendors have been unwilling to build their expertise or invest in any substantive way until they think they have customers ready to buy. This strategy of ‘wait and see’ undoubtedly has its attractions–given that it’s cheap–and the vendors don’t yet see that their current customer base has any alternatives.

    But there are alternatives, albeit ones that require some initiative and investment by either libraries or vendors willing to step forward and perhaps gain a competitive advantage. In essence this strategy is based on the notion that if vendors won’t smarten up their systems, a solution that treats the vendor systems like ‘dumb consumers’ might be the best bet for moving forward. If indeed the tight coordination necessary in the past to share data and manage change is no longer optimal, distributed data need not use an ILS as its primary ‘node’ for storage and management of data. It could just sit there, waiting for some other machine that wished to share data (in or out), and still run its functions for the OPAC and pass data to OCLC.

    But I suggest it’s no longer necessary for that ILS to be the center of our concern and attention, particularly if we see value in participating in the linked data world. The functions of creating and maintaining data could be accomplished elsewhere, preferably in a ‘system’ (maybe just a cache with services) designed to ingest, manage, and expose statement-based data in a variety of formats–including MARC, for as long as we want. Thus, the export of library data and the serving of it to users via an OPAC could be accomplished without giving up the MARC-based ILS, cutting the cord to OCLC, or upsetting current partners and collaborators.

    Yes, we’d still have some work to do, but not nearly as much as we think. We have long understood that the old ideal of a fully ‘integrated’ system is unnecessarily cumbersome and limits our ability to improve our services. Some libraries have bolted discovery platforms on their OPAC that meet their needs better than their ILS does. Others use ERM systems to manage electronic subscriptions. Maybe it’s time to do the same with some of the other backend services that have passed their sell-by date.

    Let the dis-integration begin!

  • Wake-up Call for CC:DA

    Presentations on innovative ways to gather data outside the library silo are happening all over ALA–generally hosted by committees and interest groups using speakers already planning to be at the conference. A great example of the kind of presentation I’m talking about was the Sunday presentation sponsored by the ALCTS CaMMS Cataloging & Classification Research Interest Group produced by the ProMusicaDB project, with founder Christy Crowl and metadata librarian Kimmy Szeto. They provided a veritable feast of slides and stories, all of them illustrating the new ways that we’ll all be operating in the very near future. Their slides should be available on the ALCTS Cataloging and Classification Research IG site sometime soon. [Full disclosure: I spoke at that session too–see previous blog post for more details.]

    On the Saturday of Midwinter, I attended 2 parts of the CC:DA meeting (I had to leave to do a presentation to another group in the middle), but I dutifully returned for the last part. It was probably a mistake–my return occurred during the last gasp of a perfectly awful discussion. I had a brief chat with Peter Rolla (the current chair) after the meeting, and continued to think about why I was so appalled during the last part of the meeting. Later, when held hostage in a meeting by a conversation in which I had little interest, I wrote up some of my thoughts.

    I would describe the discussion as one of the endless number of highly detailed conversations on improving the RDA rules that have been a “feature” of CC:DA meetings for the past few years. To be honest, I have a limited tolerance for such discussions, though I usually enjoy some of the ones at a less excruciating level of detail.

    Somehow this discussion struck me as even more circular than most, and seemed to be aimed at “improving” the rules by limiting the choices allowed to catalogers–in a sense by mechanizing the descriptive process to an extreme degree. Now, I’m no foe of using automated means to create descriptive metadata, either as a sole technique or (preferably) for submission to catalogers or editors to complete. I think we ought to know a lot more about what can be done using technology rather than continue to flog any remaining potential for rule changes intended to push catalogers to supply a level of consistency that isn’t really achievable for humans. If you want consistency–particularly in transcription–use machines. Humans are far better utilized for reviewing the product and correcting errors and adding information to improve its usefulness.

    But in cataloging circles, discussing the use of automated methods is generally considered off-topic. When the [technological] revolution comes, catalogers will be the first to go, or so it is too often believed. Copy cataloging and other less ‘professional’ means of cutting costs and increasing productivity is not a happy topic of conversation for this group.

    But, looking ahead, I see no letup in this trajectory without some changes. Catalogers love rules, and rules are endlessly improvable, no? Maybe, maybe not, but just put a tech services administrator in the room for some of these discussions, and you’re likely to get a reaction pretty close to mine. But to my mind, the total focus on rules rather than a more practical approach to address the inevitability of change in the business of cataloging is doing more towards ensuring that the human role in the process will be limited in ways that make little sense, except monetarily.

    What we need here is to change the conversation, and no group is more qualified to do that than CC:DA. To do that it’s absolutely necessary that its membership become more knowledgeable about what is now possible in automating metadata creation. Without that kind of awareness, it’s impossible to start thinking and discussing how to focus less of CC:DA’s efforts on that part of the cataloging process which should be done by machines, and more on what still needs humans to accomplish. There are several ways to do this. One is by dedicating some of CC:DA’s conference time to bringing in those folks who understand the technology issues to demonstrate, discuss, and collaborate.

    Catalogers and their roles have been changing greatly over the past few years, and promises of more change must be taken seriously. Then the ultimate question might be asked: if resistance is futile (and it surely is), how can catalogers learn enough to help frame that change?

  • The Revolution Is On The Way, Televised or Not

    Many of you have heard me say “Time flies, whether you’re having fun or not”–and that has certainly been the case since I got back from the NISO Roadmap meeting a few weeks ago. Somehow, with my head down, I missed part 1 of Roy Tennant’s post “The Post-MARC Era, Part 1: “If It’s Televised, It Can’t Be the Revolution”. I’m old enough to remember the 60’s and the call to revolution that Gil Scott-Heron referred to, and in fact had a small part in it–but since it WAS live, I’ve no evidence to present about my participation, you’ll just have to believe me.

    On the other hand, I’ve been very involved in the revolution under discussion in the remainder of his post, and there’s quite a bit of video to confirm that, including at the beginning of the NISO Roadmap meeting, where Gordon Dunsire and I tossed a few thought-bombs out before the conversation got going. I think it validates Roy’s point about participation to say that the points we made came up frequently in the subsequent small group sessions, which were not, I believe, on the video feed. What I observed as a participant was that more than a few folks left with some new information and (I hope) some expanded thinking about what the revolution was about; more than they came in with.

    Despite the fact that I’ve acquired an undeserved reputation for being a MARC hater, I actually think that we should continue to use the semantics of MARC, and get rid of the ancient encoding standard. It’s in some ways a Dr. Jekyll and Mr. Hyde problem we have here, and we’re about to kill the ‘wrong MARC’ in our exasperated search for something simpler, because we can’t seem to get clear about what MARC is and isn’t. The reality is that the MARC semantics represent the accumulated experience in library description from the days of the 3 x 5 card with the hole in the bottom (see Gordon Dunsire’s presentation on that evolution). We’ll clearly need to map the semantics of our legacy data forward, but that doesn’t require that we carry along the ‘classic’ MARC encoding. Consider the old days of the telegraph, where messages were encoded using dots and dashes. Those messages were translated into written English for end users, who didn’t need to know Morse Code to read them. Now we use telephone messaging and email for those kinds of communications, and Morse Code doesn’t figure in there anywhere.

    In addition, we need to look past all those rarely used MARC fields, and recognize that they are only irrelevant in an environment that looks very much like our current one, with artisanal catalog records records and top-down standards development. That’s not really what we’re hoping for, as we wrap our minds around what an environment based on linked open data might free us to do differently. When systems were built to process MARC-encoded records, those systems needed to be updated at regular frequencies and all the sharing partners moved in lockstep. It was very expensive to manage the code that was the plumbing of those systems and the specialized fields didn’t add much value. But remember that each of the proposals for change were extensively discussed and formally accepted. I was there for many of those discussions, and recognize that not all of them were accepted, but a considerable number were, and then not always (or often) used after they were included in MARC. Before we label all that effort wasted, and attempt to re-litigate all those decisions, let’s take a closer look at the real costs of moving those forward, in the very different environment we’re envisioning, where the costs are differently distributed and everyone need not move in lockstep. It’s entirely possible that some new communities will find these specialized fields very relevant, even though libraries have not.

    Roy quotes from the BibFrame announcement, which states:

    “A major focus of the initiative will be to determine a transition path for the MARC 21 exchange format in order to reap the benefits of newer technology while preserving a robust data exchange that has supported resource sharing and cataloging cost savings in recent decades.”

    It’s still unclear to me (and I’m not alone here), that we really needed a ‘transition path for the MARC 21 exchange format’. Why can’t we join the rest of the world, which is tootling along quite nicely, thank you, without a bespoke exchange format? We have several useful sets of semantics, built collaboratively over the past half century–why would we need to start over? I generally read the BibFrame discussions, but rarely participate, mostly because it all seems like a reinvention of something that doesn’t need reinventing, and I have no time for that. Whatever the BibFrame people come up with will be mappable to and from the other ongoing bibliographic standards, and whoever wants to use it for exchange can certainly do that, but it will never have the penetration in the library market that MARC has.

    It’s also a bit mysterious what ‘preserving a robust data exchange’ actually means. Are we talking about maintaining the current exchange of records using OCLC as the centralized node through which everything passes? What part of that ‘preservation’ is about preserving the income streams inherent in the current distribution model? What is it about linked open data, without a central node, that isn’t robust enough?

    Roy ends his post with something that I didn’t expect, but definitely applaud:

    “Watching the NISO event over the last two days crystallized for me that I had fallen into the trap of thinking that the Library of Congress or NISO or OCLC (my employer) would come along and save us all. I forgot that for a revolution to occur it can’t come from the seats of the existing power structure. True change only happens when everyone is involved. Those organizations may implement and support what the changes that the revolution produces, but anything dictated from on high will not be a revolution. The revolution will not be piped into our cubicles, ready for easy consumption. The revolution will be live.”

    We could start by no longer waiting for LC to deliver an RDF version of MARC 21, unencumbered by 50 year old encoding standards. We already have that, at http://marc21rdf.info. Yeah, it needs some work, but it’ll get done a lot faster if we can get some help from the 99% of the library world. Give us a holler if you’re interested.

    Clearly the revolution is not happening on the BibFrame discussion list, it is happening elsewhere.

  • Not Letting “Who Pays” be the Killing Question

    A couple of weeks ago I made a short presentation at a linked data session at the American Association of Law Libraries (AALL). Many of the audience members were people I’ve known since I was a baby librarian (this is the group where I started my career as a presenter, and they invite me back every couple of years to talk about this kind of stuff.) One of the questions from the audience was one I hear fairly often: “Who’s paying for this?” I always assume, perhaps wrongly, that the questioner is responding to pressure from an administrator, but in fact anyone with with administrative and budget responsibilities–particularly in Technical Services, which has been under budget siege for decades–does and should think about costs.

    What I said to her was that we were all going to pay for it, and it seems to me that this isn’t just a platitude–given that the culture of collaboration we have developed assures us that many (though certainly not all) of the costs associated with the change we contemplate will be shared, as in the effort noted in my previous post. But the costs are difficult to assess at this stage, because we don’t know how long the transition will be nor exactly what the ‘end result’ will look like. If indeed we have three options for change—metamorphosis, evolution, and revolution—it seems we’ve not yet made the decision on what it’s going to be. If there are still some hoping for metamorphosis—where everything happens inside the pupa and the result is much more attractive (but the DNA hasn’t changed), well, it may be too late for that option.

    Evolution–defined as creative destruction and adaptation leading to a stronger result, with similar (but not identical) DNA–is much more what I’d like to see, and particularly if we look carefully at what we have–the MARC semantics, the SemWeb friendly RDA vocabularies, and the strong community culture in particular–and build on those assets, we have a fighting chance for a good result. The trick is that we don’t have millenia to accomplish this, we have a couple of years at best, if we work really quickly and keep our wits about us. The interesting thing about evolution is that when the environment changes and the affected species either adapt or disappear, it’s never entirely clear what that adaptation will look like prior to the point-of-no-return.

    As for revolution–perhaps that’s the possible result where Google and its partners take over the things we used to do in libraries when we brought users and resources together. They’re doing metadata now (not as well as we do, I’m thinking) but if we keep trying to make our ‘catalogs’ work better instead of getting ourselves out there on the Web, I don’t think the result will be pretty.