https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31422

            Bug ID: 31422
           Summary: Library limitations might cause data loss
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: major
          Priority: P5 - low
         Component: System Administration
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected], [email protected]

The library limitations are used to limit down the selection in pull downs in
several spots. If you are editing data from library B while logged in at
library A, doing so might result in data loss as the value stored in the
modified object might be missing from the drop downs your user sees.

Example 1: Item values

Itemtype: BK Books - limited to Centerville
AV LOC: FIC Fiction - limited to Centerville
Your user: logged in for Centerville

* Edit an item and make sure it uses the itemtype Books and location Fiction.
* Switch library to any but Centerville.
* Edit item: Both item type and location drow downs will be empty.
* Saving now will empty out itemtype (if not set mandatory) and location
resulting in data loss.


Example 2: Patron data

Patron category: Patron PT - limited to Centerville
Your user: logged in for Centerville

* Find a patron with the limited patron category
* Edit patron: Verify the patron category shows in pull down
* Switch library to any but Centerville
* Edit patron: the category pull down will show the first entry of the pull
down visible for this library. Saving now, you will change the patron category
unknowingly resulting in data loss.

Additional bug: If you search for "all patrons", you will have an error in the
console no patrons will display: Uncaught TypeError: categories_map[data] is
undefined. Filed as bug 31421.



I think we need to make sure that the pull downs show what the library can use,
but also what the current setting of the object is in order to prevent data
loss. IIRC the funds pull down on the receive page uses a mechanism for this.

Otherwise library limitations are very dangerous to use and can only be
recommended if we can make sure that objects from other libraries cannot be
edited at all where library limitations have been applied.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to