3 thoughts on “Some things read this week, 1 – 7 July 2007

  1. I agree with you about RDA and subjects being missing. That’s one big piece of the jigsaw puzzle to be leaving out. It’s like a building a house and leaving one half of it unfinished.

    I’ve just started to read through the RDA drafts in the last two weeks and it’s literally been keeping me awake at nights. I’m excited by the work to bring into line with DCAM and RDF but the scale of implementing the changes is pretty daunting. Is it too dramatic to say the future of cataloguing is riding on this? ;-)

    From what I can gather there is no guarantee the early parts won’t be re-written. I would like to see it re-structured using FRBR and the RDA element set as the basis for the chapters rather than trying to use the old AACR structure. At the moment it’s like a caterpillar half-way on the way to emerging as a butterfly — neither one nor the other and not very pretty.

    Irvin

  2. While I’m at it …

    One thing that makes RDA very hard to read IMO is the terminology. It actually changes depending on how recent a draft you’re reading. For example, ‘resource’ seems to mean different things in different places. The later chapters use FRBR terms more than the earlier chapters. I haven’t read the carrier/content sections yet so I can’t comment on them.

    And the term ‘access’ seems to me a potential source of confusion. Elements are described as ‘access control points’ but what access do they provide? A naive user would probably expect ‘access to the resource’, but really it’s access to the bib record, isn’t it, in the old card catalog sense? The drafts are full of such atavisms. I can see why they have been kept: to reassure cataloguers that it’s ‘really still the old AACR underneath’, but it’s not the old AACR anymore so it’s time to bite the bullet and do a complete re-write.

  3. Hi Irvin, I do expect the early parts to be re-written. In fact, I’m fairly sure I’ve seen something that says so since the RDA-DC announcement, but I don’t remember where.

    Yes, terminology is a big issue. Both for us in the field, and for the user. Of course, with proper implementations the end user would never have to see such terminology anyway. But can we hope for our systems to be designed so they don’t?