One of the conclusions of the LC Working Group on the Future of
Bibliographic Control, was that we (speaking generally) kept trying to solve
EVERY issue in a single package, and not to issue the final package until it
was all done. As opposed to working on discrete problems/issues (though in
context), coming up with a possible solution on X and trying it out, then
coming up with a possible solution on Y and trying it out, and eventually
tying it all (or lots of it) together into an ex-post-facto package. The
LCWG was talking about how we approach the revision of massive things like
AACR/RDA, LCSH, MARC, etc. But the same thoughts could well apply to the
matter of a user interface/tool. If we don't try to solve EVERYTHING all
at once, we might make greater (and ultimately more satisfactory) progress.
janet
Janet Swan Hill, Professor
Associate Director for Technical Services
University of Colorado Libraries, CB184
Boulder, CO 80309
janet.hill_at_colorado.edu
*****
Tradition is the handing-on of Fire, and not the worship of Ashes.
- Gustav Mahler
Received on Wed Mar 11 2009 - 11:07:17 EDT