[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ARSCLIST] More on cataloging
Dear All,
And I would add that not only does the data need to be consistent, but the file(s) need to be accompanied by a text-based document (which can then be converted - for example, to Word for Windows). This document lists the various procedures for entering the data, so the data becomes "consistent" by default, while being based on ASCII text it should permanently be readable however word-processors may evolve in future.
Each field in the database is given a name, and its function is defined and its internal syntax described. Thus a performer or composer will be entered surname-first (for sorting or indexing purposes). But I also find I need a "Notes" field, for any unstructured extra information.
I don't know dBaseIII, I only use dBaseII. This software allows one to find the name "Bloggs" whether it's a forename or a surname! And, being an ASCII-based program, I can also write software (in dBase's own language) to generate text-only files of any or all of the data - depending how I write the program.
I feel that both the "phonorecords" feature mentioned by Steven Barr and his "discographical" features are both incorporated. But I admit I am a nerd, and this would not be suitable for general use by anybody. However, so long as people can read, printouts may be made at any time for "general use". My printout software is written so the whole thing is a practical number of sheets of paper, with blank spaces programmed to be ignored, and other features (such as indents) to make it instinctively readable.
Peter Copeland
former Technical Manager
British Library Sound Archive
-----Original Message-----
From: Association for Recorded Sound Discussion List on behalf of Steven C. Barr
Sent: Wed 17/08/2005 23:38
To: ARSCLIST@xxxxxxxxxxxx
Cc:
Subject: Re: [ARSCLIST] More on cataloging
----- Original Message -----
From: "Green Richard" <richard.green@xxxxxxxxxxxxx>
To: <ARSCLIST@xxxxxxxxxxxx>
> This is an old (never-ending) debate - quick and (sometimes) dirty versus
> complete and detailed. Even if you make the cataloguing as complete as
> possible, as we do on the Virtual Gramophone site
> http://www.collectionscanada.ca/gramophone/index-e.html people will
complain
> - there is too much detail or we didn't check all the sources for whatever
> specific detail they are interested in, be it subject headings, session
> information, or whatever. (Those libraries that want to do copy
cataloguing
> from the Virtual Gramophone can now do so through the LACs main catalogue
> AMICUS - this is a step forward.)
>
> My experience tells me that whatever depth of cataloguing you go for it
> needs to be consistent. Which means that record collectors do not always
> make the best cataloguers - as consistency is not always a strong point.
> You need good instructions, good training, and a patient person with a
> meticulous streak in them to spot errors and inconsistencies. Being a
> little retentive helps.
>
> The super catalogue is a dream. Yes there is lots of data out there in
> various computer formats, but there are so many variables in that data,
> nothing is really standardized, that bringing it altogether would result
in
> another series of Rigler Deutsch type complaints. It should be noted that
> Rigler Deutsch does what it was intended to do - provide inexpensive
access
> to large collections that were previously inaccessible at any level.
>
> NAXOS itself has had a debate about cataloguing levels and is dealing with
> complaints about errors, inconsistencies and omissions. They are even
> hiring librarians. The cycle begins again.
>
Basically, there are at least two completely different rationales behind
cataloguing...and this means there are two different forms of the beast!
The first is cataloguing simply to provide a record of the phonorecords
held in a particular collection (or, as in RDI, a group of collections.
At a minimum, this requires some data on each phonorecord (artist credit(s),
title credit(s), label, country, catalog number) as well as the location
where the phonorecord is stored if this is not obvious from the label/
number data.
The second is cataloguing to provide a discographic data archive. Note
that a "type I" catalog can be maintained including all, or as much as
possible, of the applicable discographic data for each phonorecord in
the collection(s) being catalogued.
Insofar as collection catalogs include discographic data, they become
more useful to researchers accessing the data for purposes rather
than accessing the listed phonorecords. The best example is (are?)
the Abrams files; these provide only 160 bytes of data (including
spaces to fill out fields) per phonorecord side, and probably
include about 5% of the existing phonorecords (with a fair amount
of inaccuracy, it might be noted)...but they are consistently
used, and cited on 78-L, to answer questions about phonorecords!
Since I am both collector and discographer, my collection catalog
includes considerable discographic data. I created it using MS
Access and a 3 level relational database. The problem is that
data entry is a long and tedious procedure, requiring 10-15 minutes
per catalogued phonorecord; so far, I have less than 200 phonorecords
catalogued, and have serious doubts as to whether I will ever be
finished with the task! However, if I ever do it will be a valuable
data source for posterity.
As far as the usefulness and/or use of a fairly complete
discographic data archive...note how many times Brian Rust's
discographies are used!
Steven C. Barr
**************************************************************************
Experience the British Library online at www.bl.uk
Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook
The Library's St Pancras site is WiFI - enabled
**************************************************************************
The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the postmaster@xxxxx : The contents of this e-mail must not be disclosed or copied without the sender's consent.
The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author.
**************************************************************************