Verifying User as A Student

This feature will take information provided by the user, send it to the back-end, query one of two databases for existence, and then return whether or not the user is a student at the school they claim to be enrolled in.

In order to query the appropriate database, the user must have provided two pieces of information: their enrolled school, and their student ID number. It may be possible to locate the “R-number” for Rollins University without needing the enrolled school field, but this may not be the case for all schools. To allow maximum room for expansion, it would be best to require both types of data.

In the beginning, we will also need the users to have pressed the submit button to begin the validation process. Later, we might be able to do a “live” validation as soon as the necessary information has been entered.

See the data gathering page for more information of how the data gathering process will go: Gathering user Data.

If the user has been validated, they will see no change in the page. If the user has not been validated, they will be prompted on the screen that no user ID matching that Student number has been found. This will make them to re-confirm they entered the data correctly.

Describe the options for what a user can do. Be specific. (May be tied with fields in earlier section.)

What is required of the user? Any input that needs to validated? Any constraints? (Perhaps a user must fill in two fields or only one of two fields.)

When a user enters input or clicks a button, what are the possible outcomes?

Examples: if user enters erroneous input, what happens? if user does one of three options, what happens in each of those cases?

Describe some typical situations of what a user can/will do.

May want to put this earlier, but may not make sense unless you explain the other stuff.

This feature is of medium to low priority. It would be very convenient, but the app could function without it.