[OPEN-ILS-GENERAL] ***SPAM*** RE: Open-ils-general Digest, Vol 52, Issue 22
Lori Bowen Ayre
lori.ayre at galecia.com
Fri Oct 15 12:36:20 EDT 2010
If you want to see the requirements that are on KCLS' plate, go to here:
http://www.rscel.org/kcls?field_kcr_funcarea_value_many_to_one[]=ACQ+-+Acquisitions+-+Selection+and+Ordering&field_kcr_id_value_op=%3D&field_kcr_id_value=&title_op=word&title=&body_op=word&body=
<http://www.rscel.org/kcls?field_kcr_funcarea_value_many_to_one[]=ACQ+-+Acquisitions+-+Selection+and+Ordering&field_kcr_id_value_op=%3D&field_kcr_id_value=&title_op=word&title=&body_op=word&body=>The
link (ugly as it is) will take you to all the Acquisitions Requirements that
KCLS is working on. What we don't know is which of those requirements have
been rolled into 2.0 and which are slated for "soonish" (in development) and
wish are tabled for now (deferred) because KCLS has been a bit busy
migrating!
But Kathleen, if you could update those requirements with one of those
statuses, that would be great. I'll set you up with the right permissions
to do so as soon as you give me the word. Everyone would greatly appreciate
it I'm sure!
Lori Ayre
On Fri, Oct 15, 2010 at 9:12 AM, Kathleen Olsen <ksolsen at kcls.org> wrote:
> Tim Spindler's message here exactly examples what KCLS has asked for
> development for our ACQ system.
>
> Kathleen Olsen
> Supervisor - Selection & Order Dept.
> King County Library System
>
>
>
> -----Original Message-----
> From: open-ils-general-bounces at list.georgialibraries.org [mailto:
> open-ils-general-bounces at list.georgialibraries.org] On Behalf Of
> open-ils-general-request at list.georgialibraries.org
> Sent: Friday, October 15, 2010 8:34 AM
> To: open-ils-general at list.georgialibraries.org
> Subject: Open-ils-general Digest, Vol 52, Issue 22
>
> Send Open-ils-general mailing list submissions to
> open-ils-general at list.georgialibraries.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> http://libmail.georgialibraries.org/mailman/listinfo/open-ils-general
> or, via email, send a message with subject or body 'help' to
> open-ils-general-request at list.georgialibraries.org
>
> You can reach the person managing the list at
> open-ils-general-owner at list.georgialibraries.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Open-ils-general digest..."
>
>
> Today's Topics:
>
> 1. ***SPAM*** Re: Acquisitions and Invoices (Tim Spindler)
> 2. Re: Acquisitions and Invoices (Joe Atzberger)
> 3. Re: Acquisitions and Invoices (Tim Spindler)
> 4. Reminder: Developer IRC Meeting, Tuesday October 19 (Ben Shum)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 14 Oct 2010 12:54:09 -0400
> From: Tim Spindler <tjspindler at gmail.com>
> Subject: [OPEN-ILS-GENERAL] ***SPAM*** Re: Acquisitions and Invoices
> To: atz at esilibrary.com, Evergreen Discussion Group
> <open-ils-general at list.georgialibraries.org>
> Message-ID:
> <AANLkTin61AbD9zsnezK8XpieyvPATfs9OnhgrN4fOM5L at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I have been going back and forth with my member libraries and they have a
> concern about this functionality and maybe current development is
> addressing
> this. Right now in their workflow, they might issue 3 orders to Baker &
> Taylor on the 1st, 15th and 30th of the month and lets say each order had
> 10
> line items. Baker and Taylor ships 6 items the folowing month with an
> appropriate invoice. Of the 6 items, 2 of the items are from the order on
> the 1st, 2 of the items are from the order on the 15th and 2 are from the
> order on the 30th. In the Innovative system, they will import the
> electronic invoice (or status update) from Baker & Taylor and that will
> change the items to received. They still physically verify that the items
> were received and if there was a problem they would make the appropriate
> changes to their records and notify Baker & Taylor.
>
> As I understand the way Evergreen acquisitions currently operates, the
> libraries would have to touch 3 different POs and select the appropriate
> line items in each order and mark the item received. With a small amount
> of
> ordering, this is manageable but libraries that are receiving a large
> volume
> of items each month, this creates a significant amount of extra work.
>
> Thanks,
>
> Tim Spindler
> C/W MARS
>
> On Wed, Oct 13, 2010 at 5:33 PM, Joe Atzberger <jatzberger at esilibrary.com
> >wrote:
>
> > We have 2.0 Alpha 1 loaded and I don't see any way to load electronic
> >> invoices and can't seem to finid any details on this. Is this something
> >> that will be available at some point?
> >
> >
> > We might have some terminological confusion over the term "invoice". The
> > EDIFACT message type "INVOIC" is not currently processed in any version
> of
> > EG.
> >
> > Most EDI features are only a few weeks old, so Alpha1 (Aug 23rd) may be
> too
> > old a release for many purposes. The newest one right now is Alpha4.
> The
> > currently used message types are:
> >
> > - ORDERS: purchase order, from EG
> > - ORDRSP: purchase order response, from vendor
> >
> > Yet to be implemented:
> >
> > - OSTENQ: order status enquiry, from EG
> > - OSTRPT: order status report (an update), from vendor
> > - INVOIC: invoice
> >
> >
> > INVOIC, OSTRPT and ORDRSP are similar, and I think ORDRSP probably
> provides
> > the information you are asking about currently.
> >
> > Also, if it is available, will you be able to receive all items if you
> load
> >> the invoices?
> >>
> >
> > When ORDRSP or OSTRPT files are loaded, they are used to update
> > order/lineitem status, expected delivery date and price. No EDI is
> > necessary to receive items individually or as part of a whole PO. So, to
> > answer your question, yes you are able to receive all PO items, whether
> > INVOIC processing is available or not.
> >
> > As I understand it, the workflow of "load this file to tell you what you
> > received" is unsupported by design. At some point an operator needs to
> tell
> > the system what items actually arrived in the real world, and not just
> what
> > the machines say arrived. For EG, we expect that reality check to happen
> as
> > items are received. Afterwards, we don't care if an electronic file says
> > otherwise, we *know* we received a given item (or that we didn't).
> >
> > We will be looking to update price info from an INVOIC when we do process
> > those files. However, I'm not sure what we will do, if anything, with
> > account balance information that may appear in the same message. I'll
> have
> > to decide when I get to that part.
> >
> > I hope that answers a few questions.
> >
> > --Joe Atzberger
> > Equinox Software, Inc.
> >
>
>
>
> --
> __________________________
> Tim Spindler
> tjspindler at gmail.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20101014/8edc47e5/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Thu, 14 Oct 2010 15:00:00 -0400
> From: Joe Atzberger <jatzberger at esilibrary.com>
> Subject: Re: [OPEN-ILS-GENERAL] Acquisitions and Invoices
> To: Tim Spindler <tjspindler at gmail.com>
> Cc: Evergreen Discussion Group
> <open-ils-general at list.georgialibraries.org>
> Message-ID:
> <AANLkTikdkpaFTLxsd6=XgE-HsKUi6rLToS=zoHg9qacn at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> > I have been going back and forth with my member libraries and they have a
> > concern about this functionality and maybe current development is
> addressing
> > this. Right now in their workflow, they might issue 3 orders to Baker &
> > Taylor on the 1st, 15th and 30th of the month and lets say each order had
> 10
> > line items. Baker and Taylor ships 6 items the folowing month with an
> > appropriate invoice. Of the 6 items, 2 of the items are from the order
> on
> > the 1st, 2 of the items are from the order on the 15th and 2 are from the
> > order on the 30th. In the Innovative system, they will import the
> > electronic invoice (or status update) from Baker & Taylor and that will
> > change the items to received. They still physically verify that the
> items
> > were received and if there was a problem they would make the appropriate
> > changes to their records and notify Baker & Taylor.
> >
>
> That seems like a good workflow. It relies on the editeur library supply
> guidelines that an INVOIC correspond to one shipment (not required by EDI).
> It is an open question whether any vendor (or any we should care about)
> implements EDI INVOIC without regard for the editeur guideline.
>
> I imagine the invoice files are still retrieved automatically by the system
> when they are made available, but no processing is done based on them until
> one or more get selected during receiving. Or perhaps they are uploaded
> from copies sent to staff via email?
>
> I assume a printed invoice accompanies the shipment. Does it identify
> itself by a unique key (or by corresonding EDI filename) to make calling up
> the right electronic INVOIC easier?
>
> --Joe
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20101014/6969eeb3/attachment-0001.htm
>
> ------------------------------
>
> Message: 3
> Date: Thu, 14 Oct 2010 16:13:39 -0400
> From: Tim Spindler <tjspindler at gmail.com>
> Subject: Re: [OPEN-ILS-GENERAL] Acquisitions and Invoices
> To: atz at esilibrary.com
> Cc: Evergreen Discussion Group
> <open-ils-general at list.georgialibraries.org>
> Message-ID:
> <AANLkTinxobZxsyCxxodzWrxgYt-jxybt+H0hhsGHRWXf at mail.gmail.com<AANLkTinxobZxsyCxxodzWrxgYt-jxybt%2BH0hhsGHRWXf at mail.gmail.com>
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> I'll have to say you are loosing me a bit because I don't know the details
> of the EDI standard and I'm struggling as an intermediary between our
> users.
> I'm not an acquisitions person and I am not entirely familiar with the
> daily
> workflow.
>
> In any case, the software we are currently using for acquisitions does
> automatically retrieve status information and invoices when it is updated
> by
> the vendor on their site. Additional, the vendors generally ship a paper
> invoice with the items. I believe it does have a unique key to correspond
> to the electronic INVOIC but I need to confirm this. In any case, our
> libraries are looking for a work flow that would allow them to update the
> status of the order information through the standard EDI process (which it
> sounds like this is what Evergreen acquisitions will do). When they
> physically receive the items, they want to be able to take the paper
> invoice
> or packing slip after confirming that everything has arrived and match it
> to
> an INVOIC which they could then with a single click mark all items received
> based on the contents of the INVOIC.
>
> Will Evergreen acquisitions have this functionality? It sounds like it
> does
> not as currently being developed. The only way to mark items received is
> by
> receiving the entire PO or selecting line items in the PO and marking theme
> received.
>
> Tim
>
> On Thu, Oct 14, 2010 at 3:00 PM, Joe Atzberger <jatzberger at esilibrary.com
> >wrote:
>
> >
> > I have been going back and forth with my member libraries and they have a
> >> concern about this functionality and maybe current development is
> addressing
> >> this. Right now in their workflow, they might issue 3 orders to Baker &
> >> Taylor on the 1st, 15th and 30th of the month and lets say each order
> had 10
> >> line items. Baker and Taylor ships 6 items the folowing month with an
> >> appropriate invoice. Of the 6 items, 2 of the items are from the order
> on
> >> the 1st, 2 of the items are from the order on the 15th and 2 are from
> the
> >> order on the 30th. In the Innovative system, they will import the
> >> electronic invoice (or status update) from Baker & Taylor and that will
> >> change the items to received. They still physically verify that the
> items
> >> were received and if there was a problem they would make the appropriate
> >> changes to their records and notify Baker & Taylor.
> >>
> >
> > That seems like a good workflow. It relies on the editeur library supply
> > guidelines that an INVOIC correspond to one shipment (not required by
> EDI).
> > It is an open question whether any vendor (or any we should care about)
> > implements EDI INVOIC without regard for the editeur guideline.
> >
> > I imagine the invoice files are still retrieved automatically by the
> system
> > when they are made available, but no processing is done based on them
> until
> > one or more get selected during receiving. Or perhaps they are uploaded
> > from copies sent to staff via email?
> >
> > I assume a printed invoice accompanies the shipment. Does it identify
> > itself by a unique key (or by corresonding EDI filename) to make calling
> up
> > the right electronic INVOIC easier?
> >
> > --Joe
> >
>
>
>
> --
> __________________________
> Tim Spindler
> tjspindler at gmail.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20101014/2ed0a6d8/attachment-0001.htm
>
> ------------------------------
>
> Message: 4
> Date: Fri, 15 Oct 2010 11:33:30 -0400
> From: Ben Shum <bshum at biblio.org>
> Subject: [OPEN-ILS-GENERAL] Reminder: Developer IRC Meeting, Tuesday
> October 19
> To: Evergreen Development Discussion List
> <open-ils-dev at list.georgialibraries.org>
> Cc: Evergreen Discussion Group
> <open-ils-general at list.georgialibraries.org>, Documentation
> discussion
> for Evergreen software
> <open-ils-documentation at list.georgialibraries.org>
> Message-ID: <4CB8744A.8000700 at biblio.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Time for another developer meeting! The next Evergreen development IRC
> meeting will be held at:
>
> * 11:00:00 a.m. Tuesday October 19, 2010 in America/Los_Angeles
>
> * 02:00:00 p.m. Tuesday October 19, 2010 in Canada/Eastern
>
> * 06:00:00 p.m. Tuesday October 19, 2010 in UTC
>
> This is a public meeting for Evergreen developers that will be held on
> the #evergreen channel on the Freenode IRC network
> (http://open-ils.org/irc.php). All members of the community with an
> interest in contributing to the development of Evergreen are welcome to
> attend. If you are unable to attend at the designated time, please feel
> free to submit comments for any of the agenda items in advance to the
> Evergreen development mailing list.
>
> The agenda is evolving at
> http://www.open-ils.org/dokuwiki/doku.php?id=dev:meetings:2010-10 -
> please extend and amend to ensure that it meets the immediate concerns
> of the project.
>
> For agenda items that have the potential to be too long to express
> during a single IRC meeting, it would probably make sense to post more
> considered opinions in advance on this mailing list. Examples of such
> agenda items might include major release process changes or drastically
> revising our bug tracking processes. If a given discussion item starts
> eating up too much meeting time and a decision is not immediately
> necessary, we can also delegate the responsibility to a volunteer
> sub-team for investigating alternatives and coming up with a proposal
> for adoption at the next meeting.
>
>
> End of Open-ils-general Digest, Vol 52, Issue 22
> ************************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20101015/cecabe54/attachment-0001.htm
More information about the Open-ils-general
mailing list