Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Knowing what tool to pull upon for what is key–make sure to have these big six at your ready.


•OS 1) OS ticket (OST) : https://qticket.cns.utexas.edu/scp/login.php

Customer facing help line. You will also get emails for every one of these. There are a few different address sources that are piped to this help line; for ease of memory refer people to use: questhelp@austin.utexas.edu


•SysAdmin (also on lbtest2) Systems Admin (sys admin, also on the backup server, changing the 'quest' in the address line to 'lbtest'):

(on production, or 'prod', notice 'quest' in the URL and UI has ample white space) https://quest.cns.utexas.edu/systemadmin/main

...

          masquerade (bookmark!-pretend to be someone else!)


•Institutional admin:3) Institutional admin (inst admin)

https://quest.cns.utexas.edu/institutionadmin/institutions

Drill down into different buckets tied to an institution, specifically
         Managing credentials (adding teacher/contributing editor)
         Assignments (missing generations, collective and individual)
         Adding students to a course unique, or a specific section within a unique (for staggered start times)


•Specific 4) Specific assignments or courses drill down (called the cua page, for course user assignment). This is a child page under each institution under the institutional admin page. Most commonly used are assignment id (a.id), course id (c.id), learning module (lmod), course user assignment (cua), and module session. Because there are many different levels (ie the assignment's general id number vs the specific ones paired with an individual) we'll touch more on this soon. Right now just know under assignment id (under elements) and learning module.id are the assignment number on the instructors address line–this is the the general identification for the assignment before it gets differentiated into the specific students in the class. For a specific student in a class, courseuserassignment.id  or modulesession.id will be used–we'll see those in the specific student's address line for a given assignment.

https://quest.cns.utexas.edu/institutionadmin/institutions/show?institutioncredential=72276


•Find 5) Find ut eid:* - this is used to look up UT eids of users when they fail to provide that necessary info. I like to look up by email as that tends to be most specific, but a first and last name combo (as long as it's somewhat original) can be viable too

https://enterprise.login.utexas.edu/idp/profile/SAML2/Redirect/SSO?execution=e1s1

Or https://idmanager.its.utexas.edu/eid_admin/ )•Billing info (public facing): https://getquest.cns.utexas.edu/


•Instructor 6) Instructor and Student (and TA) Quest technical help pages:. Whenever it is possible to empower the user to do something to solve their own problems in the future, refer them to the relevant help page on how. While not a great idea to consume in one sitting, it is a good idea to read these help pages to know what is possible for different clients.

https://wikisutexas.utexasatlassian.edunet/wiki/display/questla/

             Examples of common problem/solutions to link to on help pages include:

•Clear cache: (#1 Here) https://wikisutexas.utexasatlassian.edunet/wiki/display/questla/Reccomendations+before+testing+online
•Instructors, pooling questions: https://wikisutexas.utexasatlassian.edunet/wiki/display/questla/Pooling+Questions
•Instructors, late submit: https://wikisutexas.utexasatlassian.edunet/wiki/display/questla/Late+submissions

...


There's additional information that exists (always), but they won't be essential for your first weeks on the job. Cycle back to these after you have a firm sense of the OST, institutional admin, systems admin side of things:


7) Promotional/sign up Quest pages (called: getquest): https://getquest.cns.utexas.edu/


8) Txshop* - how students pay for Quest : http://utdirect.utexas.edu/txshop/index.WBX


9) Trac (for now, slack/email leta) - the communication system with the developer (Steve) to document problems and errors: https://qtrac.cns.utexas.edu/trac/

...