TracCloudMigration and TracCloudTechBarcode: Difference between pages

From Redrock Wiki

(Difference between pages)
No edit summary
 
No edit summary
 
Line 3: Line 3:
| style="vertical-align:top; padding:20px 20px 20px 2px;" |
| style="vertical-align:top; padding:20px 20px 20px 2px;" |
{| style="width:100%; vertical-align:top; "
{| style="width:100%; vertical-align:top; "
<onlyinclude>
<big><b>Barcode Scanners in TracCloud</b></big><br><br>
Barcode Scanners and Magnetic Strip Reads can be utilized in Trac Cloud to allow students to scan their Barcode, ID, etc to login for their visit. This article goes over some common barcode scanner examples, your barcode scanner may or may not match the formatted described below.
<br><br>
If it doesn’t match, or you simply aren’t 100% sure, reach out [mailto:helpdesk@go-redrock.com helpdesk@go-redrock.com] and we’d be happy to assist.
<br><br>
<b><i>What scanners are compatible with TracCloud?</b></i><br>
Scanners are input devices, just like keyboards. Any scanner should work fine, but may require some editing to convert the data into something usable.
<br><br>
<b><i>Program your card scanner to modify the scanned ID</b></i><br>
It may be easier to convert IDs on the scanner side of this process rather than TracCloud. If this option is available and the end result matches what is found in student barcode fields, then no changes are needed in TracCloud.
<br><br>
<b><i>Program TracCloud to modify the scanned ID</b></i><br>
If reprogramming the scanner isn’t an option or you would rather leave it as-is, you can have TracCloud handle the conversion for you.
<br>
<i>Other > Other Options > Preferences > General KIOSK Login Options</i>
[[File:7k6k67kl56k56kj56jk.png|800px]]
<br><br>
* <b>Barcode Detection Formula</b>
::If the format of the entered text matches this formula, the Barcode Adjust logic will be used. The asterisk is a wildcard, so in the example above, we’re saying “if the value entered on the log listing starts with a semi-colon and ends with a question mark, it’s a barcode scan, and we should apply the Barcode Adjust script.”


==Migrating from Trac 4.0 to TracCloud==
* <b>Barcode Adjust</b>
::Transforms the text from the barcode scanner into something that matches the student barcode fields.


<big><b>Step 1. Planning out the migration process</big></b>
* <b>KIOSK No student found message</b>
::The message displayed when a student isn’t found.
::[[File:Ewrh57kj64htr.png|500px]]


Schedule a call with us to put together a plan and schedule for the following steps.
==Configuring your Barcode Scanner==
<hr>
Start by scanning a student’s ID into a document on your computer. This will show you what the formatting of the ID will be, then you can start deciding what adjustments need to be made.
<big><b>Step 2. IT Integrations</big></b>
 
We will be working with your IT throughout steps 3 and 4 to integrate your campus services with TracCloud. This includes:
 
:[https://wiki.go-redrock.com/index.php/TracCloudTechMail Setting up your mail server]
 
:[https://wiki.go-redrock.com/index.php/TracCloudTechImport Importing data from your SIS]
 
:[https://wiki.go-redrock.com/index.php/TracCloudTechSSO Integrating your campus single sign-on]
 
:[https://wiki.go-redrock.com/index.php/TracCloudTechURL Using a custom URL]
 
:[https://wiki.go-redrock.com/index.php/TracCloudTechBarcode Configuring barcode scanners]
 
:Getting a copy of your Trac 4.0 database for steps 3 and 5 (if not hosted).
<hr>
<big><b>Step 3. First migration</big></b>
 
This first migration will bring much of your data into TracCloud. This is also the point where you will no longer be able to apply changes to your Trac 4.0 instance outside of the basics like Visits, Appointments, and Resource Checkouts.


For the examples below, the student’s ID is 1931.
<hr>
<hr>
<big><b>Step 4. SysAdmin Training</big></b>
During the initial SysAdmin trainings, we will go over the following topics (in roughly this order):
1st Training: Creating Centers, Reasons, and the start of your Profile Prefs.
2nd Training: Profile Prefs.
3rd Training: Creating Groups, Staff (aka Users/Consultants), and Course Lists.
4th Training: System Prefs such as Custom Fields, Welcome Messages, and Confirm bio options.
5th Training: Setting up modules (if applicable).
<hr>
<big><b>Step 5. Final migration</big></b>
This step is where we bring over the remaining data from your Trac 4.0 instance, the visits, appointments, etc that you've created since the first migration. This is also the step where your Trac 4.0 instance will be shutdown, as any further recorded data will not be brought into TracCloud.
<hr>
<big><b>Step 6. Continued Training</big></b>
After the final migration has been completed, we can go back to the basics to ensure you're comfortable using the system.
6th Training: Logging visits, using quick and batch visit utilities.
7th Training: Creating schedules and booking appointments.
8th Training: Running reports (typically a few weeks after going live).
<hr>
==What data will be migrated?==
<b><i>What does it mean if something is included in the first migration, but not the second?</i></b>
:This indicates that the data will be brought over, but any modifications made to your Trac 4.0 data relating to this field will not be carried over into the final TracCloud migration. For example, if you create a center after the first migration, it and any associated data will not be brought over.
<b><i>What does it mean if something is included in the first *and* second migration?</i></b>
:This indicates that on top of being available during the training process, it will also overwrite any existing data that was created in TracCloud during the training process. For example, if you log visits during the training process (prior to second migration), this data will be lost after said second migration.
<b><i>What does it mean if something isn't migrated at all?</i></b>
:This means the data simply won't be brought into TracCloud, and will need to be (re)created manually. This typically occurs where significant changes are seen, such as your profile prefs and permission groups, where few 1-to-1 options are found.
{| class="wikitable"
{| class="wikitable"
! Trac 4.0 Data !! Included in First Migration? !! Included in Second Migration?
|-
|-
| Profiles || <span style="color:green">Yes</span> || <span style="color:red">No</span>
! Barcode Scanner Contents !! Barcode Detection Formula !! Barcode Adjust
|-
| Profile Prefs || <span style="color:red">No</span> || <span style="color:red">No</span>
|-
| System Prefs || <span style="color:red">No</span> || <span style="color:red">No</span>
|-
| Centers/Subcenters || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-
|-
| ABCDEF1931|| {#scan#}='ABCDEF*' || {#WORD:{#scan#}:2:'ABCDEF'#}
|}


| Groups || <span style="color:red">No</span> || <span style="color:red">No</span>
In this example, we want to remove a static string of characters from the left side.
|-


| Consultants || <span style="color:green">Yes</span> || <span style="color:red">No</span>
The Detection Formula recognized a barcode scan because it starts with the string of characters we want to remove. The Adjust script says “Get the second word in the string, delimited by “ABCDEF.” The result is “ABCDEF1931” turning into just “1931.
|-
<hr>
| Users (e.g., SysAdmin accounts) || <span style="color:red">No</span> || <span style="color:red">No</span>
{| class="wikitable"
|-
| Students || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Faculty || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
|-
| ;1931000000? || {#scan#}=';*?' || {#SUBSTR:{#scan#}:1:4#}
|}
In this scan, we’re unable to use any character as a delimiter, so we need to count out the characters we actually need with a Substring script.


| Reasons || <span style="color:green">Yes</span> || <span style="color:red">No</span>
The Adjust script is taking the scan, starting at character 1 and taking the following 4 characters. This is 0-based, so “0” would be the semicolon in the example scan.<br><br>
|-
<hr>
| Registrations || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
{| class="wikitable"
|-
| Courses || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Sections || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Class Schedules || <span style="color:red">No</span> || <span style="color:red">No</span>
|-
 
 
| Visits || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Appointments || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Availabilities || <span style="color:red">No</span> || <span style="color:red">No</span>
|-
 
| Static Student Lists || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
|-
| Dynamic Student Lists || <span style="color:red">No</span> || <span style="color:red">No</span>
| 1931 || N/A || N/A
|-
| Documents || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Messages || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Resources || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-
| Resource Checkouts || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
 
| SAGE Referral Types || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-
| SAGE Referrals || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| SurveyTrac Surveys || <span style="color:green">Yes</span> || <span style="color:red">No</span>
|-
| SurveyTrac Responses || <span style="color:green">Yes</span> || <span style="color:green">Yes</span>
|-
| Q2 Configs || <span style="color:red">No</span> || <span style="color:red">No</span>
|-
| Whiteboard Rooms || <span style="color:red">No</span> || <span style="color:red">No</span>
|}
|}
 
No changes needed.
 
<hr>
 
</onlyinclude>
|}
|}
{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}}
{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}}
[[Category:rsc_internal]]

Revision as of 16:03, 5 October 2021


Barcode Scanners in TracCloud

Barcode Scanners and Magnetic Strip Reads can be utilized in Trac Cloud to allow students to scan their Barcode, ID, etc to login for their visit. This article goes over some common barcode scanner examples, your barcode scanner may or may not match the formatted described below.

If it doesn’t match, or you simply aren’t 100% sure, reach out helpdesk@go-redrock.com and we’d be happy to assist.

What scanners are compatible with TracCloud?
Scanners are input devices, just like keyboards. Any scanner should work fine, but may require some editing to convert the data into something usable.

Program your card scanner to modify the scanned ID
It may be easier to convert IDs on the scanner side of this process rather than TracCloud. If this option is available and the end result matches what is found in student barcode fields, then no changes are needed in TracCloud.

Program TracCloud to modify the scanned ID
If reprogramming the scanner isn’t an option or you would rather leave it as-is, you can have TracCloud handle the conversion for you.
Other > Other Options > Preferences > General KIOSK Login OptionsFile:7k6k67kl56k56kj56jk.png

  • Barcode Detection Formula
If the format of the entered text matches this formula, the Barcode Adjust logic will be used. The asterisk is a wildcard, so in the example above, we’re saying “if the value entered on the log listing starts with a semi-colon and ends with a question mark, it’s a barcode scan, and we should apply the Barcode Adjust script.”
  • Barcode Adjust
Transforms the text from the barcode scanner into something that matches the student barcode fields.
  • KIOSK No student found message
The message displayed when a student isn’t found.
Ewrh57kj64htr.png

Configuring your Barcode Scanner

Start by scanning a student’s ID into a document on your computer. This will show you what the formatting of the ID will be, then you can start deciding what adjustments need to be made.

For the examples below, the student’s ID is 1931.


Barcode Scanner Contents Barcode Detection Formula Barcode Adjust
ABCDEF1931 {#scan#}='ABCDEF*' {#WORD:{#scan#}:2:'ABCDEF'#}

In this example, we want to remove a static string of characters from the left side.

The Detection Formula recognized a barcode scan because it starts with the string of characters we want to remove. The Adjust script says “Get the second word in the string, delimited by “ABCDEF.” The result is “ABCDEF1931” turning into just “1931.”


;1931000000? {#scan#}=';*?' {#SUBSTR:{#scan#}:1:4#}

In this scan, we’re unable to use any character as a delimiter, so we need to count out the characters we actually need with a Substring script.

The Adjust script is taking the scan, starting at character 1 and taking the following 4 characters. This is 0-based, so “0” would be the semicolon in the example scan.


1931 N/A N/A

No changes needed.