[OPEN-ILS-GENERAL] Question on loading order records in acq

[Bill Erickson]

Hi Kathy,

I agree those docs are not quite right.  The context org unit should map to
the entity which is responsible for placing and managing the order.  It
defines, as you said, what org unit settings are in scope, as well what
fiscal year to use, who is allowed to view/modify the PO, where the items
should be delivered, the EDI SAN, and probably some other stuff I'm not
thinking of.  In the case of a multi-branch system, where the system is
responsible for ordering for the branches, choosing the system as the
context org unit is best.

-b



On Mon, Jul 15, 2013 at 5:01 PM, Kathy Lussier <klussier at masslnc.org> wrote:

>  Hi all,
>
> I'm working on updates to the Evergreen documentation for loading MARC
> order records to incorporate some of the sticky fields we have in 2.4. As
> part of the process, I realized that the original documentation for loading
> order records was never moved up beyond 2.1.
>
> I have a question about step 5 in these docs
> http://docs.evergreen-ils.org/2.1/html/_load_marc_order_records.html:
>
>  Select an org unit from the drop down menu. The context org unit is the
> org unit that owns the bib record.  You should select a physical location
> rather than a political or administrative org unit as the context org unit.
> For example, the Smith County Library System is funding purchase of a
> copy of Gone with the Wind. The system owns the bib record, but it cannot
> receive the physical item. The acquisitions librarian will choose a
> physical branch of that system, a processing center or an individual
> branch, to receive the item.
>
> I would like to rewrite this paragraph, because I think it's confusing,
> but, more importantly, I'm not sure the information is still accurate three
> versions later. I just want to make sure my line of thinking is correct
> before I put it into documentation.
>
> The way I understand the above paragraph, the branch (the physical
> location) should be selected as the context org unit. However, in my work
> in acquisitions, I actually find that it's better to select the system in a
> multi-branch environment. Our multi-branch systems often upload records for
> multiple branches in one file. If we were to select a branch as the context
> org unit, it would create problems because another branch may be using a
> copy location that is not owned by the context org unit, and the upload
> would fail. If we select a system as that context org unit, then the system
> allows uploads for items in copy locations owned by all the branches in the
> system.
>
> Is there some problem I'm unaware of that occurs if you select the system
> as the context org unit here instead of selecting a physical location?
>
> Thanks!
> Kathy
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative(508) 343-0128klussier at masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>


-- 
Bill Erickson
| Senior Software Developer
| phone: 877-OPEN-ILS (673-6457)
| email: berick at esilibrary.com
| web: http://esilibrary.com
| Equinox Software, Inc. / Your Library's Guide to Open Source
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20130716/17e3a4c2/attachment-0001.htm>