Actions

Sending parsed DL-ID data to CM: Difference between revisions

From Convention Master Documentation

No edit summary
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 2: Line 2:


This document attempts to create a standard so either mobile applications, or hardware imagers can be programmed to send the needed DL/ID information to CM, in a way that is universal and easy to understand.
This document attempts to create a standard so either mobile applications, or hardware imagers can be programmed to send the needed DL/ID information to CM, in a way that is universal and easy to understand.
Note, any field concatenation should be done on the server side, and blank fields are allowed, and will be ignored by the server side parser.


== V1 Data String ==
== V1 Data String ==
Line 11: Line 13:
|+ V1 Data String Breakdown and Explanation
|+ V1 Data String Breakdown and Explanation
|-
|-
! Data String !! AAMVA field !! Notes/Definition
! Data String !! AAMVA field !! Field Information !! Notes/Definition
|-
|-
| V1 || N/A || Version String
| V1 || N/A || !V followed by up to 3 numbers || Version String
|-
|-
| firstname || DAC || First name of the cardholder.
| firstname || DAC || Up to 40 Chars ANSI Text || First name of the cardholder.
|-
|-
| lastname || DCS || Family Name of the Cardholder
| lastname || DCS || Up to 40 Chars ANSI Text || Family Name of the Cardholder
|-
|-
| suffix || DCU || Name Suffix (Issuer Optional)
| suffix || DCU || Up to 40 Chars ANSI Text || Name Suffix (Issuer Optional)
|-
|-
| dateofbirth || DBB || CM Expected format is CCYYMMDD, format on license may be MMDDCCYY or CCYYMMDD, Reader must convert
| dateofbirth || DBB || 8 Characters Numbers Only || CM Expected format is CCYYMMDD, format on license may be MMDDCCYY or CCYYMMDD, Reader must convert
|-
|-
| address1 || DAG || Street Portion of Address
| address1 || DAG || Up to 35 Chars ANSI Text || Street Portion of Address
|-
|-
| address2 || DAH || Second Line of Address (Issuer Optional)
| address2 || DAH || Up to 35 Chars ANSI Text || Second Line of Address (Issuer Optional)
|-
|-
| city || DAI || City Portion of Cardholder Address
| city || DAI || Up to 20 Chars ANSI Text || City Portion of Cardholder Address
|-
|-
| state || DAJ || State Portion of the Cardholder Address
| state || DAJ || 2 Chars ANSI Text || State Portion of the Cardholder Address
|-
|-
| postalcode || DAK || Postal Code, includes zip+4 for US
| postalcode || DAK || Up to 11 Chars ANSI Text || Postal Code, includes zip+4 for US
|-
|-
| country || DCG || Country the Card is issued in
| country || DCG || 3 Chars ANSI Text || Country the Card is issued in
|-
|-
| <enter> || N/A || Send the Enter Key when done reading.
| <enter> || N/A || N/A || Send the Enter Key when done reading.
|}
|}
==Pre-Built Configuration Files for Zebra Imagers==
* These configuration files should work on any Zebra USB scanners that can support DL/ID scanning.
[https://leho.blastpuppy.com/cm-ref/DS4208-DS6708-Config.pdf Pre Made DS4208/DS6708 Config File]
[https://leho.blastpuppy.com/cm-ref/Config_File_DS4208_DLID_Decode_2023.02.25.scncfg Scan123 Config File for DS408 (works on DS6708)]


==Reference Documents==
==Reference Documents==
[https://www.aamva.org/assets/best-practices-guidance/dl-id-card-design-standard AAMVA DL/ID Card Design Standard]
[https://www.aamva.org/assets/best-practices,-guides,-standards,-manuals,-whitepapers/aamva-dl-id-card-design-standard-(2020) AAMVA DL/ID Card Design Standard]


[https://www.zebra.com/us/en/support-downloads/scanners/general-purpose-scanners/ds6708-dl.html Support Page to obtain product reference guide for DS6708]
[https://www.zebra.com/us/en/support-downloads/scanners/general-purpose-scanners/ds6708-dl.html Support Page to obtain product reference guide for DS6708]

Latest revision as of 07:29, 12 March 2023

When trying to implement reading of DL/ID barcodes we realized a way to pass the information to CM in a machine parsable way that was easy to send via a web browser without add-on software was needed.

This document attempts to create a standard so either mobile applications, or hardware imagers can be programmed to send the needed DL/ID information to CM, in a way that is universal and easy to understand.

Note, any field concatenation should be done on the server side, and blank fields are allowed, and will be ignored by the server side parser.

V1 Data String

!V1!firstname!lastname!suffix!dateofbirth!address1!address2!city!state!postalcode!country<enter>

For more information about the AAMVA field, see Annex D of the AAMVA DL/ID Card Design Standard

V1 Data String Breakdown and Explanation
Data String AAMVA field Field Information Notes/Definition
V1 N/A !V followed by up to 3 numbers Version String
firstname DAC Up to 40 Chars ANSI Text First name of the cardholder.
lastname DCS Up to 40 Chars ANSI Text Family Name of the Cardholder
suffix DCU Up to 40 Chars ANSI Text Name Suffix (Issuer Optional)
dateofbirth DBB 8 Characters Numbers Only CM Expected format is CCYYMMDD, format on license may be MMDDCCYY or CCYYMMDD, Reader must convert
address1 DAG Up to 35 Chars ANSI Text Street Portion of Address
address2 DAH Up to 35 Chars ANSI Text Second Line of Address (Issuer Optional)
city DAI Up to 20 Chars ANSI Text City Portion of Cardholder Address
state DAJ 2 Chars ANSI Text State Portion of the Cardholder Address
postalcode DAK Up to 11 Chars ANSI Text Postal Code, includes zip+4 for US
country DCG 3 Chars ANSI Text Country the Card is issued in
<enter> N/A N/A Send the Enter Key when done reading.

Pre-Built Configuration Files for Zebra Imagers

  • These configuration files should work on any Zebra USB scanners that can support DL/ID scanning.

Pre Made DS4208/DS6708 Config File

Scan123 Config File for DS408 (works on DS6708)

Reference Documents

AAMVA DL/ID Card Design Standard

Support Page to obtain product reference guide for DS6708

Retrieved from "https://docs.civetsolutions.com/index.php?title=Sending_parsed_DL-ID_data_to_CM&oldid=725"