Perian,
I believe bar coding works best when the database generates a random
number for each location, object, component and container.
The bar code number stays with the location, object etc for it's life
in the database. It's best to use a bar code number that is untouched
by human hands just like your objects have a hidden inventory#
different than the accession#.
You will run into problems eventually if you create bar codes from
the accession#s and the location and container names (duplication and
humans changing accession#s etc).
Your labels can print both the bar code and the human readable text
to enable identification by staff and the database. I set our labels
up to print the bar code, the bar code# and the text (accession#,
location or container name).
Finally, use the same bar code format for everything you are bar
coding (IE: code 39 or codabar or 128). If you mix bar code formats
you are asking for complexity and problems you don't need.
Bar codes are a big subject that I've just touched lightly on here.
I'll be glad to answer specific questions or I can send you a
powerpoint presentation I did on bar codes at MCN a few years ago.
The Yale University Art Gallery and the Yale Center for British Art
both use TMS, which has bar code functionality built into the
database as discussed above (TMS uses the 128 code).
David Parsell
david.pars...@yale.edu
The Yale University Art Gallery and the Yale Center for British Art
At 05:18 PM 3/23/2006, you wrote:
Hi everyone:
So, along with everything else we're doing, we're setting up a barcode
tracking system. My boss and I have different theories on how this should
work, but we're agreed that there should be 2 to 3 levels of codes:
1) Storage compartment: in our case, the first shelf (1) in one of a number
of flat files (FF1) in the rare books room (RBR) could be coded RBR FF1 1
(Code 39)
2) Container: a solanger box or folder containing a number of items -
example, B1, B2 (for boxes), F1 (for folder), etc. short codes (Code 39)
3) Item level: a bar code for individual items. (probably currently Codabar
format) Here is where our theories differ.
A year or so ago, a bunch of (more or less) sequential bar code numbers were
generated (ex. 000125, 000126), and applied to objects being moved
offsite. Perhaps 150-200 objects were given these codes and they were
designed to be temporary (the reasoning being that if a number fell off, you
could just stick a different number on it). After doing some research, I
learned about Code 39 and its ability to allow us to create a code for the
existing accession numbers.
I believe that it would be better to use Code 39 and make the Item Level
numbers human readable, so that the code is merely a way for the machine to
know immediately which accession number is where, rather than having to
cross reference a string of numbers to an accession number. My boss is of
the opinion that it's easier to print out a page of sequential numbers and
randomly assign a number to an object and that it won't matter, because the
database software (EMu) will understand it. I think this will be more of a
headache in the long run, especially if a tag gets lost or you're looking at
an object and wondering what it is, not to mention adding another number to
an object which already has a number assigned to it.
So I'm curious as to how your instituion deals with barcoding and
inventories, particularly at the item-level. Would assigning random numbers
be just as effective as using the accession number, especially given the
potential time savings involved with not having to print out individual
accession numbers?
Thanks!
Perian Sully
Collection Database Records Administrator
Judah L. Magnes Museum
2911 Russell St.
Berkeley, CA 94705
510-549-6950 x 335
You are currently subscribed to MCN-L, the listserv of the Museum Computer
Network (www.mcn.edu). To post messages to this list, send emails to:
mcn-l@mcn.edu
To unsubscribe from this list, please send an email to
mcn-unsubscr...@lists.mediatrope.com with any message.
If you are receiving messages as they are posted and wish to change to daily
digest format, send an email to listser...@lists.mediatrope.com with SET
mcn-l DIGEST in the BODY of the message.
If you are receiving messages in the daily digest format and wish to recieve
them as they are posted, send an email to listser...@lists.mediatrope.com with
SET mcn-l MAIL
You are currently subscribed to MCN-L, the listserv of the Museum Computer
Network (www.mcn.edu). To post messages to this list, send emails to:
mcn-l@mcn.edu
To unsubscribe from this list, please send an email to
mcn-unsubscr...@lists.mediatrope.com with any message.
If you are receiving messages as they are posted and wish to change to daily
digest format, send an email to listser...@lists.mediatrope.com with SET
mcn-l DIGEST in the BODY of the message.
If you are receiving messages in the daily digest format and
