SPAM: RE: [OPEN-ILS-DEV] Evergreen and EDI (was Evergreen Collection Development)

Tue May 29 16:49:56 EDT 2007

Hi everybody,

Now that another vendor has mentioned EDI, I'll uncloak and say "me,
too!" There was a post a while back talking about the first phase of
acquisitions containing the ability to print paper purchase orders.
While I understand that some publishers may not be able to receive EDI
POs, almost all of the library wholesalers can, and having a library
have to print/mail paper POs would be a step backwards, both in terms of
doublekeying and fulfillment time. Like Ingram, YBP (an academic library
supplier) accepts electronic orders in a variety of EDI and non-standard
formats. In terms of EDI invoices, I would think that any library that
has gotten used to receiving its huge subscription agent renewal invoice
via EDI will have concerns about going back to entering all of that data
manually from a printed invoice. 

If you plan to program to one EDI format, our recommendation (for now)
would be EDIFACT, it being a mature international standard. X12 is a US
standard, TRADACOMS is a British standard, and ONIX/XML standards are
still in development. Ideally an acquisitions system would be able to
output EDI purchase orders and claims, and receive EDI purchase order
acknowledgments and invoices. If that's too ambitious, then POs and
invoices seem like a good starting point.

Also like Ingram, we have many customers who place orders or gather
bibliographic information from our website that they then load into
their local system. Data supplied in MARC 9xx fields is often used to
drive acquisitions processes, whether that's creating the order record
or individual invoice lines. That's especially critical in situations
like approval plans (not common in public libraries, but widely used in
academic libraries), where there is no existing order in the library's
system, but the supplier sends a batch of books every week fitting the
library's general profile. For those books, the library must then gather
MARC records, create POs without sending them, receive/close the POs,
and post the invoice. Many of our customers drive all or part of that
work via a file of MARC records with order and invoice data in 9xx
fields.

I'm not in the position at YBP to volunteer any developers to the
project, but when you get to the point of outputting sample POs for
vetting by vendors and/or needing sample invoices, I'm happy to help
with that.

Thanks for this continuing discussion of the acquisitions module
development.

A-M

Ann-Marie Breaux      
Vice President, Academic Service Integration 
YBP Library Services, plus Baker & Taylor and J.A. Majors

phone/fax: (678) 445-5720 
vmail: (800) 258-3774 x3504 
e-mail: abreaux at ybp.com 

GA address: 131 Dockside Downs Drive, Woodstock, GA  30189 
NH address: 999 Maple Street, Contoocook, NH  03229

________________________________

From: open-ils-dev-bounces at list.georgialibraries.org
[mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of
Wilkening, Chris
Sent: Thursday, May 24, 2007 3:22 PM
To: open-ils-dev at list.georgialibraries.org
Subject: RE: [OPEN-ILS-DEV] Evergreen Collection Development

Below are some excerpts from an e-mail that might answer some of the
questions you had posed for me a month ago:

Brodart would encourage Evergreen to adopt an industry standard EDI
order format.  Brodart can process such orders and produce electronic
acknowledgments and invoices.  

Evergreen should consider in their development the need for libraries to
communicate distribution and cataloging information to the vendors that
they do business with.  This is commonly referred to as enriched or
enhanced order details and would include; Bib Number, Branch Code,
Branch Quantity, Collection Code, Item Type, Fund Code, and Call Number.
Depending on the format they are leaning towards we could recommend the
structure of this data.

Brodart currently processes orders in EDI standard formats of X12 and
EDIFACT format.  The new ONIX format is also on our radar.

I would be interested to know if they have the ability to import MARC
records from a vendor's website either to update that system with what
has been ordered on the vendor's website or to populate a purchase order
that would later be sent to the vendor as an EDI order.  If they have
this capability they should know that Brodart's Bibz can produce
on-order MARC records with holdings information for these purposes. 

Christopher Wilkening

Web/Application Developer

Brodart Co.

570-326-2461 x6496

________________________________

From: arhyno at uwindsor.ca [mailto:arhyno at uwindsor.ca] 
Sent: Monday, April 30, 2007 11:21 PM
To: open-ils-dev at list.georgialibraries.org
Subject: Re: [OPEN-ILS-DEV] Evergreen Collection Development

Hi Chris, 

There is a "Desiderata" piece to the work going in acq/ser with OFBiz.
The idea is that it will be a sort of rolling catalogue of materials
that are either on order and/or represent potential items to be ordered.
I used a system like this in a previous life and found it was invaluable
for automatically calculating different spending scenarios for those,
like me, who tended to want far more materials than their budget could
sustain. Can you provide some more details on the type of interface you
have in mind? 

art

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.georgialibraries.org/pipermail/open-ils-dev/attachments/20070529/bfcf9db4/attachment-0001.html