Re: arsclist Cataloging

[<stevenc@xxxxxxxxxxxxxx>]

Okeh...
1) dBASE (in fact, any DOS program that I'm aware of) can support most
common diacriticized characters...however, they aren't eay to read. If you
know (or can look up) the byte value of the character ( a chart should be
easy to find) you can enter Alt + <byte value as number> and the desired
character will be both displayed and entered. Some programs, as well as
(I think) Macs will allow diacriticals to be entered with key combinations;
as well, Windows programs can use the Windows character map to insert
high-order characters as well as symbolic-font characters.
2) While dBASE has "gone to its great reward," one can find used or
leftover copies on occasion...even of newer versions. I bought a sealed
copy of dBASE V for Windows for $2.99; it can read and open all older
version dBASE files and adds a whole array of Access-like features I
still haven't fully explored.
3) The main advantage of dBASE is that the files are comprehensible even
without the program; it stores its data as ASCII files with short file
headers.
4) The main disadvantage is that it makes it very difficult to use
relational
databases (Access, on the other hand, makes that task so easy a user can
easily wind up well over his/her/its head when creating and using one!)
Relational database use is not absolutely vital for computerizing
discography,
but (as I learned the hard way) results in a lot of wasted storage space
if you are documenting, say, single-face Red Seals.
5) One small but very useful dBASE feature I haven't so far found in Access
is the "Repeat Field" feature, which allows you to catalog, say, a whole
pile of RCA Victor discs by filling the LABEL field with a single keystroke.
6) The nice thing about dBASE and other programs using the "xBASE"
format (NOT MS FoxPro!) is that almost every database application
can import dBASE files. Create an Access file, for example, and anyone
who wants to use it has to have Access.
7) Finally, the important aspect of catalog databases (and the related
discographic archives) is NOT the file format, or the application(s) used;
it is, rather, the data record structure, on which there is (AFAIK) little
or no standardization between users. As long as I know which field
contains the data on the actual artist and which the pseudonym (as an
example)...I can import your data by, if all else fails, an OCR scan of
your printout, and add it to my archives. However, if I don't know
what is stored where...or if you use a system where the ARTIST field
contains a numeric key to a table of listed artists, and I don't have
a copy of that table...I can't use your data! This is the area in which
I think some standardization is important (and which I hope to see
discussed at the convention this spring).
Steven C. Barr
----- Original Message -----
From: "Kevin P. Mostyn" <koussy@xxxxxxx>
To: <ARSCLIST@xxxxxxxxxxxxxxxx>
Sent: Friday, December 20, 2002 2:04 PM
Subject: Re: arsclist Cataloging


