MUSEUM-L Archives

Museum discussion list

MUSEUM-L@HOME.EASE.LSOFT.COM

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gary Acord <[log in to unmask]>
Reply To:
Museum discussion list <[log in to unmask]>
Date:
Mon, 2 Jun 1997 20:09:57 UT
Content-Type:
text/plain
Parts/Attachments:
text/plain (53 lines)
there's certainly nothing wrong with concatenating fields to arrive at a key.
and if anyone looks into a RDMS that can't handl multiple key indexes like Mr.
Baron described then they should look elsewhere.
we should also talk about backing up data files if we launch into digital
disasters.  anyone that is depending on there database should be keeping
regular backups of ALL of there data files, whether it's just one Access file
or  a hundred MS SQL Server tables etc.
my general recommendation is one tape(or better media) for each day of the
week.  and be very religious about changing it each day.

Gary Acord
Acord Information Management
[log in to unmask]

-----Original Message-----
From:   Museum discussion list  On Behalf Of Robert A. Baron
Sent:   Monday, June 02, 1997 7:06 AM
To:     [log in to unmask]
Subject:        Re: Catalogue numbering

At 04:27 AM 6/2/97 UT, Gary Acord wrote:
>EXACTLY, i'm certainly not saying that you must change old numbers. my god,
>what an effort!  those with alpha characters in the number may pose an
>intriguing problem depending on how the system is set up to handle the unique
>field.  but nothing that can't be overcome from the db design point of view.
>just to reiterate my opinion, let's get off of relying on those numbers to
>reflect something useful in terms of information.  since we can sort and
>filter and query data in so many ways now in order to make useful information
>out of it, we shouldn't care how the records are individualized.  AS LONG AS
>THEY ARE.

There is a reason not yet mentioned why museums should try to use, whenever
possible, traditional accession numbers as the joining field in relational
databases.  If, heaven forfend, a vital link file gets ruined or some other
digital disaster strikes, at least the accession number can be used to
rebuild the system.  If arbitrary numbers are used relinking can be nearly
impossible.

Accession numbers, however, because of their variety and because they may
need to be processed in parts, can be difficult to use as joins.  In one
database I built the accession number was actually a concatenation of four
fields that were used for selection and sorting.  Links to the accession
number were created by defining the four fields as a cluster of fields and
indexed and linked as a group.  Not every database can do this, however.




===========================
Robert A. Baron
Museum Computer Consultant
mailto:[log in to unmask]

ATOM RSS1 RSS2