Creating a Database
The “Validation Database” is used for two primary reasons:
- Enable your app-users to check if the value of a scanned barcode (or an NFC tap, manual entry, search entry, etc.) exists in that database. If it does, it will return a Valid message to the app user and any related information (the ‘Response’ text). If the value is not in the database it will return an Invalid message.
- Enable your app-users to see information specifically related to the scanned barcode value immediately after each scan. In the Response you can show them plain text, structured text, HTML and web content to help them in their assigned task.
Example use cases:
- Tickets with barcodes scanned will be matched to determine authenticity
- Check if an item or asset exists in the database and show a description
- Verify if a member, student or employee’s ID is valid and optionally their photo
To create a database CSV file in the correct format, please click here for formatting instructions.
- You do not need to use barcodes generated by codeREADr. Most clients use their own barcodes and simply upload the barcode values (IDs) to our servers or keep them on their own servers for validation.
- Depending on your use case, multiple Services can be associated with a single database. However, a Service can only have one associated database. This distinction is particularly important when checking for duplicate scans because checking if a scan is a duplicate or not is by Service, not the associated database.
- You can scan barcodes with hundreds of characters embedded in them. However, automatically we limit the barcode value in the database to 100 characters. To validate a scanned barcode value greater than 100 characters you’ll need to use our Alter Scan Value feature (Example D).
Step by Step Creation
The first step to creating a database is clicking the Databases link in the navigation bar on the CodeREADr website.
Second, click the Create Database button on that page.
Third, you will want to enter a name for your Database. Make it something descriptive, that way you will know which service it must be attached to. Now, click Create Database and it will be generated.
Which One To Use
Adding the values manually is the most straightforward way to add to a database, but it won’t always be time efficient to do so. Adding values this way can be done at any time, even after importing values from a file or auto filling them.
Importing the values from a CSV or TXT file will be useful if the code values exist somewhere already. It is important to have the file properly formatted, though. For example, one value is assigned to one response (description). These would be read by the app from your entries in column 1 and column 2, respectively. Click here for a guide to formatting.
Auto-fill is a good option if you want to generate values for your barcodes, that will then be used to print these codes. After filling the database, export a CSV file full of these values and codes, and send them to be printed. If you already have codes you want to scan, do not use auto-fill.
After filling the database with values, you will now have a database that can be validated against.
- Uploading a CSV file and adding it to an existing database will not erase the old values in that database. If the value is already in the database, it will not be removed. If any of the data in column 2 or 3 changes for that value, it will be updated.
- To add values to an existing database you can add those values to your original CSV file and then import that new file. Alternatively, you can create a new CSV file with just the new values and import that. The new values will be added to the database.
- To totally replace the values in a database with a new set of values, clear the database and import a new CSV file.
Navigating to the Clear tab will bring you to this page.
Be careful. Once a database has been cleared, its values will not be recoverable.
If you’re intention is to check and invalidate duplicate scans, that is done when creating the Service associated to the database. It is not done here in the Database section because the status of a duplicate scan is based on scans done for the Service, not the database.
Settings exist to invalidate duplicate scans, under the Type tab when editing Services. They can be reset based on a specific period (e.g. daily).