This release of WAM contains some improvements and bug-fixes from v2.1.0, as well as some slight clean ups in navigation and typographical fixes, and upgrades for compatibility with Django 3.2.
What is WAM?
WAM started life as a Workload Allocation Modeller, although it is now supports the workflows around moderation and external examination of assessment, and has other features intended to provide support for Academic Schools and Departments. WAM is Free and Open Source, and is designed to be flexible to the needs of many Higher Education Providers.
More details, instructions and screencasts can be found on the project wiki.
Improvements
- Improvements to the master assessment tracking list on modules, such as:
- There is a new option to show moderaters and coordinators to be shown (or not) from the master list, without having to drill into individual modules. This also shows the "Lead external examiner". As a result all key people are easily visible from the main list.
- Modules can be filtered by "Lead Programme" to make it easier to see assessments for a given External Examiner.
- There are significant improvements on clarity of instructions to users at each assessment stage both within the app, and emails.
- Superusers can access all modules
- More prominent advice to use staff numbers when adding new members of staff (usually assuming you are authenticating against a corporate database).
- Assessment resources can be better handled from within the admin interface.
- When Permission is Denied, there is sometimes more information as to why.
- Fixes to be compatible with Django 3.2 have been added.
Bug Fixes
- when a new superuser is created, WAM automatically creates a matching staff record on first login, fixing a problem for completely fresh installations. (See #45)
- there is clearer handling for when an authenticed visitor has no user account created. (See #34)
- the populate_database --add-test-data command was slightly broken in 2.1.0 and has now been fixed (See #32)
- fixed deletion confirmations for assessment items.
- some recipient address were missed on sign off notification emails.
- slight improvements in "quiet" handling of assessment notification emails with the command tool.
- users marked as "inactive" are bypassed in all email communications.
- sometimes incorrect guidance was shown when there were unsigned assessments.
- cloning workpackages could be broken when items outside the package were referenced. (See #39)
and some others not worth recording.