Category: ALA Conferences

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

  • Hey BibFramers, what’s it all about?

    One of the ongoing myths about RDA is that it’s just a set of instructions and rules for the creation and maintenance of bibliographic metadata, regardless of data model. This has never been entirely accurate, since the RDA instructions explicitly reference RDA’s FRBR-based metadata model, which was significantly modified by BibFrame. But the notion of RDA-as-rules divorced from its data and infrastructure seems still to be part of the promotion of Bibframe. This is not helpful, and when the misinformation is stated over and over it begins to look like an Alternative Fact.

    For example, as part of the Bibframe Update presentations at ALA in Chicago, it was stated that the Bibframe editor will have the “RDA rules hot linked to element labels” (presumably from the Toolkit) to assist catalogers using BF to create bib data. I find this difficult to get my head around — BF and RDA use different reference models, name things differently, etc. And the RDA 3R project to reorganize and rewrite the instructions to align RDA with the IFLA LRM (which is both more extensive than, and less aligned with the Bibframe model) is well underway, and will likely confuse the issue even more.

    The contention that RDA guidance can be used to build BF data is certainly not new. What is new was the momentum of change in process with RDA, from the R3 project, to the internationalization of RDA governance, to the growing list of translations. When the 3R Project is complete (early next year), the RDA instructions in the Toolkit and the data in the RDA Registry will be far more integrated than AACR and MARC ever were. Whether that integration will leave room for BibFrame to use the new instructions is unclear.

    There was an impressive list of RDA information sessions at Annual, and an increasing numbers of folks attending them. This suggests that the RDA message seems to be gaining momentum, and there’s mounting evidence that this is so. A few presentations from the “RDA towards Linked Data sessions, held in conjunction with the European RDA Interest Group (EURIG) annual meeting in Fiesole, Italy this May illustrate that point:

    In his presentation, Philip Schreur pointed out that RDA “is a natural representation of our data on the Web” because of its extensible and flexible framework, its rich treatment of relationships, and its focus on resource discovery.

    Gordon Dunsire’s presentation showed how the wider implementation of the “4-fold path” in RDA for data capture and storage is intended to support a full range of data representation from catalogue cards, flat file schema, and RDBMS, to linked data.

    Most people who attended the RDA sessions in Chicago seemed to be very interested in RDA’s approach, in particular how the data is handled, the growth of translations, and the strong desire to extend RDA to meet the needs of specialized cataloging communities. A meeting to explore the needs of those communities was exceptionally well attended, with lots of good suggestions. And the RDA Linked Data Forum (where people actually got a chance to ask questions!!) was standing room only. (My slides are here).

    There are definite challenges for the North American cataloging community moving forward if they want to avoid isolating themselves from the rest of the bibliographic world, by and large unenthusiastic about BibFrame. The Anglo-American cataloging rules are fading into the distance as the rest of the world embraces the reality of a truly multinational, multilingual, multicultural metadata environment, exemplified by the RDA/LRM bibliographic model. The North American bibliographic community has never been explicitly “America First” and now is not the time to start.

    Stay tuned.

  • “Understanding Metadata”: a sort of review

    While checking email during a moment of inattention at the recent ALA Midwinter meeting in Atlanta, I spotted an announcement of the new NISO publication “Understanding Metadata”, by Jenn Riley. It was a surprise, I’d not known that it was in preparation, but I hoped that such a primer would be helpful in raising the level of understanding around metadata in the general library community.

    So I downloaded the publication, and as is my wont, started with the Table of Contents to get a sense of what was being covered. To my absolute astonishment, neither the list of Notable Metadata Languages: Examples in Broad Use nor the one of Notable Metadata Languages: Examples from the Cultural Heritage Sector included RDA: Resource Description and Access. In disbelief, I searched the document for “RDA” and found only a footnote describing RDA as the successor to AACR2 and categorized as a ‘content standard’. I then tried searching for “FRBR”, and there was nothing at all to be found.

    Full disclosure: I’m part of the RDA Development Team and have worked on the RDA Vocabularies since late 2007, after the RDA group and DCMI got together to build them. Granted, it took until January 2014 to publish them formally and bring up the RDA Registry, but we were not hiding under a rock for those years.

    There’s a long trail of articles and blog posts documenting the trajectory of RDA (only some of them with my name on them), so it’s inexplicable to me how the author of this primer, the estimable Jenn Riley, could still subscribe to the notion that RDA is all about instructions for populating element sets. That was certainly true before 2008, but I know Jenn has not been hiding under a rock, either. Particularly when efforts outside North America are considered, RDA is a force to be reckoned with in the metadata space, and interest in Europe and other places outside of North America is enthusiastic and growing.

    None of the IFLA standards show up in this publication either, which suggests a somewhat US-centric view–inexplicable to me given the increasing internationalization of metadata efforts overall. Several of those missing IFLA standards, including FRBR, are being republished after extensive reviews, and at least in RDA-land, the IFLA Library Reference Model (LRM) is a significant topic of conversation where library metadata people hang out.

    Then I checked out Jenn’s wonderful image categorizing metadata standards “Seeing Standards: A Visualization of the Metadata Universe”, and noted that it also included RDA as a content standard and successor to AACR2. Then I saw that the image was copyrighted 2009-2010, and the most obvious answer for the gap became clearer. [I should note that I have a large poster sized version of the image, which I had printed up so I could study the image better, back when I was doing more teaching]. I was pretty relieved by this realization, to be honest, but it occurred to me that the revolutionary change represented by the RDA Vocabularies seems to have been overlooked by Jenn (and probably others) who think they know what RDA is, but haven’t looked at it lately (or at least since 2008, when the vocabularies began to appear in the Open Metadata Registry). I guess as one involved in metadata standards for well over 3 decades, it’s been my experience that with few exceptions, metadata standards change continually, and the assumption that they are fixed in time and space is a dangerous one.

    That said, there is much to be applauded in this primer. The explanation of storage and sharing is an excellent overview, clear and well illustrated. It was good to see a section covering standardization issues, but I would argue with this statement in the ‘Standardization’ section: “Formal standardization is not the norm for most RDF vocabularies; instead, communities tend to build vocabularies that are useful to them, then promote their use through a combination of documentation and open sharing of data that uses these vocabularies.” This statement absolutely does not apply to RDA, nor to the majority of the examples listed in Notable Metadata Languages: Examples in Broad Use. But in a sense it explains the emphasis on XML that seemed a bit out of date as I first read through the document

    I would also argue with the following statement in the Controlled Vocabularies section: “Those developed and maintained by the cultural heritage community, such as LCSH, tend to be among the most robust controlled vocabularies in common use.” I’m not sure what definition of ‘robust’ is being used here, but I posted on Metadata Matters in 2013 about the significant problems with LCSH in http://id.loc.gov, which i think makes a strong argument against the ‘robustness’ of the LCSH services. (https://managemetadata.com/blog/2013/07/23/versions-and-services-pt-2/). Not much has changed since that post, sadly.

    I guess, on the whole, I’d have to say I’m disappointed with this primer, despite some strong sections. Although I’m no fan of peer review, it strikes me that this is one situation where it might have been useful.

  • The RDA Toolkit == The RDA Data Model

    Sitting in the CC:DA meeting at ALA last week, listening to the RDA report and the questions it generated, I was struck yet again by the disconnect between the understanding by the audience of RDA as a content model — the Instructions as embodied in the Toolkit — and the presentation by the speakers of the changes to both the RDA Toolkit and the RDA Registry in terms of the changes to the RDA data model.

    In the case of the Toolkit, a significant part of the reorganization is intended to better align the Toolkit with the Registry, the data model. In the case of the Registry, a significant portion of the changes are intended to continue the current data model’s status as an implementation of FRBR, and to adjust the model to accommodate the consolidation of the various FRBR models into the IFLA LRM.

    From its inception, the Toolkit has reflected the RDA instructions, an upgraded and internationalized version of AACR2, originally intended to provide content instructions for populating the MARC21 carrier, while conceptually describing the data in terms of the FRBR-oriented RDA carrier. The changes to the Toolkit are a necessary evolution away from the slowly devolving MARC21 data model toward the RDA data model. But the audience doesn’t, can’t, easily see that distinction, and the ‘questions’ swirl around expressions of discomfort with the changes that reflect a lack of understanding of the broadening disconnect between the Toolkit and the Registry, and between RDA and MARC21.

    This cognitive dissonance must be addressed by the RSC and its representatives at every future opportunity when discussing the rationale for both the alignment of the RDA data model with IFLA LRM, and the alignment of the RDA content model in the Toolkit with the RDA data model. In that context, the global bibliographic community needs definitive guidance in understanding the relationship between the entities and elements of the RDA data model and the MARC21 data model in which they currently create and maintain their metadata.

  • Breaking the silence: Atlanta

    Still here in Atlanta, enjoying the weather (today is something of an exception: thunderstorms and rain). My first meeting of the conference was on Friday–the FRBR Interest Group discussion–and although I rarely attend, it seemed to have a lot of potential. I was especially interested in finding out what other folks were thinking and asking about the IFLA Library Reference Model, the successor to FRBR, now being widely discussed.

    There were probably 25 people there, actively chatting with colleagues and friends, waiting for the session to begin. But it didn’t. There was a table set up with microphones and bottled water, a podium, a projection screen in the corner and the usual aging Dell laptop for presenters next to the podium. Nobody behind the table, nobody putting a stop to the conversations to start the meeting.

    Although there was a past leader of the IG present, she wasn’t interested in taking over. It will surprise none of you that I ended up leading the meeting. We went around the group and everyone introduced themselves and spoke about why there were there. As part of that we discovered that there were at least three people in the group for whom Atlanta was their first ALA conference, and not only that: the FRBR IG meeting was their first ever ALA meeting. The old hands apologized to them, told them it wasn’t usually like this, and suggested some other meetings where they could learn about the subject.

    But this situation was appalling, and though none of us had any idea who should have been there or why they weren’t, there was a meeting on the schedule and somebody paid for the microphones, room and A/V setup. We all know about the things that can go wrong on the way to a presentation: travel/weather hassles, illness, etc., none of which can be avoided entirely. But why wasn’t a substitute in place? There are certainly others from the IG who could have stepped in, and we all know how to send slides through the ether for a substitute to present.

    This IG is an ALCTS group (http://www.ala.org/alcts/mgrps/ig/ats-dgfrbr) and I’d suggest that ALCTS needS to look into this and perhaps add something to their instructions for IG chairs. #ALAMW17

  • 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

  • Fresh From ALA, What’s New?

    In the old days, when I was on MARBI as liaison for AALL, I used to write a fairly detailed report, and after that wrote it up for my Cornell colleagues. The gist of those reports was to describe what happened, and if there might be implications to consider from the decisions. I don’t propose to do that here, but it does feel as if I’m acting in a familiar ‘reporting’ mode.

    In an early Saturday presentation sponsored by the Linked Library Data IG, we heard about BibFrame and VIVO. I was very interested to see how VIVO has grown (having seen it as an infant), but was puzzled by the suggestion that it or FOAF could substitute for the functionality embedded in authority records. For one thing, auth records are about disambiguating names, and not describing people–much as some believe that’s where authority control should be going. Even when we stop using text strings as identifiers, we’ll still need that function and should be thinking carefully whether adding other functions makes good sense.

    Later on Saturday, at the Cataloging Norms IG meeting, Nancy Fallgren spoke on the NLM collaboration with Zepheira, GW, (and others) on BibFrame Lite. They’re now testing the Kuali OLE cataloging module for use with BF Lite, which will include a triple store. An important quote from Nancy: “Legacy data should not drive development.” So true, but neither should we be starting over, or discarding data, just to simplify data creation, thus losing the ability to respond to the more complex needs in cataloging, which aren’t going away, (a point demonstrated usefully in the recent Jane-athons).

    I was the last speaker on that program, and spoke on the topic of “What Can We Do About Our Legacy Data?” I was primarily asking questions and discussing options, not providing answers. The one thing I am adamant about is that nobody should be throwing away their MARC records. I even came up with a simple rule: “Park the MARC”. After all, storage is cheap, and nobody really knows how the current situation will settle out. Data is easy to dumb down, but not so easy to smarten up, and there may be do-overs in store for some down the road, after the experimentation is done and the tradeoffs clearer.

    I also attended the BibFrame Update, and noted that there’s still no open discussion about the ‘classic’ (as in ‘Classic Coke’) BibFrame version used by LC, and the ‘new’ (as in ‘New Coke’) BibFrame Lite version being developed by Zepheira, which is apparently the vocabulary they’re using in their projects and training. It seems like it could be a useful discussion, but somebody’s got to start it. It’s not gonna be me.

    The most interesting part of that update from my point of view was hearing Sally McCallum talk about the testing of BibFrame by LC’s catalogers. The tool they’re planning on using (in development, I believe) will use RDA labels and include rule numbers from the RDA Toolkit. Now, there’s a test I really want to hear about at Midwinter! But of course all of that RDA ‘testing’ they insisted on several years ago to determine if the RDA rules could be applied to MARC21 doesn’t (can’t) apply to BibFrame Classic so … Will there be a new round of much publicized and eagerly anticipated shared institutional testing of this new tool and its assumptions? Just askin’.

  • The Jane-athon Report

    I’ve been back from Chicago for just over a week now, but still reflecting on a very successful Jane-athon pre-conference the Friday before Midwinter. And the good news is that our participant survey responses agree with the “successful” part, plus contain a lot of food for thought going forward. More about that later …

    There was a lot of buzz in the Jane-athon room that day, primarily from the enthusiastic participants, working together at tables, definitely having the fun we promised. Afterwards, the buzz came from those who wished they’d been there (many on Twitter #Janeathon) and others that wanted us to promise to do it again. Rest assured–we’re planning on another one in San Francisco at ALA Annual, but it will probably be somewhat different because by then we’ll have a better support infrastructure and will be able to be more concrete about the question of ‘what do you do with the data once you have it?’ If you’re particularly interested in that question, keep an eye on the rballs.info site, where new resources and improvements will be announced.

    Rballs? What the heck are those? Originally they were meant to be ‘RIMMF-balls’, but then we started talking about ‘resource-balls’, and other such wanderings. The ‘ball’ part was suggested by ‘tar-balls’ and ‘mudballs’ (mudball was a term of derision in the old MARBI days, but Jon and I started using it more generally when we were working on aggregated records in NSDL).

    So, how did we come up with such a crazy idea as a Jane-athon anyway? The idea came from Deborah Fritz, who’d been teaching about RDA for some time, plus working with her husband Richard on the RIMMF (RDA In Many Metadata Formats) tool, which is designed to allow creation of RDA data and export to RDF. The tool was upgraded to version 3 for the Jane-athon, and Deborah added some tutorials so that Jane-athon participants could get some practice with RIMMF beforehand (she also did online sessions for team leaders and coaches).

    Deborah and I had discussed many times the frustration we shared with the ‘sage on the stage’ model of training, which left attendees to such events unhappy with the limitations of that model. They wanted something concrete–they usually said–something they could get their teeth into. Something that would help them visualize RDA out of the context of MARC. The Jane-athon idea promised to do just that.

    I had done a prototype session of the Jane-athon with some librarians from the University of Hawaii (Nancy Sack did a great job organizing everything, even though a dodgy plane made me a day late to the party!) We got some very useful evaluations from that group, and those contributed to the success of the official Chicago debut.

    So a crazy idea, bolstered by a lot of work and a whole lot of organizational effort, actually happened, and was even better than we’d dared to hope. There was a certain chaos on the day, which most people accepted with equanimity, and an awful lot of learning of the best kind. The event couldn’t have happened without Deborah and Richard Fritz, Gordon Dunsire, and Jon Phipps, each of whom had a part to play. Jamie Hennelly from ALA Publishing was instrumental in making the event happen, despite his reservations about herding the organizer cats.

    And, as the cherry on top: After the five organizers finished their celebratory dinner later in the evening after the Jane-athon, we were all out on the sidewalk looking for cabs. A long black limousine pulled up, and asked us if we wanted a ride. Needless to say, we did, and soon pulled up in style in front of the Hyatt Regency on Wacker. Sadly, there was no one we knew at the front of the hotel, but many looked askance at the somewhat scruffy mob who piled out of the limo, no doubt wondering who the heck we were.

    What’s up next? We think we’re on the path of a new data sharing paradigm, and we’ll run with that for the next few months, and maybe riff on that in San Francisco. Stay tuned! And do download a copy of RIMMF and play–there are rballs to look at and use for your purposes.

    P.S. A report of the evaluation survey will be on RDA-L sometime next week.

  • The Jane-athon Prototype in Hawaii

    The planning for the Midwinter Jane-athon pre-conference has been taking up a lot of my attention lately. It’s a really cool idea (credit to Deborah Fritz) to address the desire we’ve been hearing for some time for a participatory, hands on, session on RDA. And lets be clear, we’re not talking about the RDA instructions–this is about the RDA data model, vocabularies, and RDA’s availability for linked data. We’ll be using RIMMF (RDA in Many Metadata Formats) as our visualization and data creation tool, setting up small teams with leaders who’ve been prepared to support the teams and a wandering phalanx of coaches to give help on the fly.

    Part of the planning has to do with building a set of RIMMF ‘records’ to start with, for participants to add on their own resources and explore the rich relationships in RDA. We’re calling these ‘r-balls’ (a cross between RIMMF and tarballs). These zipped-up r-balls will be available for others to use for their own homegrown sessions, along with instructions for using RIMMF and setting up a Jane-athon (or other themed -athon), and also how to contribute their own r-balls for the use of others. In case you’ve not picked it up, this is a radically different training model, and we’d like to make it possible for others to play, too.

    That’s the plan for the morning. After lunch we’ll take a look at what we’ve done, and prise out the issues we’ve encountered, and others we know about. The hope is that the participants will walk out the door with both an understanding of what RDA is (more than the instructions) and how it fits into the emerging linked data world.

    I recently returned from a trip to Honolulu, where I did a prototype Jane-athon workshop for the Hawaii Library Association. I have to admit that I didn’t give much thought to how difficult it would be to do solo, but I did have the presence of mind to give the organizer of the workshop some preliminary setup instructions (based on what we’ll be doing in Chicago) to ensure that there would be access to laptops with software and records pre-loaded, and a small cadre of folks who had been working with RIMMF to help out with data creation on the day.

    The original plan included a day before the workshop with a general presentation on linked data and some smaller meetings with administrators and others in specialized areas. It’s a format I’ve used before and the smaller meetings after the presentation generally bring out questions that are unlikely to be asked in a larger group.

    What I didn’t plan for was that I wouldn’t be able to get out of Ithaca on the appointed day (the day before the presentation) thanks not to bad weather, but instead to a non-functioning plane which couldn’t be repaired. So after a phone discussion with Hawaii, I tried again the next day, and everything went smoothly. On the receiving end there was lots of effort expended to make it all work in the time available, with some meetings dribbling into the next day. But we did it, thanks to organizer Nancy Sack’s prodigious skills and the flexibility of all concerned.

    Nancy asked the Jane-athon participants to fill out an evaluation, and sent me the anonymized results. I really appreciated that the respondents added many useful (and frank) comments to the usual range of questions. Those comments in particular were very helpful to me, and were passed on to the other MW Jane-athon organizers. One of the goals of the workshop was to help participants visualize, using RIMMF, how familiar MARC records could be automatically mapped into the FRBR structure of RDA, and how that process might begin to address concerns about future workflow and reuse of MARC records. Another goal was to illustrate how RDA’s relationships enhanced the value of the data, particularly for users. For the most part, it looked as if most of the participants understood the goals of the workshop and felt they had gotten value from it.

    But there were those who provided frank criticism of the workshop goals and organization (as well as the presenter, of course!). Part of these criticisms involved the limitations of the workshop, wanting more information on how they could put their new knowledge to work, right now. The clearest expression of this desire came in as follows:

    “I sort of expected to be given the whole road map for how to take a set of data and use LOD to make it available to users via the web. In rereading the flyer I see that this was not something the presenter wanted to cover. But I think it was apparent in the afternoon discussion that we wanted more information in the big picture … I feel like I have an understanding of what LOD is, but I have no idea how to use it in a meaningful way.”

    Aside from the time constraints–which everyone understood–there’s a problem inherent in the fact that very few active LOD projects have moved beyond publishing their data (a good thing, no doubt about it) to using the data published by others. So it wasn’t so much that I didn’t ‘want’ to present more about the ‘bigger picture’, there wasn’t really anything to say aside from the fact that the answer to that question is still unclear (and I probably wasn’t all that clear about it either). If I had a ‘road map’ to talk about and point them to, I certainly would have shared it, but sadly I have nothing to share at this stage.

    But I continue to believe that just as progress in this realm is iterative, it is hugely important that we not wait for the final answers before we talk about the issues. Our learning needs to be iterative too, to move along the path from the abstract to the concrete along with the technical developments. So for MidWinter, we’ll need to be crystal clear about what we’re doing (and why), as well as why there are blank areas in the road-map.

    Thanks again to the Hawaii participants, and especially Nancy Sack, for their efforts to make the workshop happen, and the questions and comments that will improve the Jane-athon in Chicago!

    For additional information, including a link to register, look here. Although I haven’t seen the latest registration figures, we’re expecting to fill up, so don’t delay!

    [these are the workshop slides]

    [these are the general presentation slides]

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