Handling ID Suffix Issues

Overview

Documentation for the IT Service Desk to handle ID Card Suffix issues. ID cards are encoded with information in the magnetic strip when they are produced. This information includes the nine-digit ID number printed on the card and a two-digit issuance code (or suffix) not printed on the card. When the suffix encoded on the card does not match what is in other systems that the card may be used for (e.g. dining, card-swipe door access, card-swipe authentication to printers) the owner of the card will not be able to successfully access those services with the card.

Description

1. Confirm what is encoded on the card by using a card reader. This is best done inside the appropriate field of the ID Suffix incident form.
   • The card reader should output an 11-character string of numbers, depending on how the reader is programmed. 
   • Special characters (e.g.;,?) can be ignored, but should not be removed from the incident form should the card reader output them. These characters are left over from encoding the card readers with special functions such as carriage returns
2. Fill out the rest of the ID Suffix incident form for later reference. 
3. Update Touchnet OneCard with the correct Suffix
   • Accounts management on the left navigation pane
   • Create/Edit Account
   • Edit Account
   • Paste the ID number into the search criteria field
   • Confirm the record is for the correct user
   • Update the Suffix Field to the last two digits output by the card reader, ignoring special characters (e.g. 02)
   • Save
     • CBORD (Dining Services) should update within 15 minutes
     • PawPrint and CCURE (Door Access) update daily
4. If OneCard already has the correct suffix listed
   • ​​​​​​​Issues with Dining should be directed to Dining Services 
   • Issues with door locks should be directed to Campus Police
   • Issues with PaperCut (PawPrint) can be handled by the service desk)