Dmlis 540 Spring 2004 Information System Project mecca pop and Jazz Music For Family Learning and Enjoyment All Team members participated in the development of the spec Project Manager: Carolyn Karis Information Architect: Emily Wheeler

“My Toolkit” Feature

----------------------------------------------------------------------------------

• 
  Description and Explanation for the My Toolkit Feature
  

[Or go directly to http://www.arabissmo.net/meccahomepage/Login.asp]

• 
  As described in the Features section of this spec, the Toolkit “is our favorite educational tool for parents to guide the curriculum of their children. A parent can save details about particular artists, albums, instruments, or musical styles in their own “toolkit” and have their children access the information later. Features involved would include a registration system to keep track of the owners of each toolkit, password-protection, and a storage area for saved details.“ This involves creating a separate database to store information about the users and their items. We have created the primary table for this database as included in the section to show how we are envisioning it. Here in this section, will not describe the full functionality for this feature but will describe and define the controls and queries for the login and registration process which will involve retrieval, storage, and update functionalities in our system.
  

• 
  Controls used for the Login and Registration parts of the Toolkit feature.
  

• 
  Queries used for the Login and Registration parts of the Toolkit feature.
  

• 
  Logic used for the Login and Registration parts of the Toolkit feature.
  

At Login,

1. 
   If user’s email and password do not match any in the database, Then
   

2. 
   If user’s email and password match with an email and password in the database, Then
   

At Registration, check if it is being submitted by a new or already-registered user;

1. 
   To check for a current user, check the user’s ID (user IDs are often stored in a session-level variable for the duration of the user’s session with the system), retrieve the matching record for that ID, then copy the information submitted into the fields of the matching record. (In many database applications, the update – involving copying new data and overwriting old data - is first done through a recordset then copied into the database.)
   
2. 
   To check for new user, match data entered with existing email addresses and passwords. If at end of file, no match then add a new record to the database and insert data submitted.