-
Epic
-
Resolution: Fixed
-
Minor
-
3.11.9, 4.0.3, 4.1
-
MOODLE_311_STABLE, MOODLE_400_STABLE, MOODLE_401_STABLE
-
MOODLE_401_STABLE
-
Moodle 4.1 Database project
This project arises from the deep study and analysis carried out by MUA (MDL-71006) and UX of the Database activity. Therefore, it aims to modernise Moodle’s database interface, improve the existing workflows and make its usage a more intuitive and user-friendly experience. There are two main goals, the first it makes it easy for teachers to create new database activities, providing a new set of presets and preview mode. Second, it is to improve the student experience by providing a better experience with the existing views in his journey.
MVP
The key tasks related to the teacher persona are:
- Provide "zero state" information to point teachers in the right direction. Especially to use presets.
- Revamp the list and simple view page styling with a more modern design and make it easier to use and navigate.
- Add a new set of useful presets.
- New preset management page providing preview mode.
The key tasks related to the student persona relate to simplifying and modernising the list and simple view layout so the database entries are easier to find and understand, by providing:
- Revamp the list and simple view page styling with a more modern design and make it easier to use and navigate.
- Minor style adjustments to add entry database interface.
Future work / out of scope
There are some out-of-scope goals for teachers that may be aimed at a 4.2 release, including:
- Modernize and improve the add fields workflow.
- Improve the template section to make it easy to use.
- Preview mode.
- Automatically add fields to templates when creating a new field.
- Providing new actions like duplicating or fixing/hiding the view layout.
- Add new views like grid or table layout.
- Allow the teacher to change the view name.
- Some admin actions like enabled/disabled/delete admin presets to site level.
It's important to notice that all the prototypes are in working in progress and open to new changes.
Epic Issue Integration order:
We would like to explain what we think is a proper order to integrate the issues of the epic because there are some parts of the code that some issues share. The code of the module database is old and to work properly we need to refactor some parts and create new classes, mustaches, tests and improve other parts of the code.
The following issues should be integrated in this order:
MDL-75146Create a new ##id## tag to use in Database activity templatesMDL-75211Select/Unselect all options should be visible when there is a 'delete' checkbox on database activity List template only
MDL-75148Improve Presets management list page for Database activityMDL-75142Add description to Database activity presetsMDL-75143Edit Database activity presets' name and descriptionMDL-75186Add "Export" preset feature to presets list
MDL-75137Redesign the zero state page for Database activity moduleMDL-75187Move "Delete" preset confirmation to a modalMDL-75149Create a new preview page for Database activity PresetsMDL-75401add sticky footer to mod_data pages
MDL-75275Create new dropdown kebab menu tag with all the actions for the "List view" and "Single view" templatesMDL-75140Skip fields mappings form if there are not fields createdMDL-75289Implement the prototyped navigation changes in database activityMDL-75410Reset all templates in one go
MDL-75335Zero state on fields and templates when there is no field created on the DatabaseMDL-76006Improve zero state images for database activity
- has a non-specific relationship to
-
MDL-75189 Final deprecation of functions in mod/data/lib.php
- Waiting for peer review
-
MDL-36270 Shift code that checks if 'user has created sufficient entries before being able to view' to a function and add unit tests
- Open
- has been marked as being related by
-
MDL-75605 Follow up: Database UX improvements
- Open
- will help resolve
-
IDEA-30 Database activity UX improvements
- Closed