Thanks Chad --
That makes sense, and I was a bit perplexed when we discovered that 2010 wasn't creating entries in BCLabels until the manager was run.
-Scott
From: "The Museum System (TMS) Users" on behalf of Chad Petrovay
Reply-To: "The Museum System (TMS) Users"
Date: Friday, August 28, 2015 at 2:50 PM
To: "[log in to unmask]<mailto:[log in to unmask]>"
Subject: Re: BC LabelUUID hash
Christine, Yes you can grab this for reports. The table should be BCLabels, and you join using the ID and TableID, but be sure to join via OBJComponentID = ID AND TableID = 94. And remember that If you are trying to turn these into readable barcodes (using a font like Code 39), then you may need to perform additional transforms to the LabelUUID string to make it actionable (in the case of Code 39, I believe it requires adding * to the beginning and end of the string.)
Scott, I don't remember which release the change was made to (which is why I said "newer"), but it was added so that institutions could leverage barcodes from TMS, without being tied to the BarCode Manager application. It also helps Barcode Manager run quicker, because the user no longer has to wait while the manager checks and generates barcodes for components/locations/crates without one.
~Chad
On Fri, Aug 28, 2015 at 2:38 PM, Williams, Scott <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Hi Chad --
I think I see what you are saying but I just want to clarify. I was testing this in TMS 2010 SP2 which is what prompted by email to the list-serv. When I create a component (but before I run the BacCode Manager utility) I do see that a BCLabel UUD value is generated in the Components screen. In this case I created the component amf_ag_bc_1.
[cid:12D4ABCA-3765-4837-B50D-F1298E220B19]
However, there is no corresponding entry in the BCLabels table for this component or labeluuid until I run BarCode Manager and then it inserts rows into BCLabels for all components, crates and locations which does not exist in that table.
However, when I just tried running this process again in TMS 2012 SP2 it does create an entry in the BCLabels table without needing to open and run the BarCode Manager utility. I've been reviewing the release notes for TMS 2012 over the last weeks and may have missed this. If anyone knows specifically what version TMS 2012, SP1 or SP2 this changed that would be very helpful to know.
Many thanks --
Scott
From: "The Museum System (TMS) Users" on behalf of Chad Petrovay
Reply-To: "The Museum System (TMS) Users"
Date: Friday, August 28, 2015 at 2:10 PM
To: "[log in to unmask]<mailto:[log in to unmask]>"
Subject: Re: BC LabelUUID hash
Scott, The newer versions of TMS automatically produce a BCLabel UUID when a component, location or crate is added to the system. There is a configuration value that allows you to turn that functionality off - in case you use preprinted barcode tags. If there is a Barcode field displayed on the ObjComponent screen, then you have this existing functionality.
~Chad
On Fri, Aug 28, 2015 at 1:57 PM, Williams, Scott <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Hi --
Has anyone generated their own barcode hash values (BCLabels.LabalUUID field)? We are developing a mobile application for barcode scanning and will likely need to build a software component to generate a hash value from the (TableID + primary key) and I was curious if anyone knows the algorithm that the BarCode manager uses to generate the hex(?) value for LabelUUID.
Just curious..
Thanks
Scott
--
Scott Williams
Data & Database Administrator
Yale University Art Gallery
[log in to unmask]<mailto:[log in to unmask]>
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.