Move calculated dewey ranges/blocks to their own reporting view
Bug #1813191 reported by
Jason Boyer
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Eg 3.2.3
One of the few reasons to still use the Classic Item View reporting source is that it has calculated fields for dewey blocks and ranges that can make it very easy to build reports that circ or weeding by subject block(s). Because there aren't really any other benefits to this view those calculated fields should be moved to their own view off of asset.call_number so they're available for use in reporting if needed, but have no effect whatsoever if they're not.
Changed in evergreen: | |
milestone: | 3.3-beta1 → 3.3-rc |
Changed in evergreen: | |
milestone: | 3.3-rc → 3.next |
Changed in evergreen: | |
assignee: | nobody → Rogan Hamby (rogan-hamby) |
Changed in evergreen: | |
assignee: | Rogan Hamby (rogan-hamby) → nobody |
tags: | removed: needsreleasenote |
tags: | added: signedoff |
Changed in evergreen: | |
milestone: | 3.next → 3.7-beta |
Changed in evergreen: | |
milestone: | 3.7-beta → none |
milestone: | none → 3.next |
tags: | removed: needsrepatch |
Changed in evergreen: | |
assignee: | nobody → Terran McCanna (tmccanna) |
Changed in evergreen: | |
assignee: | nobody → Evergreen Bug Maintenance (bugmaster) |
status: | New → Confirmed |
tags: | added: signedoff |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note: Because of some current issues with might_have links in the IDL in web reports the proposed fix (or some equivalent) to bug 1796945 will be required to use this view.