[OPEN-ILS-DOCUMENTATION] ***SPAM*** Re: EDI Setup

[Ben Shum]

Hi Tim,

The additional information about SAN codes seems useful to me, but I 
would note that there is a place to edit the SAN codes for org unit 
addresses in the staff client.  It was added to the org unit part of the 
server admin area as another field when editing and creating org unit 
addresses.

See James' patch on that here in case maybe you don't have this on your 
system? 
http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=41358314b81a6d238f5433da70963aaed00a70f5

-- Ben

On 10/21/2011 9:07 AM, Tim Spindler wrote:
> I think we should up date these instructions 
> (http://docs.evergreen-ils.org/2.0/draft/html/acq_admin_edi.html). 
>  See what I added at the bottom.
>
>
>       EDI Accounts
>
> Create EDI Accounts to communicate electronically with providers.
>
> 1.
>
>     Create a label. The label allows you to differentiate between
>     accounts for the same provider. No limits exist on the number of
>     characters that can be entered in this field.
>
> 2.
>
>     Enter a host. Your provider will provide you with the requisite
>     FTP or SCP information.
>
> 3.
>
>     Enter the username that has been supplied by your provider.
>
> 4.
>
>     Enter the password that has been supplied by your provider.
>
> 5.
>
>     Enter account information. This field enables you to add a
>     supplemental password for entry to a remote system after log in
>     has been completed. This field is optional for the ILS but may be
>     required by your provider.
>
> 6.
>
>     Select an owner from the drop down menu. The owner indicates the
>     organizational units whose staff can use this EDI account. This
>     menu is populated with the shortnames that you created for your
>     libraries in the organizational units tree (See Admin ? Server
>     Administration ? Organizational Units).
>
>     The rule of parental inheritance applies to this list.
>
> 7.
>
>     The Last Activity updates automatically with any inbound or
>     outbound communication.
>
> 8.
>
>     Select a provider from the drop down menu to whom this account
>     belongs.
>
> 9.
>
>     Enter a path. The path indicates the remote location on the server
>     from which files are pulled in to the ILS.
>
>10.
>
>     Enter the incoming directory. This directory indicates the
>     location on your local network to which the files download.
>
>11.
>
>     Enter the vendor account number supplied by your provider.
>
>12.
>
>     Enter the vendor account code supplied by your provider.
>
> 13. Click Save.
>
> The Standard Address Number (SAN) for the library also has to be added 
> into  SAN column of the table actor.org_address for the given 
> organizational unit.  This currently can only be done through Postgres 
> and there is no client interface,
>
> -- 
>
> Tim Spindler
>
> Manager of Library Applications
>
> tspindler at cwmars.org <mailto:tspindler at cwmars.org>
>
> 508-755-3323 x20
> IM: tjspindler (AOL, meebo, google wave)
>
> C/W MARS, Inc.
>
> 67 Millbrook St, Suite 201
>
> Worcester, MA 01606
> http://www.cwmars.org <http://www.cwmars.org/>
>
> *P**   Go Green - **Save a tree! Please don't print this e-mail unless 
> it's really necessary.*
>
>
>
>
> _______________________________________________
> OPEN-ILS-DOCUMENTATION mailing list
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation

-- 
Benjamin Shum
Open Source Software Coordinator
Bibliomation, Inc.
32 Crest Road
Middlebury, CT 06762
203-577-4070, ext. 113

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.georgialibraries.org/pipermail/open-ils-documentation/attachments/20111021/d905cde5/attachment-0001.htm>