>
>
> Dear Peter,
>
> Microsoft Access can do Boolean searches exactly as you list. They
> are not command line, but they are quite easy to do, using simple queries.
>
> Access fully supports diacriticals, although not as thoroughly as did the
> WordPerfect database called DataPerfect. I would posit that any database
> program that cannot support diacriticals is fatally flawed, at least for
> collectors of classical or ethnic music.
>
> Access also easily exports/imports to/from ASCII text files; the
> diacriticals are not lost in this process.
>
> Windows XP fully supports DOS programs; I'm using one (YARN) to write this
> reply to you. Its support for DOS is even better than that of Windows
2000.
> I do not claim that all DOS programs will run, but certainly most non-game
> programs will.
>
> I am not a shill for Microsoft; indeed I am a vociferous critic of many of
> their actions. However, old is not necessarily better, unless one is
talking
> about recordings!
>
> Kevin Mostyn
>
>
> In article <343540CF89C2774289E7F3C9EE4F5DF15939E2@xxxxxxxxxxxxxxx>, you
wrote:
> >Dear All,
> >    I'm afraid the question of which software to use depends very much
upon
> >what kind of person *you* are. Personally, I still use dBaseII (version
> >2.41) for the following reason. It came with a simple programming
language,
> >which makes it possible to *export* the data in any way you like,
including
> >ASCII .TXT files, which (in my experience) most things can read. And, if
> >people preserved their original floppydiscs (as in my case), the program
> >could be migrated onto any new computer which can handle 8-bit software.
> >(This rules out Microsoft XP, due to Bill Gates' apparent penchant for
> >deliberate obsolescence. What is the point of 32-bit capability anyway?).
> >    Personally, I have written software for printing my catalogue using a
> >short form (when listing the titles on an album), in long form (when
listing
> >a complete album and printing details like matrix numbers, notes about
the
> >item, recording dates (translated from numeric into English, etc)), and
in
> >tabular form (for broadcasts, where it is important to see the stuff in
> >chronological order of first transmission, and either a "subtitle" or a
> >made-up "subtitle" to identify the programme unambiguously). In the
> >short-form case, dBase copies all the details into the next record (using
> >the word in its computer sense). So usually, one only needs to overwrite
the
> >title and the composer(s), when an album takes only a few minutes more
than
> >a "single".
> >    It is possible to sort or index upon any field or group of fields, or
> >upon characters within a field. The structure of my database includes
> >characters representing (for example) Western Art Music composers, solo
> >instruments, sound-effects, mono/stereo/quadraphonic, media format, etc.
The
> >only restrictions are (1) that a field is limited to 254 characters, so a
> >complete plot summary of a film is out of the question; (2) one database
> >cannot exceed 65536 records; and (3) the data is ASCII, so it loses the
> >diacriticals as Don Cox mentioned.
> >    Furthermore, it seems infinitely flexible for searching, using a
command
> >line such as :
> >loca for "Goon Show"$title .and. "1957"$recorded <CR>
> >At present, this kind of command-line does not seem to be provided on
> >software for the public to use, because users aren't accustomed to
logical
> >expressions (such as .and. .or. .not., etc).
> >    Yes, I am a "nerd"; and programmable databases are hated by IT
> >professionals because of the risk of viruses and other damage. But the
point
> >of this posting is that one should closely examine *what kind of person
you
> >are*, back up the data on another computer (for which dBaseII won't be
> >necessary), and do regular sorted printed catalogues of various forms.
> >    I was *given* a version of dBase called dBaseIII, but I've never
needed
> >to use it. But I suggest anyone used to reproducing obsolete audio-visual
> >formats might like to buy a second-hand legal version of dBaseII - and
its
> >instruction-book!
> >Peter Copeland
> >
> >-----Original Message-----
> >From: Don Cox [mailto:doncox@xxxxxxxxxxxxxx]
> >Sent: 15 December 2002 12:31
> >To: ARSCLIST@xxxxxxxxxxxxxxxx
> >Subject: Re: arsclist Cataloging
> >
> >On 14/12/02, Mwcpc6@xxxxxxx wrote:
> >
> >> It is remarkable that anyone connected with modern computers and
> >> computer science would mention using ASCII text files for anything.
> >> The mere thought of putting down a string of characters without a kb
> >> of formatting information must be appalling. The fact that anyone,
> >> anytime (even an alien with six fingers would still use binary
> >> numbers) could interpret it with just the ASCII code list.
> >
> >Your irony is appreciated. Actually, Linux uses ASCII files extensively.
> >
> >Plain ASCII cannot handle accented characters, which is a limitation for
> >music cataloguing. It's a pity Unicode was not around earlier in the
> >development of computers.
> >
> >The advantages of a database stored as a plain ASCII text file are
> >obvious - simple, robust, and easily edited without deep knowledge of
> >computers.
> >
> >The advantage of a properly set up database management system is that
> >you can ask for combinations such as "All recordings of Beethoven
> >symphonies conducted by Klemperer not with the Philharmonia". But
> >setting up and maintaining such a database needs a lot of well informed
> >planning, and the data entry must be done by expert staff, otherwise the
> >whole thing is worse than useless.
> >
> >The technology of setting up an SQL database with a web page as a front
> >end is well known. It's the planning, design and construction of the
> >database that is a mammoth effort.
> >
> >It could well be that not enough users would benefit to make the effort
> >worth while. In which case, ASCII files would do fine.
> >
> >Regards
> >--
> >Don Cox
> >doncox@xxxxxxxxxxxxxx
> >
> >
>
>**************************************************************************
> >
> >Free exhibitions at the British Library Galleries :
> >
> >50 Years of Number Ones : Listen to any one of over 930 pop music chart
> >toppers 1952-2002 (from 11 October)
> >
> >Magic Pencil : Children's Book Illustration Today (from 1 November)
original
> >graphic work of 13 contemporary artists
> >
> >*************************************************************************
> >
> >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.
> >
> >*************************************************************************
> >
> >-
> >For subscription instructions, see the ARSC home page
> >http://www.arsc-audio.org/arsclist.html
> >Copyright of individual posting is owned by the author of the posting and
> >permission to re-transmit or publish a post must be secured
> >from the author of the post.
> >
> >
>
> --
>
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Kevin P. Mostyn
>
> -
> For subscription instructions, see the ARSC home page
> http://www.arsc-audio.org/arsclist.html
> Copyright of individual posting is owned by the author of the posting and
> permission to re-transmit or publish a post must be secured
> from the author of the post.
>

-
For subscription instructions, see the ARSC home page
http://www.arsc-audio.org/arsclist.html
Copyright of individual posting is owned by the author of the posting and
permission to re-transmit or publish a post must be secured
from the author of the post.