[racktables-users] Betr.: survey: barcodes versus asset tags

Hello Denis,
 
Currently we are using option 3:
- I store 1 value in "asset tag" column only
 
Regards,
Joep

>>> Denis Ovsienko <pilot@xxxxxxxxxx> 9-7-2009 15:21 >>>
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


###################################################################

* * *   D I S C L A I M E R   * * *

###################################################################

De informatie in dit e-mailbericht is vertrouwelijk en uitsluitend bestemd voor 
de geadresseerde. Wanneer u dit bericht per abuis ontvangt, gelieve 
onmiddellijk contact op te nemen met de afzender per kerende e-mail. Wij 
verzoeken u dit e-mailbericht te vernietigen en de inhoud ervan aan niemand 
openbaar te maken. Afzender aanvaardt geen enkele aansprakelijkheid voor 
onjuiste, onvolledige dan wel ontijdige overbrenging van de inhoud van een 
verzonden e-mailbericht, noch voor door haar daarbij overgebrachte virussen.

The information contained in this e-mail is confidential and may be privileged. 
It may be read, copied and used only by the intended recipient. If you have 
received it in error, please contact the sender immediately by return e-mail. 
Please delete this e-mail and do not disclose its contents to any person. 
Sender does not accept any liability for any errors, omissions, delays of 
receipt or viruses in the contents of this message which arise as a result of 
e-mail transmission.

Other related posts: