<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	   <channel>
	   	
		  <title>																																																				Evergreen Acquisitions															 from Howe Library</title>
		  <link>http://engagedpatrons.org/Blogs.cfm?SiteID=2391&amp;BlogID=137</link>
		  <description>For selectors, technical services staff and administration staff to communicate and share information about Evergreen Acquisitions.
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	</description>
	      <pubDate>Thu, 04 Aug 2011 00:00:00 GMT</pubDate>
		  <copyright>Copyright 2026 Howe Library</copyright>
		  <language>en-us</language>
		  <lastBuildDate>Tue, 09 Jun 2026 13:18:33 CDT</lastBuildDate>
		
		  	<item>
				<title>Those Pesky ISBNs!</title>
				<link>http://engagedpatrons.org/Blogs.cfm?SiteID=2391&amp;BlogID=137&amp;BlogPostID=14069</link>
				<description><![CDATA[We have had some titles not accepted by Ingram because of a problem with the ISBN field.&nbsp; The ISBN is correct &amp; the title is available from Ingram, but when the ISBN was entered (either keyed in or copied &amp; pasted) an extra space was added at the end of the field.&nbsp; When the EDI order arrives at Ingram it sees a 14 digit field instead of the normal 13 digits (it&#39;s a machine, what do you expect?).&nbsp; It doesn&#39;t know what to do with this data so it refuses this line item. &nbsp;<br />  <br />  If you are copying &amp; pasting the ISBN, please try to copy only the 13 digits &amp; try not to get an extra space at either end of the field.&nbsp; If you do grab an extra space, be sure to remove it before you save the template.&nbsp;&nbsp;<br />  <br />  If you are keying in the ISBN, try not to add a space at the end of this field.&nbsp;&nbsp;<br />  <br />  The EDI function works really well &amp; is a very efficient way to order.&nbsp; However, the downside is that it is absolutely exacting and unforgiving of even the slightest variation.&nbsp; <P>]]></description>
				<author>Pam</author>
	           <pubDate>Fri, 30 May 2014 13:39:32 GMT</pubDate>
				</item>
		  
		  	<item>
				<title>More Forbidden Characters!</title>
				<link>http://engagedpatrons.org/Blogs.cfm?SiteID=2391&amp;BlogID=137&amp;BlogPostID=9592</link>
				<description><![CDATA[The week before last I posted about the problem with the ? in titles causing the electronic orders to fail.&nbsp; Well, that&#39;s not the only punctuation problem!&nbsp;<br />  <br />  We&#39;ve learned, due to another EDI failure this week, that these characters/punctuation will also cause failure:<br />  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;   (plus sign)<br />  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :&nbsp; (colon)<br />  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#39; (apostrophe)<br />  &nbsp;Preceeding these characters with a ? will release the character and restore the meaning, for example the title 2 2 would be entered 2? 2; a title with a colon would be entered ?:, a title with question mark would be entered ??.<br />  <br />  Rather than worry about coding your title field this way, just ignore these characters when creating your records; simply skip over them.&nbsp;<br />  <br />  Don&#39;t worry about titles that you have already entered in your selection lists.&nbsp; Mary will edit out these offending characters before she creates the purchase order.&nbsp; But do start ignoring them when entering new titles.<br />   <P>]]></description>
				<author>Pam</author>
	           <pubDate>Wed, 31 Aug 2011 11:08:19 GMT</pubDate>
				</item>
		  
		  	<item>
				<title>Progress Report</title>
				<link>http://engagedpatrons.org/Blogs.cfm?SiteID=2391&amp;BlogID=137&amp;BlogPostID=9501</link>
				<description><![CDATA[Everyone is doing a great job entering order records and preparing them for ordering. The&nbsp; process has been working well.&nbsp; We are doing frequent small orders which seems to be the best for both the ordering/receiving functions as well as invoicing.&nbsp;<br />  <br />  The EDI ordering with Ingram is&nbsp; working smoothly for the most part.<br />  There are a few occasional glitches that cause the order to fail or individual line items to be cancelled.&nbsp;<br />  <br />  Equinox says they are learning a lot from us!&nbsp; Here is what we&#39;ve learned so far:<br />  <br />  1. If there are any spaces preceeding or after the ISBN the ISBN field will not send properly and Ingram will cancel the line item.&nbsp;<br />  <br />  The title can still be ordered, we order it via iPage (we add a note in the note field of the line item that it was ordered @ iPage &amp; the date). but it does add a couple of steps to our process.&nbsp; It has happened on a few occasions that most and in one case all line items in a purchase order have been cancelled because of a space in the ISBN fields.&nbsp;<br />  <br />  So, we would ask that when you are entering the ISBN that you make sure that you are at the beginning of the field when you start typing the ISBN.&nbsp; Do not hit the space bar when you have finished entering the ISBN,&nbsp; just click on Save record.<br />  <br />  2.&nbsp; If there is a quesiton mark in a title, the entire Purchase Order will fail to send via EDI.&nbsp; Evidently in the software coding, the character ? means something other than a question mark so the entire process will stop.&nbsp;<br />  <br />  Titles that have question marks should be entered without the ?.&nbsp; The title will display incorrectly for only a short time as when the full Marc record is loaded, it will have the correct punctuation.&nbsp; This is likely a temporary problem and will hopefully be fixed in a future release.<br />  <br />  Equinox was able to fix the overlay function so that when we upload the Marc records&nbsp; most are now properly overlaying the order bibs.&nbsp; That&#39;s progress!<br />  <br />  <br />  <br />   <P>]]></description>
				<author>Pam</author>
	           <pubDate>Wed, 17 Aug 2011 17:19:10 GMT</pubDate>
				</item>
		  
		  	<item>
				<title>Successful EDI Launch</title>
				<link>http://engagedpatrons.org/Blogs.cfm?SiteID=2391&amp;BlogID=137&amp;BlogPostID=9439</link>
				<description><![CDATA[Our EDI (Electronic Data Interchange) testing is complete and we have successfully placed several orders from Ingram via EDI!&nbsp; All Ingram orders will now be automatically submitted electronically via EDI.<br />  <br />  It&#39;s a very cool, efficient process and we are very pleased with ourselves!!<br />  Each Ingram account has a separate EDI account set-up in Evergreen.<br />  When Mary activates a Ingram purchase order, it is sent via ftp to the Ingram server.&nbsp; There is a built in delay before the order is transmitted to Ingram.&nbsp; Ingram then transmits a confimation report with the status of each line item: confirmed, backordered or cancelled.<br />  <br />  For backordered items, we are adding a note in the line item stating that it&#39;s backordered and the date.&nbsp; If a title you have ordered hasn&#39;t arrived, check the notes field to see if it&#39;s on backorder.<br />  <br />  A couple of titles have been cancelled via EDI but are in fact available at Ingram and have been ordered via iPage.&nbsp; Those titles will also have a note in the line item stating that they were cancelled via EDI but ordered on iPage and the date.&nbsp; I&#39;m investigating this issue with Ingram EDI support. &nbsp;<br />  <br />  While this was a bear to implement and the testing was rocky, it is a big advancement for us and is one of the benefits of open source.&nbsp; Innovative&#39;s electronic ordering module was way out of our price range. &nbsp;<br />   <P>]]></description>
				<author>Pam</author>
	           <pubDate>Thu, 04 Aug 2011 10:19:03 GMT</pubDate>
				</item>
		  
		</channel>
	</rss> 