[racktables-users] Re: survey: barcodes versus asset tags
- From: "Winters, Jeremy" <jwinters@xxxxxxxxxxxxxxxx>
- To: <racktables-users@xxxxxxxxxxxxx>
- Date: Thu, 9 Jul 2009 09:34:38 -0400
We store 1 value in "asset tag" column only.
Awesome software btw!
-Jeremy
-----Original Message-----
From: racktables-users-bounce@xxxxxxxxxxxxx
[mailto:racktables-users-bounce@xxxxxxxxxxxxx] On Behalf Of Denis
Ovsienko
Sent: Thursday, July 09, 2009 9:22 AM
To: racktables-users@xxxxxxxxxxxxx
Subject: [racktables-users] survey: barcodes versus asset tags
Hello, list.
There are two columns for each object: "asset tag" and "barcode". There
is also a story behind them. Long time ago the initial implementation of
RackTables had to serve a hardware base, which was accounted by two
independent systems at once (don't ask me, why). One system used labels
without a barcode, and another --- labels with barcode. So at that time
I added two fixed columns into SQL table and that did the trick. Later
it became obvious, that enterprises normally employ only one asset
accounting systems, but the columns were already there, and user's data
also was. So I left things as was.
Now I consider dismissing the "barcode" column in favor of "asset
tag" this year. There are ways to handle existing data:
1. Append the contents of "barcode" to "asset tag".
2. Create an optional "barcode" attribute and move the "barcode" fixed
column data there.
3. Something else, perhaps.
To make the right decision, it is necessary to know, how you,
RackTables users, use these columns. Could you choose, which answer
describes your case best?
- I don't store values in either "barcode" or "asset tag" columns
- I store 1 value in "barcode" column only
- I store 1 value in "asset tag" column only
- I store values in both "barcode" and "asset tag" columns, they are
different
- I always store the same value in both "barcode" and "asset tag"
columns
Thank you in advance.
--
Denis Ovsienko
***CONFIDENTIALITY NOTICE***
The information in this email may be confidential and/or privileged. This email
is intended to be reviewed by only the individual or organization named above.
If you are not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any review, dissemination or
copying of this email and its attachments, if any, or the information contained
herein is prohibited. If you have received this email in error, please
immediately notify the sender by return email and delete this message from your
system.
Other related posts:
