Category: Systems

  • Review of: DRAFT Principles for Evaluating Metadata Standards

    Metadata standards is a huge topic and evaluation a difficult task, one I’ve been involved in for quite a while. So I was pretty excited when I saw the link for “DRAFT Principles for Evaluating Metadata Standards”, but after reading it? Not so much. If we’re talking about “principles” in the sense of ‘stating-the-obvious-as-a-first-step’, well, okay—but I’m still not very excited. I do note that the earlier version link uses the title ‘draft checklist’, and I certainly think that’s a bit more real than ‘draft principles’ for this effort. But even taken as a draft, the text manages to use lots of terms without defining them—not a good thing in an environment where semantics is so important. Let’s start with a review of the document itself, then maybe I can suggest some alternative paths forward.

    First off, I have a problem with the preamble: “These principles are intended for use by libraries, archives and museum (LAM) communities for the development, maintenance, governance, selection, use and assessment of metadata standards. They apply to metadata structures (field lists, property definitions, etc.), but can also be used with content standards and value vocabularies”. Those tasks (“development, maintenance, governance, selection, use and assessment” are pretty all encompassing, but yet the connection between those tasks and the overall “evaluation” is unclear. And, of course, without definitions, it’s difficult to understand how ‘evaluation’ relates to ‘assessment’ in this context—are they they same thing?

    Moving on to the second part about what kind of metadata standards that might be evaluated, we have a very general term, ‘metadata structures’, with what look to be examples of such structures (field lists, property definitions, etc.). Some would argue (including me) that a field list is not a structure without a notion of connections between the fields; and although property definitions may be part of a ‘structure’ (as I understand it, at least), they are not a structure, per se. And what is meant by the term ‘content standards’, and how is that different from ‘metadata structures’? The term ’value vocabularies’ goes by many names, and is not something that can go without a definition. I say this as an author/co-author of a lot of papers that use this term, and we always define it within the context of the paper for just that reason.

    There are many more places in the text where fuzziness in terminology is a problem (maybe not a problem for a checklist, but certainly for principles). Some examples:

    1. What is meant by ’network’? There are many different kinds, and if you mean to refer to the Internet, for goodness sakes say so. ‘Things’ rather than ‘strings’ is good, but it will take a while to make it happen in legacy data, which we’ll be dealing with for some time, most likely forever. Prospectively created data is a bit easier, but still not a cakewalk — if the ‘network’ is the global Internet, then “leveraging ‘by-reference’ models” present yet-to-be-solved problems of network latency, caching, provenance, security, persistence, and most importantly: stability. Metadata models for both properties and controlled values are an essential part of LAM systems and simply saying that metadata is “most efficient when connected with the broader network” doesn’t necessarily make it so.

    2. ‘Open’ can mean many things. Are we talking specific kinds of licenses, or the lack of a license? What kind of re-use are you talking about? Extension? Wholesale adoption with namespace substitution? How does semantic mapping fit into this? (In lieu of a definition, see the paper at (1) below)

    3. This principle seems to imply that “metadata creation” is the sole province of human practitioners and seriously muddies the meaning of the word creation by drawing a distinction between passive system-created metadata and human-created metadata. Metadata is metadata and standards apply regardless. What do you mean by ‘benefit user communities’? Whose communities? Please define what is meant by ‘value’ in this context? How would metadata practitioners ‘dictate the level of description provided based on the situation at hand’?

    4. As an evaluative ‘principle’ this seems overly vague. How would you evaluate a metadata standard’s ability to ‘easily’ support ‘emerging’ research? What is meant by ‘exchange/access methods’ and what do they have to do with metadata standards for new kinds of research?

    5. I agree totally with the sentence “Metadata standards are only as valuable and current as their communities of practice,” but the one following makes little sense to me. “ … metadata in LAM institutions have been very stable over the last 40 years …” Really? It could easily be argued that the reason for that perceived stability is the continual inability of implementers to “be a driving force for change” within a governance model that has at the same time been resistant to change. The existence of the DCMI usage board, MARBI, the various boards advising the RDA Steering Committee, all speak to the involvement of ‘implementers’. Yet there’s an implication in this ‘principle’ that stability is liable to no longer be the case and that implementers ‘driving’ will somehow make that inevitable lack of stability palatable. I would submit that stability of the standard should be the guiding principle rather than the democracy of its governance.

    6. “Extensible, embeddable, and interoperable” sounds good, but each is more complex than this triumvirate seems. Interoperability in particular is something that we should all keep in mind, but although admirable, interoperability rarely succeeds in practice because of the practical incompatibility of different models. DC, MARC21, BibFrame, RDA, and Schema.org are examples of this — despite their ‘modularity’ they generally can’t simply be used as ‘modules’ because of differences in the thinking behind the model and their respective audiences.

    I would also argue that ‘lite style implementations’ make sense only if ‘lite’ means a dumbed-down core that can be mapped to by more detailed metadata. But stressing the ‘lite implementations’ as a specified part of an overall standard gives too much power to the creator of the standard, rather than the creator of the data. Instead we should encourage the use of application profiles, so that the particular choices and usages of the creating entity are well documented, and others can use the data in full or in part according to their needs. I predict that lossy data transfer will be less acceptable in the reality than it is in the abstract, and would suggest that dumb data is more expensive over the longer term (and certainly doesn’t support ‘new research methods’ at all). “Incorporation into local systems” really can only be accomplished by building local systems that adhere to their own local metadata model and are able to map that model in/out to more global models. Extensible and embeddable are very different from interoperable in that context.

    7. The last section, after the inarguable first sentence, describes what the DCMI ‘dumb-down’ principle defined nearly twenty years ago, and that strategy still makes sense in a lot of situations. But ‘graceful degradation’ and ‘supporting new and unexpected uses’ requires smart data to start with. ‘Lite’ implementation choices (as in #6 above) preclude either of those options, IMO, and ‘adding value’ of any kind (much less by using ‘ontological inferencing’) is in no way easily achievable.

    I intend to be present at the session in Boston [9:00-10:00 Boston Conference and Exhibition Center, 107AB] and since I’ve asked most of my questions here I intend not to talk much. Let’s see how successful I can be at that!

    It may well be that a document this short and generalized isn’t yet ready to be a useful tool for metadata practitioners (especially without definitions!). That doesn’t mean that the topics that it’s trying to address aren’t important, just that the comprehensive goals in the preamble are not yet being met in this document.

    There are efforts going on in other arenas–the NISO Bibliography Roadmap work, for instance, that should have an important impact on many of these issues, which suggests that it might be wise for the Committee to pause and take another look around. Maybe a good glossary would be a important step?

    Dunsire, Gordon, et al. “A Reconsideration of Mapping in a Semantic World”, paper presented at International Conference on Dublin Core and Metadata Applications, The Hague, 2011. Available at: http://dcpapers.dublincore.org/pubs/article/view/3622/1848

  • 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!

  • Versions and services, pt. 2

    [Continuing from a post earlier today]

    The second, and not unrelated, announcement had to do with the end of printed versions of the Red Books, which have traditionally represented LCSH in its most official form. In the LC report to CC:DA the cessation of publication of the Red Books was announced:

    In 2012, LC conducted an extensive study on the impact and opportunities of changes in the bibliographic framework and the technological environment on the future distribution of its cataloging data and products. LC’s transition from print to online-only for cataloging documentation is a response to a steadily declining customer base for print and the availability of alternatives made possible by advances in technology. This shift will enable the Library to achieve a more sustainable financial model and better serve its mission in the years ahead.

    Certainly there’s not much to argue with here–consumers have spoken, and LC, like every institution and service provider, needs to pay attention. But more troubling is what the online-only policy really means. The announcement includes some information on a planned PDF version of LCSH, and points to that PDF, plus the Cataloger’s Desktop and Classification Web products (both behind paywalls) as the remaining complete and up-to-date options.

    Notable for its absence in that announcement is any comment on LCSH on http://id.loc.gov. Many of us are well aware of the gaps that make this version less than complete and up-to-date, and indeed the introduction to the service points out that:

    LCSH in this service includes all Library of Congress Subject Headings, free-floating subdivisions (topical and form), Genre/Form headings, Children’s (AC) headings, and validation strings* for which authority records have been created. The content includes a few name headings (personal and corporate), such as William Shakespeare, Jesus Christ, and Harvard University, and geographic headings that are added to LCSH as they are needed to establish subdivisions, provide a pattern for subdivision practice, or provide reference structure for other terms. This content is expanded beyond the print issue of LCSH (the “red books”) with inclusion of validation strings. *Validation strings: Some authority records are for headings that have been built by adding subdivisions. These records are the result of an ongoing project to programmatically create authority records for valid subject strings from subject heading strings found in bibliographic records. The authority records for these subject strings were created so the entire string could be machine-validated. The strings do not have broader, narrower, or related terms.

    It’s not clear to me that the caveats in this introduction are either widely read or completely understood, but I think a survey of random catalogers to ask how useful the service is and what it includes and doesn’t, you’d get a wide variety of responses. And of course, the updating strategy for the subject headings operates under the same ‘versioning’ pattern as the relators: files are reloaded periodically and there isn’t much in the way of the sort of versioning that could support any kind of notifications to users or support for updating linked data using LCSH outside of ILS’s or traditional central services like OCLC.

    What LC has done could serve as a case study in how not to handle versioning of semantics in a public vocabulary. If we accept the premise that vocabulary semantics will change, there are very few methods to create stable systems that can rely on linked data. One option (preferred) is to use vocabularies from systems that provide stable URIs for past, present, and future versions of the vocabulary or (not preferred) to create a local, stable shadow vocabulary and map the local vocabulary to the public vocabulary over which you have little or no control. Mapping vocabularies in this way gives you the opportunity to maintain the semantic stability of your own system, your own ‘knowledge base’, while still providing the ability to maintain semantic integration with the global pool of linked data. Clearly, this is an expensive proposition. And it’s not as if these issues of reuse vs. extension are not currently under heavy discussion in a number of contexts: on the public schema.org discussion lists, for instance.

    There are a number of related issues here that would also benefit from broader discussion. Large public vocabularies have tended to make an incomplete transition from print to online, getting stuck, like LC, attempting to use the file management processes of the print era to manage change behind a ‘service’ front end that isn’t really designed to do the job it’s being asked to do. What needs to be examined, soon and in public, is what the relationship is between these files and the legacy data which hangs over our heads like a boulder of Damocles. Clearly, we’re not just in need of access to files (whether one at a time or in batches) but require more of the kinds of services that support libraries in managing and improving their data. These needs are especially critical to those organizations engaged in the important work of integrating legacy and project data, and trying to figure out a workflow that allows them to make full use of the legacy public vocabularies.

    Ignoring or denying these issues as important changes are made to the vocabularies that LC manages, on behalf of the cultural heritage communities across the globe, does a disservice to everyone. No one expects LC to come up with all the answers, just as they could not be expected (in the past, or now) to build the vocabularies themselves without the help of the community. NACO, SACO and PCC were, and are, models of collaboration. Why not build on that strength and push more of the discussion about needs and solutions into that same eager, and very competent, community?

  • Versions and services, pt. 1

    The Library of Congress recently made a couple of announcements, which I’ve been thinking about in the context of the provision of linked data services.

    In May, LC announced that a ‘reconciliation’ had been done on the LC relators, in part to bring them into conformance with RDA role terms. This is not at all a bad thing, but the manner in which the revisions were accomplished and presented on http://id.loc.gov points up some serious issues with the strategy LC is currently using to manage these vocabularies.

    As part of this ‘reconciliation’ LC made a variety of changes to the old list. Some definitions were changed, but in most cases the code and derived URI remained the same, creating a situation where the semantics become unreliable. It’s not easy to determine which ones have changed, because the old file was overwritten, the previous version can’t be accessed through the service, and as far as I can tell, there’s no definitive list of changes available. The only clue in the new file are ‘Change Notes’–textual notes with dates of changes–though what changes are not specified. An example can be found under the term ‘Binder’ (code bnd), where the change note has two dates:

    2013-05-15: modified
    1970-01-01: new

    In another example, the term ‘Film editor’, the definition now starts: “A person who, following the script and in creative cooperation with the Director, selects, arranges, and assembles the filmed material, …” whereas the old usage note referred to “… a person or organization who is an editor of a motion picture film …”. This is a clear and significant change of definition because the reference to the organization entity has been dropped. Curiously the definition for the term ‘Scenarist’ continues to refer to “A person or organization who is the author of a motion picture screenplay …”, although the definition was changed at the same time. Perhaps the difference occurs because the change note for ‘Film editor’ refers to “FIAF”, which is probably the International Federation of Film Archives (the announcement refers to FIAT, a probable typo).

    This M.O. may be perfectly satisfactory to support most human uses of the vocabulary, but it is clearly not all that useful for machines operating in a linked data environment. I was alerted to some of these issues by a colleague building a map based on the prior version, which now needs to be completely revised (and without a list of changes, this becomes a very laborious process). It’s also my understanding that the JSC just recently updated some of the relationship definitions for the most recent update of the RDA Toolkit, which are now out-of-sync with the ‘reconciled’ relator terms.

    A number of questions arise as a result of this, perhaps chief among them the basic one of whether it makes sense to reconcile these vocabularies at all. Because this work was not discussed publicly before the reconciled vocabulary was unveiled (I might be wrong about this, but I’m sure someone will correct me if I missed something), the potential effect on legacy data is unknown, as are any other options for dealing with the issues created by lack of established process or opportunity for public comment. If you accept the premise that we will continue to live in an environment of multiple vocabularies for multiple uses, there are other strategies–mapping and extension, for instance–that might have a better chance to improve usefulness while avoiding the kinds of reliability and synchronization problems these changes bring to the fore.

    In addition to the process issues, a strong case could be made that the current services presented under the id.loc.gov umbrella might benefit from some discussion about how the data is intended to be used and managed. Not everyone is tied to traditional ILSs now, and perhaps fewer will be in future, if current interest in linked data continues. Are all users of these vocabularies going to be expected to flush their caches of data every time a new ‘version’ of the underlying file is loaded? How would they know of change happening behind the scenes (unless, of course, they are careful readers of LC’s announcements)? If LC expects to provide services for linked data users, these issues must be discussed openly and use cases defined so that appropriate decisions are enabled. At a minimum, these practices need to be examined in the context of linked data principles that call for careful change to definitions and URIs to minimize surprises and loss of backward compatibility.

    [Continued]

  • Mulling Midwinter

    One of the things I often do in the weeks following ALA conferences is check out the blog posts about sessions I missed attending. One such was the session on “Recent Trends in Catalog Architecture: ALCTS Catalog Form and Function Interest Group.” I don’t recall what we were doing instead of going to this session, but it looks like we missed a very interesting conversation. That happens far too often at the jam-packed Midwinter and Annual conferences—but thankfully these days the bloggers are keeping us all better informed. Laura Akerman has posted an interesting report of the IG’s session. Slides for this session are also available.

    One of the inescapable conclusions to draw from reading the reports is that the separation of metadata from display considerations seems to be well underway, at least if you consider those folks in the innovation corner. This is very welcome news, particularly for one who has had too many frustrating conversations over the past few years with folks whose heads are so deep into MARC that the revolutionary idea that display decisions are not inextricably tied to metadata fields is completely foreign. Also, it seems clear from the report that the notion of strict MARC-ish boundaries around what kinds of metadata libraries might be interested in providing in a discovery interface is no longer quite so impervious.

    I was struck by the blogger’s quote from the chair: “These presentations were varied but all concerned the architecture and functionality of multiple layers – “what happens (or needs to happen) in between” to transform, combine, and synchronize metadata.” It seems that everyone is traveling down this path these days, which is very good news indeed. In the search for appropriate metaphor that we’ve all done, Frances McNamara from the University of Chicago, the first presenter, called their aggregation of resources ‘stone soup’–a nice metaphor on the whole, though it does imply very hard lumps and not a lot of flavor. The second group of presenters, Joshua P. Barton & Lucas Wing Kau Mak from Michigan State University entitled their presentation “To Fix A Leaky Sink: Envisioning The Potential of Discovery Layers,” although this seems an oddly juicy metaphor for what blogger Laura Akerman described as primarily a “think piece.”

    The third presentation was by Jennifer Bowen, of the eXtensible Catalog Project (full disclosure: Jon and I worked with XC as consultants early on in their development and at various points since). XC’s view of metadata management borrows a great deal from the work we did (and published about) during the days when the National Science Digital Library (NSDL) was young and doing interesting things (before it became a development shop for the Fedora CMS). [Links to the original papers can be found at our website.) From the point of view of libraries looking at the management of metadata as something that happens outside of an ILS, their service architecture is by far their best stuff. In addition to Jennifer’s slides, anyone interested in what XC is doing should take a look at their recently released screencasts, particularly the first and the third, which includes a detailed description of what the MST (Metadata Services Toolkit) really does. Our metaphor for this functionality has always been “The Metadata Washing Machine,” so we’ve really no business complaining about anyone else’s choices!

    The last presentation was by Aaron Wood, of the University of Calgary, and the placement of this particular presentation is important, because it clearly points out that once you’ve created your soup and/or washed your dirty metadata, you still need to figure out how to present results to users in ways that are far different than what we’re used to in the typical ILS interface. Calgary uses the new Summon product from Serials Solutions (which, by the way, also builds on the notion of aggregated metadata services we pioneered in NSDL). The question that turns up in the blog post “how to prevent the local institution’s collections (print and digital) from becoming marginalized in search results when combined with a much larger number of full text resources (licensed journal articles etc.)” is right to the point, because it assumes, as we all should, that the usual alphabetic display that most of our ILS systems produce, that must be scrolled or paged through, is no longer good enough. The presentation points out something we found in NSDL several years ago, that when metadata records and full text are trolled for keywords, the full text always tends to rise to the top, and that’s not necessarily always a good thing from a user point of view. Metadata in general is a poor performer when simply treated as text by full-text indexers, not just because there’s not enough text, but also because full-text indexing generally perceives no additional value in controlled vocabularies and their relationship to well-defined properties (and the richness of the relationships that lie behind the vocabularies as well).

    But I’m sorry I missed this session, and thanks to Laura Akerman and the Metadata Blog for providing such a good summary of the session.

  • 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!

  • 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!]