Task Protocol: Reply on Completion

Just a few reminders/requests:

Everyone:

1. If an ID e-mails a task or a request directly to you please e-mail (reply all) when that task is completed. If it is a significant task you should ALSO add it to your Google Docs Task List.



2. It would also be helpful if you e-mail the responsible party upon completion of tasks in your Google Docs Task List in addition to marking them as "done" with the due date.



3. If you receive a request directly from an instructor or another DE unit (e.g. Design Center or Service Center) please CC the ID/staff member who is responsible for that course or project (Janel, Marc, Ken or myself).

IDs:

When an instructor request is completed don't forget to reply to the instructor directly.

1. I also recommend that when we reply to confirm completion of requests that come in from another DE unit (e.g. Design Center or Service Center) we CC the instructor to ensure they get the information.



2. Finally, when a developer has completed a task successfully, please verify this on their Google Docs Task List by cutting/pasting it to the Completed Tasks sheet.



3. If you have other ideas/alterations to help us keep instructors in-the-loop, please Comment here.

Practice: Backing Up Last Semester's Courses

We are implementing a new maintenance procedure for all IDS Developers:

1. Access all of your maintenance courses for the previous semester


2. Make a backup of the course through it's LMS


3. Create a "_backup" folder within the first level of the specific semester/course folder on our network drive (e.g. courses\clss\2100\IN\083_haynes_mosholder\backup)


4. Download the backup to the "_backup" folder (in Bb Vista you must "Save as file" before downloading)


5. Delete all old backup files


6. Export the gradebook to the "_backup" folder

This should be done the 2nd week of each semester on the previous semester's courses

New Course Proposal Signature & Review Process

A couple of things were clarified this morning in our weekly DE Directors' Meeting regarding new course proposals:

1. Dept Chair/Dean signature. We are going to proceed with seeking dept. chair/dean signatures at the course proposal step, not at the development compensation step. John K. has agreed that electronic signatures will be sufficient. We will need to build these into the online proposal submission and review system.



2. IDS has been charged with previewing all new course proposals in our weekly IDS meeting and making a recommendation for the IDS Director to communicate to the Senior Director. Senior Director will cover any final approval at the deans/VP level. We will need to make this process as streamlined as possible in the online system.