[Koha-bugs] [Bug 21561] New: Check out restriction to category / branch

[bugzilla-daemon at bugs.koha-community.org]

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

            Bug ID: 21561
           Summary: Check out restriction to category / branch
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: new feature
          Priority: P5 - low
         Component: Circulation
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: joseanjos at gmail.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com, kyle.m.hall at gmail.com

As discussed here:
http://koha.1045719.n5.nabble.com/Check-out-restriction-to-category-branch-for-School-Libraries-td5993220.html

its not possible to restrict holds between one library to a group of libraries.

With independentbraches it will restrict everything, including Patrons
modification.
IndependentBranchesPatronModifications should prevent that but doesn't do it.

The pretended is this:
1 Main Library (City hall Library CHL)
20 School Libraries (on the same server)

Assuming that if a Patron from a School wants to be patron of CHL it will be
duplicated

Shouldn't be possible checkout from CHL to any school Patron
Shouldn't be possible checkout from school to any CHL Patron

Should be possible to transfer from CHL to any school Patron and vice-versa
School Staff category should be able to modify Patrons because:
 - Every student is created with is student Nº
 - On next year he can change from school
 - Librarian from school should be able to change Library from Student
This last point is very important! Otherwise only super librarians can change
it.
That would be impossible to manage because hundreds of students change every
year.
The Librarian of each school MUST do that job.

Something like Library transfer limits but Library Holds limits would be nice

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.