[[systems:enrollment:adding_a_new_academic_program:ciel]]
 
Table of Contents

Overview of technical steps

  • Student Information System Make sure the program is setup in HP/SIS (contact Cheri Putro of OIT); test with SIS test acct 950354247
  • ParaDocs Setup, implement, and test new program in paradocs
  • CollegeNet Setup the program to be listed, have the right acronyms, have the right tracks, etc in Collegenet
  • Website & Documents Make sure that various webpages are updated, and that the I: drive word file is updated.
  • Databases Update database references to programs; Faculty DB,
  • Catalogue Print and web - http://www.umbc.edu/gradschool/gradcatalog/

ParaDocs

  • Groups
    • Add new groups ex: ‘HCC’ and ‘HCC_Admin’
  • Users
    • Create any new users for the program
      • Add the GLOBAL group to each user
    • Add appropriate users to each new Group
      • Add ‘Admin’ user as group admin to all groups
  • Security
    • Set DocType Security
      • goto Security Manager>Doctype Security
      • create new group/doctype combo’s (4 doctypes for each group) (copy settings from other programs)
    • Set Tree Configuration
      • add new program to ‘Graduate Admissions’ root folder
      • Log out of paradocs and log back in for new program to display in drop down
      • go to new group/program
      • delete auto-made item
      • add new folder called ‘Graduate Admissions’
      • add new folder below that, named after the new program / group acronym
      • see other tree groups for example
      • to add and delete folders / items, you RIGHT CLICK on them
    • Do above for each group Ex: ‘HCC’ and ‘HCC_Admin’
  • Workflow
    • Create Auto-Start queries
      • 3 queries, one for each doc type, see examples logged in as user ‘workflow’ or ‘Admin’
    • Workflow Wizard
      • You may need to look at examples of past workflows before this
      • Identifier Name should be “SSN”
      • task order to be overidden: No (unless a department intentionally needs to pass it around, hodge-podge)
      • add tasks / steps; As few as needed by department; usually 2-4
      • add auto-start queries (use field3; it is the SSN field)
      • add auto-email action on new applications; this sends an email to departments when they receive new applications
  • TEST
    • Scan and profile an application of the new program
      • make sure importing works (you can add a fake record manually to the t_import table on the paradocs machine; see test code below)
      • make sure workflow with docs associated with it happens
      • make sure workflow and docs open from user perspective
      • make sure docs can be searched for and seen by graduate school users (ex: gradstudent, nee)
    • CollegeNet imports need to be tested fully;
      • use test account ‘Just Testing’
      • inspect data file
      • make sure workflow with docs associated with it happens
  • Train
    • Train all employees that will use the new program
    • Because it is a new program (which might work differently than in the past), you should retrain employees that have already used ParaDocs in the past
    • Graduate Program Coordinators (GPC’s) and Graduate Program Directors (GPD’s)

Test Code

INSERT INTO t_import VALUES ('95035****', 'TESTING', 'JUST', '', '200709', 'MAGS', 'MA', 'Y', '', '', '', '', 'MALE', 'CAUCASIAN', 'U.S. Citizen (USCIT)', 'BS', '005835', '2.56', '122004', '', 'UNIV MARYLAND BALTIMORE CO', '', 'US', '05/15/1979', '', '', '', '', '', '', 'P');
 
SELECT * FROM t_import WHERE ssn='95035****';
 
DELETE FROM t_import WHERE ssn='95035****';

CollegeNet

  • Make sure that the selection process from a students perspective is correct
  • Make sure the printout/PDF output of the form is correct
  • Make sure that the CSV data files outputs all of the acronyms correct

Website & Documents

 
systems/enrollment/adding_a_new_academic_program/ciel.txt · Last modified: 03.24.2008 14:17 by 130.85.181.155
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki