Courses should not be associated with terms from other orgs (except ancestors)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.6 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
In Course Reserves, users can manage academic terms from the "Terms" tab on the Course List page. Currently, the term display defaults to the Consortium location. Users must select the "Descendants" checkbox to see term data for subordinate locations. In our consortium, course reserves are managed at the system level and data is not shared among systems. So it would be preferable for this display to default to the user's working location.
Additionally, users should not have access to terms owned by different working locations. While it is not possible to edit a term owned by a different working location, but it is possible to associate a course with a term owned by a different working location.
Other consortia may manage course reserves differently, so some discussion may be in order.
EG 3-6-0
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in evergreen: | |
importance: | Medium → Undecided |
status: | Confirmed → New |
summary: |
- Course reserves should display only terms owned at user's working + Course term map should display only terms owned at user's working location |
Changed in evergreen: | |
assignee: | nobody → Jane Sandberg (sandbej) |
summary: |
- Course term map should display only terms owned at user's working - location + Courses should not be associated with terms from other orgs (except + ancestors) |
tags: |
added: signedoff removed: signed-off |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
On my 3.7 beta test server, the Terms tab defaults to the working location. So I think that issue has been resolved in 3.7.
However, I can confirm that it's possible in 3.7 to link a course to a term belonging to another library. This makes sense within multibranch systems, but should not be possible between otherwise unrelated libraries (for example, BR1 should not be able to use terms belonging to SYS2). I think it should only be possible to use a term that belongs to the course's owning_lib or one of its ancestors.