Extending MagStripe Data to Decision Making on the Handheld

Scanning Devices Magstripe Data Collection System (available off-the-shelf) reads data from the magnetic stripe on cards, saves it in the Palm Handheld database and transfers it to PC on a hot-sync. Data moves in one direction only. No decisions are made in the Palm Handheld at the time the card is read.

Extensions to this application pre-load the Palm application and database with data on which to make a decision when and where a card is read. An example might be "Is the card-holder authorized to enter?"

In order to answer that question, some criteria must be established in the Palm Handheld. Four ways to formulate the criteria are described here.

• The general format of the card; ie, "Is there a 10-digit student ID starting in 'A' and ending in 'B'? or Is there an authorization code 'ABC' in the first field of track 1?".

  This requires a Palm Handheld application that
  

  • 1. reads the card
  • 2. compares data to the criteria
  • 3. reports the result, go or no-go, and optionally
  • 4. save the data for later hot-sync to PC.

  There is no requirement for a Palm Handheld database to make the decision as it is based only on the format of the card data.

  This application requires that the criteria is defined.
  
  

• A variation on this application displays the card data and requires the user to make the "go, no-go" decision.

  This variation requires that the data display is defined.
  
  

• The general format of the card and previously read cards; ie, "Is there a valid student ID on the card (YES) and has this card already been presented at for this event (NO)?".

  The same four steps as in #1 occur on reading a card. In addition, step 2 requires that the application search the database of cards previously read on this Palm Handheld to insure that the data is not duplicated. If, in this example, the student ID read from the card is found in the database, then the application should report that result.

  The application requires that the criteria is defined and must have a means to define the beginning and end of the duplicate period.
  
  

• An authorization database in the Palm Handheld; ie, "Is this cardholder on the list?".

  The same four steps as in #1 and #2 occur on reading a card. Additional preparation and processing is required to build and maintain the authorization database. This may be done in a spreadsheet on PC and hot-sync'ed to the Palm Handheld. A typical application might have multiple lists on the Palm Handheld with a facility (a list of lists) to let the user select which list is searched to make the decision.

  This application requires coordination of Palm and PC in order to build and maintain the authorization lists and a means to select the list to be used for specific events. Careful definition and design makes the application easy to use and effective.

Contact us to review your application requirements.

Scanning Devices Inc.
Phone: 781-272-5135
Fax: 781-272-4856
Email: mail@scanningdevices.com

Home Page | Application Stories | Product Information | News | Trade Shows