| Summary: | Store both item level and record level itemtype in statistics | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Mathieu Saby <mathsabypro> |
| Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | gmcharlt, koha, kyle, marjorie.barry-vila, patrick.robitaille |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Mathieu Saby
2014-01-22 08:51:01 UTC
+1 Note that this enhancement would be usefull even if you use the same list of possible values in items.itype and biblioitems.itemtype 2 tables to be edited : statistics and pseudonymized_transactions. They have both a "itemtype" column. I don't know if it is based on the item-level or record-level itemtype, or (probably) if it depends on item-level_itypes syspref The current "itemtype" depends on item-level_itypes syspref. I fear it would cause a total mess to change this behavior... So the cleanest way to to store both item-level and record-level itemtype is probably to add 2 new columns : item_itemtype and record_itemtype |