Distributed Empowerment

15
ALMA Alberta Livestock & Meat Agency Ltd. Canadian Bovine Genomics Workshop September 14, 2009 Calgary, Alberta

description

for presentation at FUSION, D2L's user conference July 2009 in St. Paul, MN

Transcript of Distributed Empowerment

Page 1: Distributed Empowerment

Distributed EmpowermentKyle Mackie (University of Guelph)Trevor Pemberton (University of Guelph)Terri-Lynn Brown (Calgary Board of Ed)

Page 2: Distributed Empowerment

Agenda

1. Background - Structure of our organizations, numbers for depts/schools

2. D2L Configuration – how our organizations are currently configured

3. What’s working / What’s Not – a discussion about successes and challenges at our institutions

4. Wish List – ideas proposed to meet our challenges. How do they align with the needs of other institutions? Are there commonalities or competing interests?

Page 3: Distributed Empowerment

Opening Statements

Technology and policy should allow administrators can empower others within the institution so that they have administrative control over their own environments.

The Learning Environment should be engineered so that departmental administrators can manage users, courses, tools and roles. In turn, these administrators will be able to empower other users.

Page 4: Distributed Empowerment

Tools of the Trade

• Organizational Structure• DOME• Roles and Permissions• Most importantly, communication

Page 5: Distributed Empowerment

Organizational Structure - UGuelph

Page 6: Distributed Empowerment

Organizational Structure - CBE

Page 7: Distributed Empowerment

Templates w/Multiple Parents

DE course templates can be assigned 2 parent departments Department admins can configure the course template to meet their needs, and have admin and design control over the course offering

Page 8: Distributed Empowerment

Another way to look at it…

Page 9: Distributed Empowerment

CBE – Baselines vs Templates

• One template per school/program• Program of studies is the same, but curriculum is not• Local team/individual baselines• Control over baseline is managed by the owners

Page 10: Distributed Empowerment

Empowerment

“to equip or supply with an ability; enable”http://www.thefreedictionary.com

“to promote the self-actualization or influence of”http://www.merriam-webster.com/dictionary

“Empowerment refers to increasing the spiritual, political, social or economic strength of individuals and communities. It often involves the empowered developing confidence in their own capacities.”http://en.wikipedia.org/wiki/Empowerment

Page 11: Distributed Empowerment

Goals

To ensure that the roles and permissions structure meets all use cases effectively.

"Effectiveness" will be measured by how the structure adheres to privacy guidelines, is manageable, flexible, and meets business practices for different units.

Page 12: Distributed Empowerment

Course Customization

Control for Department’s courses

Page 13: Distributed Empowerment

Course Management

Access to Department course offering folders

Page 14: Distributed Empowerment

User Management

Control over user creation and enrollment using D2L User Management tools

Page 15: Distributed Empowerment

Roles

• Develop a philosophy

• Come up with a plan

• Implement

• Refine

Page 16: Distributed Empowerment

Roles

Role types can be created in test instance and imported

• Keep it simple• Dedicated staff for role management

• recommended that only high-level administrators have access to the Manage Roles and Permissions tool. (source: Mackie & Vance “Best Practices in Role Management”, FUSION 2005)

Page 17: Distributed Empowerment

Roles

Who the are

How they are created

What they can do

Page 18: Distributed Empowerment

Organization-level Roles - UGuelph

ORG super admin ORG admin ORG user ORG non-uog user

Who they are Sys admins LTCi staff uoguelph users guests

What they can do All permissionsNo access to DOME, roles

eP, locker, my courses, profile, etc

my courses

How they are created

super admin super admin LDAP admin

Page 19: Distributed Empowerment

Organization-level Roles - CBE

ORG Super Admin

ORG Course Admin

ORG Teacher ORG Student ORG Externals

Who they are

Sys admins CLT Staff CBE Teachers CBE Students Guests

What they can

do

All permissions

No access to DOME,

roles

eP, locker, content, disc,

MyCourses, etc

eP, locker, MyCourses

No pager, no mail, no profile

my courses

How they are

createdSuper admin

Super admin

LDAP LDAPSuper admin, Course

Admins

Page 20: Distributed Empowerment

Course-level Roles - UGuelph

InstructorTA-build-

gradeTA-grade Registered-Student Guest-Graded

Guest-nongraded

Deferred

Who Teaching Instructor-level GraderOfficially

registered(incl AU)

Deferred exams

WhatAdminDesignGrade

DesignGrade

Grade Student-level Student-level Student-level past courses

How

RequestAdmin/Assoc/

Instructor

RequestAdmin/Assoc/

Instructor

RequestAdmin/Assoc/

Instructor

ColleagueOLIS

RequestAdmin/Assoc/

Instructor

RequestAdmin/Assoc/

Instructor

RequestAdmin/Assoc/

Instructor

Page 21: Distributed Empowerment

Course-level Roles - CBE

Teacher TA Student Student CBe-Learn Guest

Who Teaching Instructor-level CBE StudentCBe-Learn Online

StudentExternal Users and

Invited Guests

WhatAdminDesignGrade

Grade Student-levelStudent-level & D2L

EmailStudent-level

HowRequestAdmin/Teacher

RequestAdmin/

Teacher

Request Admin / Teacher

Course AdminRequestAdmin/

Teacher

Page 22: Distributed Empowerment

“Dept”-level Roles - UGuelph

Associate Assistant Observer

Who Departmental Marks admin Guest, Chair

What Instructor-level TA-Grade-level Guest-level

How Super adminAdmin/

Associate

Admin/

Associate

Page 23: Distributed Empowerment

Wish List

• More power tools at the department level• Provisioning roles• Granular navbar permissions• User Management• WebDAV granularity• Web services?