1 / 15

Bruce Correll Registrar Lehigh University Adviser Notes

Bruce Correll Registrar Lehigh University Adviser Notes. Response for data entry text. System generated by circumstances of user and action requested Each time a Faculty member saves, edits or changes access and submits a confirmation message is generated.

anthonyw
Télécharger la présentation

Bruce Correll Registrar Lehigh University Adviser Notes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Bruce Correll Registrar Lehigh University Adviser Notes

  2. Response for data entry text • System generated by circumstances of user and action requested • Each time a Faculty member saves, edits or changes access and submits a confirmation message is generated. • If system access is denied the user is directed to the Registrar • If “no Access” is indicated it will be stored as a sole possession note.

  3. Response Text • The system is LIN/PIN protected therefore meets FERPA and Safe Harbor Standards • Once shared the note is no longer considered Sole Possession. BY definition a sole possession note is not ever been shared with a colleague.

  4. System Capabilities • Record appointments, the results of the appointment and if the student did not show for the appointment • Record meeting by type of advisement. • Adviser Notes menu available by as few clicks as possible

  5. Security • Based on values established in a manually created record and attribute in SIRATTR. We went with a function rather than fine grain access control. • We created adviser, NOT FACULTY, records for staff with access • OIR needed to know to make sure faculty reports are not effected.

  6. Thanks, • Jim Baker, ESI Office at LU he is here, so complain to him.

  7. Questions & Closing • Any Questions? • Any suggestions? • Thank you for your courtesy. • To obtain copies of this ppt please go to http://www.lehigh.edu/~inrgs/files

More Related