Gradebook allows course staff to view, filter, and override subsection grades for a course. Additionally for Masters courses, Gradebook enables bulk management of subsection grades.
Jump to:
For existing documentation see:
- Basic Usage: Review Learner Grades (read-the-docs)
- Bulk Grade Management: Override Learner Subsection Scores in Bulk (read-the-docs)
The micro-frontend offers a great deal more granularity when searching for problems, an easy interface for editing grades, an audit trail for seeing who edited what grade and what reason they gave (if any) for doing so.
UsageProblems can be filtered by student as in the traditional gradebook, but can also be filtered by scores to see who scored within a certain range, and by assignment types (note: Not problem types, but categories like ‘Exams’ or ‘Homework’).
This project does not (yet, at least) create any graphs, which the traditional gradebook does. It also does not give quick links to the problems for the instructor to visit. It expects the instructor to be familiar with the problems they are grading and which unit they refer to.
The gradebook is expected to be much more performant for larger numbers of students as well. The Instructor Dashboard link for the legacy gradebook reports that "this feature is available only to courses with a small number of enrolled learners." However, this project comes with no such warning.
Groups whose instructors need not ever manually override grades do not need this project, but may not be any worse off depending on their needs. Instructors that expect to review grades infrequently enough that not having a direct link to the problem in question will have a worse UX than the legacy gradebook provides. Instructors that rely on the graphs generated by the current gradebook might find the lack of autogenerated graphs to be frustrating.
To install gradebook into your project:
npm i --save @edx/frontend-app-gradebook
-
Clone your new repo:
git clone https://github.com/openedx/frontend-app-gradebook.git -
Use the version of Node specified in
.nvmrc -
Stop the Tutor devstack, if it's running:
tutor dev stop -
Next, we need to tell Tutor that we're going to be running this repo in development mode, and it should be excluded from the mfe container that otherwise runs every MFE. Run this:
tutor mounts add /path/to/frontend-app-gradebook -
Start Tutor in development mode. This command will start the LMS and Studio, and other required MFEs like
authnandaccount, but will not start the Gradebook MFE, which we're going to run on the host instead of in a container managed by Tutor. Run:tutor dev start lms cms mfe
-
Install npm dependencies:
cd frontend-app-gradebook && npm install -
Start the dev server:
npm run dev
To install the project please refer to the MFE Development on Tutor instructions.
When not mounted, gradebook will run in the shared MFE container at http://apps.local.openedx.io/gradebook/course-v1:edX+DemoX+Demo_Course.
When mounted in the tutor gradebook container, or when running a local (host) webpack dev server, the web application runs on port 1994, so when you go to http://apps.local.openedx.io:1994/gradebook/course-v1:edX+DemoX+Demo_Course you should see the UI (assuming you have such a Demo Course in your devstack). Note that you always have to provide a course id to actually see a gradebook.
(Note: This may not work in Tutor; these instructions are for the deprecated Devstack) You can see the log messages for the docker container by executing make gradebook-logs in the devstack directory.
Note that starting the container executes the npm run start script which will hot-reload JavaScript and Sass files changes, so you should (:crossed_fingers:) not need to do anything (other than wait) when making changes.
This MFE can be customized using Frontend Plugin Framework.
The parts of this MFE that can be customized in that manner are documented here.
Run:
nvm use
npm ci
npm test
config- Directory for
webpackconfigurations
- Directory for
public- Entry point for the single-page application -
gradebookhas a singleindex.htmlfile
- Entry point for the single-page application -
srccomponents- Directory for presentational
Reactcomponents
- Directory for presentational
containers- Directory for container
Reactcomponents
- Directory for container
dataactions- Directory for
Reduxaction creators
- Directory for
constantsreducers- Directory for
Reduxreducers
- Directory for
See the @edx/frontend-auth repo for information about securing routes in your application that require user authentication.
The code in this repository is licensed under the AGPLv3 unless otherwise noted.
Contributions are very welcome. Please read How To Contribute for details.
This project is currently accepting all types of contributions, bug fixes, security fixes, maintenance work, or new features. However, please make sure to have a discussion about your new feature idea with the maintainers prior to beginning development to maximize the chances of your change being accepted. You can start a conversation by creating a new issue on this repo summarizing your idea.
If you're having trouble, we have discussion forums at https://discuss.openedx.org where you can connect with others in the community.
Our real-time conversations are on Slack. You can request a Slack invitation, then join our community Slack workspace Because this is a frontend repository, the best place to discuss it would be in the #wg-frontend channel.
For anything non-trivial, the best path is to open an issue in this repository with as many details about the issue you are facing as you can provide.
https://github.com/openedx/frontend-app-gradebook/issues
For more information about these options, see the Getting Help page.
All community members are expected to follow the Open edX Code of Conduct.
Please do not report security issues in public. Please email [email protected].