Bill,
This is the same conclusion that I was coming to. As I was saying
before, I didn't want to jump to a launchpad bug because it seemed odd
that something this fundamental wasn't already fleshed out and
incorporated. Shall I create a bug?
-Blake-
Conducting Magic
MOBIUS
On 12/12/2014 9:48 AM, Bill Erickson wrote:
This is probably a limitation within AutoFieldWidget. It has a
special handler for copy locations to avoid loading all perm-visible
locations, which can be many thousands in some consortia. This seems
like a good candidate for a typeahead box --
openils.widget.PCrudAutocompleteBox in this context.
-b
On Fri, Dec 12, 2014 at 10:38 AM, Blake Henderson
<[email protected] <mailto:[email protected]>> wrote:
Mike,
We do have the working locations setup (checked) on each of the
branches in the system for the user in question. We only see the
copy locations populated for the branch that the workstation is
registered.
-Blake-
Conducting Magic
MOBIUS
573-234-4513 <tel:573-234-4513>
877-312-3517 <tel:877-312-3517>
On 12/12/2014 9:23 AM, Mike Rylander wrote:
Blake,
I didn't see if this was already asked and answered elsewhere and
I don't know if it will help in the ACQ interfaces, but, did you
give the user in question multiple working locations via the user
permission editor?
HTH,
--
Mike Rylander
| President
| Equinox Software, Inc. / The Open Source Experts
| phone: 1-877-OPEN-ILS (673-6457)
| email: [email protected] <mailto:[email protected]>
| web: http://www.esilibrary.com
On Thu, Dec 11, 2014 at 11:19 AM, Blake Henderson
<[email protected] <mailto:[email protected]>>
wrote:
Hello all,
I apologize for the duplicate email, I sent this to the dev
list and it was suggested that I send it to the general list:
I couldn't find a bug on this. We are using acq for the
first time and I
don't want to jump to any conclusions. When creating a PO and
assigning
the copies to their branches and copy locations, we noticed
that the UI
only shows the copy locations for the branch that you happen
to be
registered to. We have a scenario where a single branch is
doing all of
the PO's for all of the sibling branches. Are we doing
something wrong?
During some experimenting, I found that if you register the
user to the
system level instead of the branch level, it will show all of
the copy
locations for each branch. That, of course, is not a good
idea for other
reasons. We ruled permissions out by assigning the
EVERYTHING^consortium to the user.
It seems like if the software allows the copies to be assigned to
different branches, it should also allow copies to get
assigned to the
respective shelving location in that branch.
--
-Blake-
Conducting Magic
MOBIUS
