Simple Database Builder
The standard Database Builder service enables the remote creation and editing of asset and ID databases stored on codeREADr’s servers. Currently this feature requires connectivity to the Internet via 3G/4G or Wi-Fi. Applications include:
You would use your primary event access control service to control entry to the event. When an attendee leaves, you can optionally scan their ticket with a separate Database Builder service. That service should be associated to the same database as the primary service. This will allow you to control re-entry to the event. Your app user would scan the departing attendee’s ticket and change the status from Invalid to Valid. In this way when the ticket is again scanned by the primary service it will be Valid. [Note: There are other ways to achieve this goal. Contact support if you have any questions.]
Scan the barcode value on an asset (or attach one, if there’s not one on it already) and then enter associated text to describe that asset – we call it ‘Response’ text. When that scan is submitted to our servers it is added to your asset database or, if the asset was already in there, then it will replace the Response text previously associated with it.
Asset Status – Condition / Location / Other
The process is the same as for Asset Tagging but here you would update (edit) the Response text to indicate the current condition or location of the asset.
- If you create your own barcode tags (labels) using 2D barcodes (e.g. QR, Data Matrix or PDF-417) and embed descriptive information in those barcodes, then the Response text can be used solely for status updates.
- Database Builder is ideal for many applications since it directly updates your asset or ID database. However, using a standard Recording service offers additional options. For example, you can have multiple form entries (manual entry and/or scan-to-enter) along with one or more multiple choice entries and also track the GPS location of each scan. However, this data does not update directly to your database; instead, you need to export the scan database, filter it and then merge it with your database.
1. External Database: If you already have a database hosted on your desktop, your own servers or other external databases, you can:
a) Export filter and share scan records in template form using the codeREADr ‘Scans’ page and then import those records into your external database(s).
b) Automatically insert scan records into those external databases. Please look here.
2. Hosted Database: If you want to use codeREADr’s servers to host a multi-column table of barcode data and allow the app user to view and edit the data in those columns, a more advanced Database Builder is available using our Postback feature. With that option your app-users can:
a) Create: Scan barcodes and enter select data to create records for each barcode in the codeREADr-hosted validation database; and then,
b) View and Edit: Subsequently scan those barcodes to update the previously entered data.
This Postback service is useful when you want the app-user to see and simultaneously update the last known status, location, etc. of the item scanned. Please look here for detailed instructions. [Note: Ask about our new Scan Builder option which will be available early in Q1/2017.]