With a deep sigh of relief, I report that my presentation at COSUGI this morning on planning for RDA went smoothly and seems to have been well received. I’m attaching PDFs of the slideshow and the accompanying handout on resources for RDA training; after I get a chance to edit my speaker’s notes a little and bring them a little closer to what I actually said, I’ll post those as well.
These presentations always evolve: I sent the materials you are looking at here in mid-February, and I was making changes literally as I got ready this morning. One thing I emphasized in the presentation, that is less prominent in the slideshow, is that preparation for RDA involves a lot of policy planning, much of which will probably be done while you’re learning about the code. Among other things this is an occasion for examining and rethinking your library’s or consortium’s existing policies. And a point I inexplicably omitted: As you make these decisions, it is very important to document, not only the decisions themselves but the reasons for them. Someone after you will be revisiting the issues you’re dealing with now, quite possibly someone who will not have been around for these initial discussions. They will appreciate knowing the context in which you established your policies and practices, which they can use in evaluating what they should do at that undetermined point in the future. And in fact you and your colleagues may well be returning to these questions yourselves, and it can be helpful, when re-evaluating what you’ve done, to have an answer to the question–literally–“What were we thinking?”
UPDATE: Speaker’s notes: