Bug 26622 - Unique Constraint on Authorised Values conflicts with use of Report Subgroup category
Summary: Unique Constraint on Authorised Values conflicts with use of Report Subgroup ...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Database (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement with 8 votes (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-06 16:27 UTC by Joy Nelson
Modified: 2021-01-05 08:21 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joy Nelson 2020-10-06 16:27:10 UTC
Bug 22887 introduced a unique constraint on authorised values category/code.  However, this causes problems for the existing use of Report Subgroups.  There are many sites that use the same code in Report Subgroups that relate to different Report Groups (tied via reports_subgroup lib opac value).  

Example:
category, code, description, lib_opac
Report Group, TECH, technical services,
Report Group, CIRC, Circulation department,

Report Subgroup, RENEWALS, Renewal stats, TECH
Report Subgroup, RENEWALS, Renewal circ stats, CIRC

It is entirely possible to have two Report Subgroups with the same code that relate to different Report Groups as seen in the above example.

Report Group and Subgroup functionality needs to be removed from the authorised values module and a new module/database created for it.