View the Github ticket for proposal status updates
...
Expand | ||
---|---|---|
| ||
This broad category took about 27% of the support requests, 16% related to LMS users issues and 11% related to Studio permissions. the most common stories in this category are:
|
Expand | ||
---|---|---|
Expand | ||
| ||
| ||
Nearly 11% of all requests where related to reports and accessing information, for example:
| ||
| ||
This category gets about 13% or the total number of requests, but Certificates and we often confirm during user interviews that Certificates are very important though.
Most of the challenges with certificates happen at the administrator level: certificate templates per organization, certificates in multiple languages, gating configurations to be able to access certificates or not, reporting on the total numbers of certificates issued and the specific certificates issued, allowing to integrate certificates with external tools like digital credentials, linkedin, etc. Example tickets:
Other part of the challenges with certificates happen at the course level: configuring a course to offer certificates, configure that particular certificate for the course if needed, issue certificates, etc. These needs will probably best served in studio and not the administrator console.the instructor dashboard or Studio. and not the administrator console. |
Expand | ||
---|---|---|
| ||
Nearly 11% of all requests where related to reports and accessing information, for example:
|
Proposed solution
Overview
...
The “admin core component will need to have the following capabilities.
be able to access the different models in lms and studio
be able to access the different models in all the openedx services (credentials or discovery), to enable the extensions posibilities in the admin console.
be able to “read” or “be aware of” the settings that are not stored in data models, but in lower layers such as django configs or python package entry points.
TBD - comments and contributions are most welcome
UX / UI considerations
The UX / UI should be simple and convenient for administrators, who are often used to handling this kind of consoles in many other applications.
The UX / UI should be able to accomodate all the flexibility that comes with the “core + extensions” approach.
Include any UX/UI designs. COMING SOON.
Proposed plan for any relevant usability/UX testing
Other approaches considered
...
Expand | ||
---|---|---|
| ||
In moodle, the LMS, the authoring platform and the administration console are all part of the same web application. This interface has a search function that filters all the settings by keywords and presents a list of search results that can directly be interacted with, and a save button for applying the changes made in any of the components of the search results page. This eliminates the need to navigate to a different page for each of the components you want to alter. some of the more elaborated interfaces, even after apperaring in the search results page, will need the user to navigate to a dedicated page, for example this is the page where ad administrator will list and manage users: a few elements of this interface worth hightlight:
other pieces that are also complex will have different intefaces, for example here is how roles are assigned to users: moreover, some settings can be defined at different levels, with the setting at the parent level being imposed or being the default for the lower level. (example rss enablements TBD). |
Expand | ||
---|---|---|
| ||
In Canvas, the LMS, the authoring platform and the administration console are all part of the same web application. In Canvas, a user can be granted “subaccount administration” Administrators can find a specific user (learner or instructor) and find out what courses they have assigned and the pages they have viewed. They can also email them from the application. |
...
Plan for long-term ownership/maintainership
TBD - comments and contributions are most welcome
Open questions for rollout/releases
TBD - comments and contributions are most welcome
Authors
Proposal prepared by Juan Camilo Montoya and Santiago Suarez . Initial review by Felipe Montoya