Documentation:Learning Environment/What Do We Hope For?
From Kumu Wiki - TRU
What We Hope For
- An environment that will allow and support learning that is adaptive, reflective, and flexible.
- A consistent environment across TRU that connects learners to support a community focused on learning.
- A solution that allows interaction with the content and collaboration with others.
A solution that:
- Is cost neutral/benefit to student
- Has a smooth transition
- Provides training available for students/staff/faculty
- Students and faculty love it
- Improves retention of students
- Distinguishes TRU as a leader in online course delivery through
- Streamlines production - Net zero on production – or at least streamline process
- Allows multi-access learning opportunities (Online, face to face, blended)
A system/environment that:
- Is easy to use and intuitive
- Is attractive/customizable/user friendly
- Is supported by dedicated tech support (system)
- Retains current functionality/efficiencies
- Is robust and requires minimal maintenance/upgrades
- Can be supported with current resources
- Has Single Sign On capabilities
- Allows communication for students outside their courses
- Is accessible through multiple devices
- Is seamless so the technology is invisible
- Is integrated with student systems including materials
Functionality that allows:
- Private/open options (content and tools)
- For more innovative and interactive courses
- Invisibility of technology
- Online proctored exams
- Print options for course content
- A “Dashboard” for students to track their progress
- Academic support links
- Easier editing/updating of content
- Online academic/personal supports
- Access to exam scheduling
- Mapped, webbed course display
- Just in time revisions
- Student content ownership –access to course materials and uploaded content after course ends. Including E-portfolios.
- Language Options
- Course content to have:
- Better control and flexibility over setup – own basic container creation
- An environment that can use a single source (where SME's can seamlessly develop content within) but where content can be readily pulled out.
- Within LMS versioning
- Tools developed to help move data
- Processes automated for initial course creation and for maintenance
- Future courses designed in a way that is less LMS specific (ie. reduce references to Blackboard except when necessary, and use course tools that are more or less ubiquitous from one LMS to another). However this can probably only be accomplished to a certain extent.
- Courses built and maintained efficiently in a new LMS.