TABLE OF CONTENTS

• What is a dev shell?
• Access to myLesley Courses
• Request a New Dev Shell
• Updating Dev Shells
• Dev Shell Lifespan

What is a dev shell?

A development course site (dev shell) is a primary version of a course which the program has designed and approved. The designing faculty may or may not have worked with eLIS to create the course.

An ideal dev shell has: 

• All, or most, of the content needed to teach the course
• Teaching notes to guide the facilitating instructor
• Been reviewed for accessibility issues. Accessibility issues will be fixed where possible. 
• Been reviewed for copyright issues. Issues have been addressed where possible, including linking to Library content. 
• Media content added using appropriate tools for the best student experience.  

One dev shell can be created for each modality the course is taught in: synchronous, asynchronous, and hybrid/weekend. 

Access to myLesley Courses

Request access to a dev shell:

Complete the  Dev Shell Access Form or email eLIS@lesley.edu. 

Dev Shell Roles: 

You may request faculty or staff be enrolled with edit or read-only access. 

• Owner: Enrolled as an instructor. This is the person responsible for the content. eLIS will contact them if there are questions about the content. 
• Editor: Enrolled as a Teaching Assistant. This person has full access to edit the content. 
• View and Copy: Enrolled with the ability to view all content and the gradebook. Cannot edit content but can copy the content to their course. 

Access to a previously taught course with student enrollments:

Access to courses with student activity is done through Colleague as the system of record. This ensures access to the student information can be easily tracked. 

There are two options: 

1. Ask the course scheduler for your area to add you to the course via Colleague.
2. Complete the   myLesley Course Access Request Form.
   The form will be reviewed by the Enterprise Applications team who will add you via Colleague.  

Course roles: 

• Instructor: Full edit access including grades and student submissions. Will be listed as an instructor for the course in Blackboard. 
• Teaching Assistant: Full edit access including grades and student submissions. 
• Course Assistant: Full edit access. No access to grades or graded student submissions. 
• Student: View access to content. Ability to view discussions or areas where all course members can interact. No access to grades or student submissions. 

Request a New Dev Shell

To request a new dev shell, email eLIS@lesley.edu. Include the following information: 

• Course code (such as CWRIT 1101)
• Course name
• List of faculty and staff who should have access
• Level of access for each person: read-only or edit

eLIS will check for existing devs for that course before creating. Only one dev shell per delivery method (sync, async, hybrid) will be created. 

Program chairs, associate provosts, etc, may request a list of current dev shells for their area by emailing eLIS@lesley.edu. 

Updating Dev Shells

Dev shells can be updated in two ways: 

1. Assign an instructor to make the necessary edits. 
   Once complete, request eLIS review for accessibility, copyright, and media.
   
   
2. Identify a previously taught course section to be copied into the dev shell.
   Contact eLIS to request the copy.
   eLIS will archive and delete the existing dev shell content before copying the new content. eLIS will then clean up the content to remove information specific to the source course section and address any copyright, accessibility, or media issues. 

Dev Shell Lifespan

Devs that are no longer in use may be useful for reference but tend to become out of date and can be confusing for faculty who have access.  

Criteria for deletion 

If the dev shell has not been copied from or updated in 3 or more years 

• Notify program 
• Is course still being taught? 
• Should dev be updated or disabled?