<informalfigure>\r
<para>Click the <guibutton>Add Brief Record</guibutton> button.</para>\r
<para><mediaobject>\r
-<alt>screenshot of line item status</alt>\r
+<alt>screenshot of purchase order</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/add-brief-purchaseorder-1.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/briefrecord.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<informalfigure>\r
<para>Enter bibliographic information in the desired fields and click <guibutton>Save Record</guibutton>.</para>\r
<para><mediaobject>\r
-<alt>screenshot of line item status</alt>\r
+<alt>screenshot of new brief record entry</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/add-brief-purchaseorder-2.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/newbrief.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<para>A new line item appears on your purchase order.</para>\r
<note><para>Copies will be automatically added to the line item if you have set a default number of copies for the provider.</para></note>\r
<para><mediaobject>\r
-<alt>screenshot of line item status</alt>\r
+<alt>screenshot of new line item</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/add-brief-purchaseorder-3.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/newbrief2.png" width="100%" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<para>To add additional brief records, select <menuchoice><guimenu>Actions</guimenu>\r
<guimenuitem>Add Brief Record</guimenuitem></menuchoice>.</para>\r
<para><mediaobject>\r
-<alt>screenshot of line item status</alt>\r
+<alt>screenshot of actions menu</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/add-brief-purchaseorder-4.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/newbrief3.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<alt>screenshot of view/place orders</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/view-place-record-1.png" scalefit="0"></imagedata>\r
+ <imagedata fileref="media/view_order.png" width="100%" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<section xml:id="invoice-interface">\r
<title>Invoice Interface</title>\r
\r
-<para>The invoice interface has changed slightly with the new 2.4 development. These changes include:</para>\r
-\r
<itemizedlist>\r
<listitem>\r
<para>Auto-populating of the <guilabel># Billed</guilabel> field.</para>\r
<para>via the <link linkend="copies-add-batch-update">Line Item Batch Updater</link> on a purchase order.</para>\r
</listitem>\r
<listitem>\r
-<para>via the <link linkend="copies-add-screen">Copies Screen</link>on a selection list or purchase order.</para>\r
+<para>via the <link linkend="copies-add-screen">Copies Screen</link> on a selection list or purchase order.</para>\r
</listitem>\r
</itemizedlist>\r
\r
</mediaobject></para>\r
</informalfigure>\r
</listitem>\r
+\r
+<listitem>\r
+<informalfigure>\r
+<para>delayed (blue): Item has been cancelled but debits remain as the item is really delayed.</para>\r
+<para><mediaobject>\r
+<alt>screenshot of line item status</alt>\r
+\r
+<imageobject>\r
+<imagedata fileref="media/statuses-lineitem-8.png" scalefit="0"></imagedata>\r
+</imageobject>\r
+</mediaobject></para>\r
+</informalfigure>\r
+</listitem>\r
</itemizedlist>\r
\r
<caution><para>While there is some overlap in naming, line item statuses and item statuses are not the same thing.</para></caution>\r
<para>The fund in use for all copies on a line item can be updated at any time using the <guilabel>Line Item Batch Updater</guilabel> on a purchase order.</para>\r
\r
<note><para>It is not currently possible to update the fund for individual copies on a line item. It is only possible to update the fund for all copies on a line \r
-item at once.</para>\r
-<para>Currently there is a known bug where debits are not updated if the line item has \r
-the status of <guilabel>on-order</guilabel> or <guilabel>received</guilabel>.</para></note>\r
+item at once.</para></note>\r
\r
<procedure>\r
<step>\r
\r
\r
<abstract>\r
- <para>Bibliographic records and copies can be loaded into the catalogue at different stages of the acquisitions process depending on your preferred\r
-workflow.</para>\r
+ <para>Bibliographic records and copies can be loaded into the catalogue at different stages of \r
+ the acquisitions process depending on your preferred workflow.</para> \r
<para>By default bibliographic records and copies become OPAC visible the moment they are loaded into the catalogue. Libraries that do not wish their on-order\r
materials to be visible to their patrons can set up an OPAC invisible default copy location for the system to use. \r
See <link linkend="onorder-OPAC-invisible">How to Make Your On-orderRecords OPAC Invisible</link> for instruction on setting up and using an OPAC\r
<para>Records are then loaded using the <link linkend="load-bib-vandelay">Vandelay Interface</link>.</para>\r
</step>\r
</procedure>\r
+\r
+<note><para>If your provider supplies you with full MARC records after your orders are submitted these records should be loaded through the \r
+<link xlink:href="http://docs.sitka.bclibraries.ca/Sitka/current/html/marc_batch_import.html#importing_merge">MARC Batch Import/Export</link> interface.\r
+Libraries doing this should use the overlay functionality outlined in <xref linkend="copy_overlay"/>.</para></note>\r
</section>\r
\r
\r
</step>\r
\r
<step>\r
-<para>Select <guilabel>oclc</guilabel> from the <guilabel>Record Source</guilabel> drop down menu.</para>\r
+<para>Select a <guilabel>Record Source</guilabel> from the dropdown. The default is <guilabel>oclc</guilabel>, but choose the one that best matches your \r
+file (eg. ULS, Whitehots etc.) Contact Sitka Support if you have a record source you use on a regular basis that is not listed.</para>\r
</step>\r
\r
<step>\r
\r
</section>\r
\r
-\r
+ <section xml:id="copy_overlay">\r
+ <title>Auto-Overlay In Process Acquisitions Copies</title>\r
+ \r
+ <para>A new feature in Evergreen 2.6 improves the acquisitions copy overlay code by adding broader matching criteria. This feature should be used when loading catalogue records to overlay existing brief records. Selecting the new option <guilabel>Auto Overlay In-process Acquisitions Copies</guilabel> will allow the system to overlay copies which: </para>\r
+ <itemizedlist>\r
+ <listitem><para>Have line item details created by the acquisitions process </para></listitem>\r
+ <listitem><para>Have the same owning_lib as the incoming copies owning_lib</para></listitem>\r
+ <listitem><para>Have a current copy <guilabel>In process</guilabel></para></listitem>\r
+ </itemizedlist>\r
+ <procedure>\r
+ <step><para>Click <guilabel>Cataloguing</guilabel> and select <guilabel>MARC Batch Import/Export </guilabel></para>\r
+ <informalfigure><para><mediaobject>\r
+ <alt>screenshot of Catalogue Menu</alt>\r
+ <imageobject>\r
+ <imagedata fileref="media/catmenu.png" scalefit="0"></imagedata>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure>\r
+ </step>\r
+ <step><para>The <guilabel>MARC File Upload</guilabel> screen will open. For more details about this interface please see <link xlink:title="http://docs.sitka.bclibraries.ca/Sitka/current/html/marc_batch_import.html#importing_merge" xlink:href="http://docs.sitka.bclibraries.ca/Sitka/current/html/marc_batch_import.html#importing_merge"> Importing and Merging MARC records in Batch</link></para>\r
+ <informalfigure><para><mediaobject>\r
+ <alt>screenshot of MARC File Upload</alt>\r
+ <imageobject>\r
+ <imagedata fileref="media/catupload.png" scalefit="0"></imagedata>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure>\r
+ </step>\r
+ <step><para>You may create a new queue for the file you are to upload or use an existing queue. To create a new queue, type in a name for your file in the box beside <guilabel>Create a New Upload Queue.</guilabel> To use an existing queue, choose a queue from the dropdown list beside <guilabel>Add to an Existing Queue.</guilabel></para></step>\r
+ <step><para>Leave <guilabel>SitkaMatch</guilabel> in the <guilabel>Record Match Set</guilabel> box.</para></step> \r
+ <step><para>Select a <guilabel>Record Source</guilabel> from the dropdown. The default is OCLC, but choose the one that best matches your file.</para></step>\r
+ <step><para>Select a <guilabel>Merge Profile</guilabel>. Choose <guilabel>Merge Using INCOMING Record</guilabel> from the dropdown menu.</para></step>\r
+ <step><para>Check <guilabel>Import Non-Matching Records</guilabel> box.</para></step>\r
+ <step><para>Check <guilabel>Auto-Overlay In-Process Acquisitions Copies</guilabel> box.</para></step>\r
+ <step><para>Click <guilabel>Browse...</guilabel> to choose the source MARC file on your computer, then click <guilabel>Upload.</guilabel></para>\r
+ <informalfigure><para><mediaobject>\r
+ <alt>screenshot of MARC File Upload</alt>\r
+ <imageobject>\r
+ <imagedata fileref="media/catupload1.png" scalefit="0"></imagedata>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure>\r
+ </step>\r
+ <step><para>Depending on the size of the file, it may take a while for the uploading to finish. Once it is finished, records will be displayed in <guilabel>Inspect Queue</guilabel> view. The <guilabel>Queue Summary</guilabel> shows the total number of MARC records in the queue, and items contained in these records, if any, how many items have been imported, and how many of them encountered an error when Evergreen attempted to import them.</para></step>\r
+ </procedure>\r
+ </section>\r
\r
</chapter>\r
<alt>screenshot of line item status</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/create-new-purchaseorder-6.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/briefrecord.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<informalfigure>\r
<para>The name of the purchase order is in the top left column of the purchase order. The hyperlinked number is an internal ID number that Evergreen has assigned.</para>\r
<para><mediaobject>\r
-<alt>screenshot of line item status</alt>\r
+<alt>screenshot of purchase order</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/name-purchaseorder-1.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/poname.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<informalfigure>\r
<para>Click on the hyperlinked ID number. A pop up box will appear.</para>\r
<para><mediaobject>\r
-<alt>screenshot of line item status</alt>\r
+ <alt>screenshot of text entry</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/name-purchaseorder-2.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/poname1.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<informalfigure>\r
<para>Enter a new name for your purchase order and click <guibutton>Ok</guibutton>.</para>\r
<para><mediaobject>\r
-<alt>screenshot of line item status</alt>\r
+<alt>screenshot of text entry</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/name-purchaseorder-3.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/poname2.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<informalfigure>\r
<para>The new name will replace the internal ID number as the purchase order's name.</para>\r
<para><mediaobject>\r
-<alt>screenshot of line item status</alt>\r
+<alt>screenshot of purchase order name</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/name-purchaseorder-4.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/poname3.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<alt>screenshot of line item status</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/add-brief-purchaseorder-1.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/briefrecord.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<alt>screenshot of line item status</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/add-brief-purchaseorder-2.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/newbrief.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<alt>screenshot of line item status</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/add-brief-purchaseorder-3.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/newbrief2.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<alt>screenshot of line item status</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/add-brief-purchaseorder-4.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/newbrief3.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<alt>screenshot of add a note</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/add-notes-purchaseorder-1.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/ponotes.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
\r
<para><link linkend="criteria-purchase-order">Activation Criteria</link></para>\r
<para><link linkend="activation-purchase-order">Activate a Purchase Order</link></para>\r
-\r
+<para><link linkend="activation-wo-loaditems">Activate a Purchase Order without loading Items</link></para>\r
+ \r
<simplesect xml:id="criteria-purchase-order">\r
<title>Activation Criteria</title>\r
\r
<alt>screenshot of activate order</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/activate-purchaseorder-4-2.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/activate1.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<alt>screenshot of activate order</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/activate-purchaseorder-5.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/activate2.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
</procedure>\r
\r
</simplesect>\r
+ \r
+ <simplesect xml:id="activation-wo-loaditems">\r
+ <title>Activate a Purchase Order without Loading Items</title>\r
+ \r
+ <para>It is now possible to activate a purchase order without loading items. Once the purchase order has been activated without loading items, it is not possible to load the items. This feature should only be used in situations where the copies have already been added to the catalogue.</para>\r
+ <itemizedlist>\r
+ <listitem><para>Cleaning up pre-acquisitions backlog</para></listitem>\r
+ <listitem><para>Direct purchases that have already been catalogued</para></listitem>\r
+ </itemizedlist>\r
+\r
+ <informalfigure>\r
+ <para><mediaobject>\r
+ <alt>screenshot of activate order</alt>\r
+ <imageobject>\r
+ <imagedata fileref="media/activate3.png" scalefit="0"></imagedata>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure>\r
+ \r
+ </simplesect> \r
\r
</section>\r
\r
<alt>screenshot of cancel order</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/purchase-order-suspend-1.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/cancel.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<alt>screenshot of cancel order</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/purchase-order-cancel-2.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/cancel1.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<alt>screenshot of cancel order</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/purchase-order-suspend-2.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/cancel2.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<alt>screenshot of cancel order</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/purchase-order-cancel-4.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/cancel3.png" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
\r
<step>\r
<informalfigure>\r
-<para>The status of the purchase order becomes <guilabel>cancelled</guilabel> and all the line item bars change to white.</para>\r
+<para>The status of the purchase order becomes <guilabel>cancelled</guilabel> and all the line item\r
+ bars change to blue and "postpone" has been added to each line.</para>\r
<para>Because the purchase order has been suspended rather than cancelled, the funds are still encumbered.</para>\r
<para><mediaobject>\r
<alt>screenshot of cancel order</alt>\r
\r
<imageobject>\r
-<imagedata fileref="media/purchase-order-suspend-3.png" scalefit="0"></imagedata>\r
+<imagedata fileref="media/cancel4.png" width="100%" scalefit="0"></imagedata>\r
</imageobject>\r
</mediaobject></para>\r
</informalfigure>\r
<step>\r
<para>Depending on your computer you may or may not need to select your printer and click <guibutton>OK</guibutton>.</para>\r
</step>\r
+ \r
+ <step>\r
+ <informalfigure>\r
+ <para>The <guilabel>Print Purchase Order</guilabel> option now prints the Purchase Order Name in addition to the Purchase Order ID.</para>\r
+ <para><mediaobject>\r
+ <alt>screenshot of printed purchase order</alt>\r
+ \r
+ <imageobject>\r
+ <imagedata fileref="media/printedpo.png" scalefit="0"></imagedata>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure>\r
+ </step>\r
</procedure>\r
\r
\r
\r
<abstract>\r
<para>At the end of each fiscal year libraries are able to run year end process to close out the year.</para>\r
-<para>Currently Sitka staff guide libraries through a manual year end. In the future libraries will be able to perform year end process on their own \r
-through Evergreen.</para> \r
\r
</abstract>\r
\r
<para>All items to be paid for in the current fiscal year are invoiced for in Evergreen.</para>\r
</listitem>\r
<listitem>\r
-<para>Staff are aware of the dates for the acquisitions year end freeze.</para>\r
+<para>A date on which to run the year end processes has been chosen.</para>\r
+</listitem>\r
+<listitem>\r
+<para>Dates for an acquisitions year end freeze have been selected and staff are aware of what those dates are.</para>\r
</listitem>\r
</itemizedlist>\r
\r
<section xml:id="yearend-sitka-procedure">\r
<title>Sitka Acquisitions Year End Procedure</title>\r
\r
+<note><para>If you run into difficulties at any point in this process please contact Support for assistance.</para></note>\r
+\r
<procedure>\r
<step>\r
<para><emphasis role="bold">Library</emphasis> prepares for year end using the <link linkend="yearend-checklist">Year End Checklist</link>.</para>\r
</step>\r
\r
<step>\r
-<para><emphasis role="bold">Sitka Staff</emphasis> runs fund report for old fiscal year.</para>\r
+<para><emphasis role="bold">Library</emphasis> confirms that the Library Setting <guilabel>Allow funds to be rolled over without bringing the money along</guilabel>\r
+is set to <guilabel>True</guilabel>.</para>\r
</step>\r
\r
<step>\r
</step>\r
\r
<step>\r
-<para><emphasis role="bold">Library</emphasis> confirms that the Library Setting <guilabel>Allow funds to be rolled over without bringing the money along</guilabel>\r
-is set to <guilabel>True</guilabel>.</para>\r
+<para><emphasis role="bold">Library</emphasis> runs fund report for old fiscal year.</para>\r
</step>\r
\r
<step>\r
</step>\r
\r
<step>\r
-<para><emphasis role="bold">Library</emphasis> uses fund report to confirm that the encumbrances and spent totals for the funds in the old and new fiscal years are correct.</para>\r
+<para><emphasis role="bold">Library</emphasis> runs fund report for old and new fiscal year.</para>\r
+</step>\r
+\r
+<step>\r
+<para><emphasis role="bold">Library</emphasis> uses fund reports to confirm that the encumbrances and spent totals for the funds in the old and new fiscal years are correct.</para>\r
+<para>Libraries that do not carry unspent money forward should see balances of zero in their old fiscal year and negative balances in their new fiscal year.</para>\r
</step>\r
\r
<step>\r
<title> Fund Propagation and Rollover</title>\r
\r
<para>The Year End Close-out Operation allows you to deactivate funds for the current year and create analogous funds for the next year. It transfers encumbrances\r
-to the analogous funds, and it rolls over any remaining funds if you checked the rollover box when creating the fund.</para>\r
+to the analogous funds. Depending on the needs of a library it can also transfers any remaining money into the analogous funds or back to the original funding sources.</para>\r
\r
\r
\r
</step>\r
\r
<step>\r
-<para>The <guilabel>Rollover</guilabel> and <guilabel>Propagate</guilabel> check boxes must be checked for every fund that will be rolled over.</para>\r
+<para>The <guilabel>Propagate</guilabel> check box must be checked for every fund that will be rolled over.</para>\r
+<para> The <guilabel>Rollover</guilabel> check box must be checked for every fund where the encumbrances should be rolled over.</para>\r
<para>See <link linkend="create-fund">Create a Fund</link> for information on these check boxes.</para>\r
</step>\r
\r
</step>\r
\r
<step>\r
-<para>The <guilabel>Rollover</guilabel> and <guilabel>Propagate</guilabel> check boxes must be checked for every fund that will be rolled over.</para>\r
+<para>The <guilabel>Propagate</guilabel> check box must be checked for every fund that will be rolled over.</para>\r
+<para> The <guilabel>Rollover</guilabel> check box must be checked for every fund where the encumbrances and money should be rolled over.</para>\r
<para>See <link linkend="create-fund">Create a Fund</link> for information on these check boxes.</para>\r
</step>\r
\r
</step>\r
\r
<step>\r
+<para>The <guilabel>Propagate</guilabel> check box must be checked for every fund that will be rolled over.</para>\r
+<para>See <link linkend="create-fund">Create a Fund</link> for information on these check boxes.</para>\r
+</step>\r
+\r
+<step>\r
<informalfigure>\r
<para>Click <guibutton>Fund Propagation and Rollover</guibutton>.</para>\r
<para><mediaobject>\r
<para>For EDI to work your library must have a SAN and each of your providers must supply you with their SAN.</para>\r
<para>A Standard Address Number (SAN) is a unique 7 digit number that identifies your library. Please contact Sitka Support if your library does not already have a SAN.</para>\r
\r
-<para><emphasis>Entering a Library's SAN</emphasis></para>\r
+<para><emphasis role="bold">Entering a Library's SAN</emphasis></para>\r
<para>These steps only need to be done once per library.</para>\r
\r
<procedure>\r
</step>\r
\r
<step>\r
-<para>Find your library from the tree on the left side of the page and click it to open settings. Multi-branch library systems will see an entry for each branch but should select their system's top organization unit.</para>\r
+<informalfigure>\r
+<para>Find your library from the tree on the left side of the page and click on it to open the settings.</para>\r
+<para> Multi-branch library systems will see an entry for each branch but should select their system's top organization unit.</para>\r
+<para><mediaobject>\r
+<alt>screenshot of EDI</alt>\r
+\r
+<imageobject>\r
+<imagedata fileref="media/enter-library-san-1.png" scalefit="0"></imagedata>\r
+</imageobject>\r
+</mediaobject></para>\r
+</informalfigure>\r
</step>\r
\r
<step>\r
</step>\r
\r
<step>\r
+<informalfigure>\r
<para>Click <guilabel>Save</guilabel>.</para>\r
+<para><mediaobject>\r
+<alt>screenshot of EDI</alt>\r
+\r
+<imageobject>\r
+<imagedata fileref="media/enter-library-san-2.png" scalefit="0"></imagedata>\r
+</imageobject>\r
+</mediaobject></para>\r
+</informalfigure>\r
</step>\r
</procedure>\r
\r
-<para><emphasis>Entering a Provider's SAN</emphasis></para>\r
+<para><emphasis role="bold">Entering a Provider's SAN</emphasis></para>\r
<para>These steps need to be repeated for every provider with which EDI is used.</para>\r
\r
<procedure>\r
</step>\r
\r
<step>\r
+<informalfigure>\r
<para>Click the hyperlinked name of the provider you would like to edit.</para>\r
+<para><mediaobject>\r
+<alt>screenshot of EDI</alt>\r
+\r
+<imageobject>\r
+<imagedata fileref="media/enter-provider-san-1.png" scalefit="0"></imagedata>\r
+</imageobject>\r
+</mediaobject></para>\r
+</informalfigure>\r
</step>\r
\r
<step>\r
</step>\r
\r
<step>\r
+<informalfigure>\r
<para>Click <guilabel>Save</guilabel>.</para>\r
+<para><mediaobject>\r
+<alt>screenshot of EDI</alt>\r
+\r
+<imageobject>\r
+<imagedata fileref="media/enter-provider-san-2.png" scalefit="0"></imagedata>\r
+</imageobject>\r
+</mediaobject></para>\r
+</informalfigure>\r
</step>\r
</procedure>\r
\r
<simplesect xml:id="edi-accounts">\r
<title>Create an EDI Account</title>\r
\r
-<caution><para>You <emphasis>must</emphasis> <link linkend="create-provider">create your provider</link> before you create an EDI account for the provider.</para></caution>\r
+<caution><para>You <emphasis role="bold">must</emphasis> <link linkend="create-provider">create your provider</link> before you create an EDI account for the provider.</para></caution>\r
\r
<procedure>\r
<step>\r
</step>\r
\r
<step>\r
-<informalfigure>\r
+\r
<para>In Evergreen select <menuchoice><guimenu>Admin</guimenu>\r
<guisubmenu>Server Administration</guisubmenu>\r
<guisubmenu>Acquisitions</guisubmenu>\r
<guimenuitem>EDI Accounts</guimenuitem></menuchoice>.</para> \r
-<para><mediaobject>\r
-<alt>screenshot of EDI</alt>\r
-\r
-<imageobject>\r
-<imagedata fileref="media/create-edi-accounts-1.png" scalefit="0"></imagedata>\r
-</imageobject>\r
-</mediaobject></para>\r
-</informalfigure>\r
</step>\r
\r
<step>\r
<itemizedlist>\r
<listitem>\r
<para>In the <guilabel>Label</guilabel> field, enter a name for the EDI account.</para>\r
-<note><para> The name should be entered as PROVIDER_LIBRARYCODE. This enables Sitka Support to easily identify the owning library of the EDI account when troubleshooting.</para></note>\r
+<note><para> The name should be entered as PROVIDERCODE_LIBRARYCODE. This enables Sitka Support to easily identify the owning library of the EDI account when troubleshooting.</para></note>\r
</listitem>\r
<listitem>\r
<para>In the <guilabel>Host</guilabel> field, enter the requisite FTP or SCP information supplied by your provider.</para>\r
</step>\r
\r
<step>\r
+<informalfigure>\r
<para>Click on the link in the <guilabel>Provider</guilabel> field.</para>\r
+<para><mediaobject>\r
+<alt>screenshot of EDI</alt>\r
+\r
+<imageobject>\r
+<imagedata fileref="media/create-edi-accounts-4.png" scalefit="0"></imagedata>\r
+</imageobject>\r
+</mediaobject></para>\r
+</informalfigure>\r
</step>\r
\r
<step>\r
+<informalfigure>\r
<para>Select the EDI account that has just been created from the <guilabel>EDI Default</guilabel> drop down menu.</para>\r
+<para><mediaobject>\r
+<alt>screenshot of EDI</alt>\r
+\r
+<imageobject>\r
+<imagedata fileref="media/create-edi-accounts-5.png" scalefit="0"></imagedata>\r
+</imageobject>\r
+</mediaobject></para>\r
+</informalfigure>\r
</step>\r
\r
<step>\r
\r
<procedure>\r
<step>\r
-<informalfigure>\r
<para>To view the EDI Messages screen, select <menuchoice><guimenu>Admin</guimenu>\r
<guisubmenu>Server Administration</guisubmenu>\r
<guisubmenu>Acquisitions</guisubmenu>\r
<guimenuitem>EDI Messages</guimenuitem></menuchoice>.</para>\r
-<para><mediaobject>\r
-<alt>screenshot of EDI</alt>\r
-\r
-<imageobject>\r
-<imagedata fileref="media/view-edi-messages-1.png" scalefit="0"></imagedata>\r
-</imageobject>\r
-</mediaobject></para>\r
-</informalfigure> \r
</step>\r
\r
<step>\r
<section xml:id="new-features-1">\r
<title>Support PO activation without requiring items</title>\r
<<<<<<< HEAD
+ <para>A new <guilabel>Activate PO Without Loading Items</guilabel> option in the Purchase Order\r
+ allows staff to activate the PO without loading copies into the catalog.</para>\r
+ \r
+ <informalfigure>\r
+ <para><mediaobject>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="media/activate.png"/>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure>\r
+=======
+<<<<<<< HEAD
<para>A new <guilabel>Activate PO Without Loading Items</guilabel> option in the PO allows staff to activate the PO without loading copies into the catalogue.</para>\r
=======
<para>A new <guilabel>Activate PO Without Loading Items</guilabel> option in the PO allows staff to activate the PO without loading copies into the catalog.</para>\r
>>>>>>> sitka_2_6
+>>>>>>> Acq26
</section>\r
\r
<section xml:id="new-features-2">\r
<title>Differentiate between cancelled and "delayed" lineitems</title>\r
+<para>It is now more clear to users when a lineitem has been fully cancelled or if it has been\r
+ cancelled temporarily "delayed".</para>\r
+ <itemizedlist>\r
+ <listitem>\r
+ <para>A line item that has been fully cancelled has a white background</para>\r
+ <informalfigure>\r
+ <para><mediaobject>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="media/cxldline.png"/>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure></listitem>\r
+ \r
+ <listitem><para>A line item that has been temporarily cancelled has a blue background</para>\r
+ <informalfigure>\r
+ <para><mediaobject>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="media/cxldline2.png"/>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure></listitem>\r
+ \r
+ <listitem>\r
+ <para>The line item cancel reason (label) is written next to the non-title attributes in\r
+ the line item list display</para>\r
+ <informalfigure>\r
+ <para><mediaobject>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="media/cxldline1.png"/>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure></listitem>\r
+ </itemizedlist>\r
+\r
</section>\r
\r
<section xml:id="new-features-3">\r
-<title>Opportunistic Acquisitions In-Process Copy Overlay</title>\r
+<title>Auto-Overlay In Process Acquisitions Copies</title>\r
+ <para>Improves existing acquisitions copy overlay code by adding broader matching criteria. By selecting the new option, <guilabel>Auto Overlay In-process Acquisitions Copies</guilabel>, the system will potentially overlay copies which:</para>\r
+<itemizedlist>\r
+ <listitem><para>have associated lineitem details (that is, they were created by the acquisitions process),</para></listitem>\r
+ <listitem><para>that lineitem detail has the same owning_lib as the incoming copy’s owning_lib, and,</para></listitem>\r
+ <listitem><para>the current copy associated with that lineitem detail is <guilabel>In process.</guilabel></para></listitem>\r
+</itemizedlist>\r
+ <informalfigure>\r
+ <para><mediaobject>\r
+ <imageobject>\r
+ <imagedata scalefit="1" fileref="media/marcbatch.png"/>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure>\r
</section>\r
\r
<section xml:id="new-features-4">\r
=======
<para>The <guilabel>Print Purchase Order</guilabel> option now prints the PO Name in\r
addition to the PO ID.</para>\r
+<<<<<<< HEAD
+ \r
+ <informalfigure>\r
+ <para><mediaobject>\r
+ <imageobject>\r
+ <imagedata scalefit="0" fileref="media/printedpo.png"/>\r
+ </imageobject>\r
+ </mediaobject></para>\r
+ </informalfigure>\r
+=======
>>>>>>> sitka_2_6
+>>>>>>> Acq26
</section>\r
\r
</chapter>\r
<section xml:id="acq-workflow-three">\r
<title>Selection By Loading MARC Order Records</title>\r
\r
-<simplesect xml:id="workflow-three-admin">\r
-<title>Admin</title>\r
+<simplesect xml:id="workflow-three-selection">\r
+<title>Selection</title>\r
\r
<procedure>\r
<step>\r
-<para>A 970 holdings tag is set up in the <link linkend="provider-profile">provider's record</link>.</para>\r
+<para>Selector creates a cart on the provider's website and adds the desired items to the cart.</para>\r
</step>\r
+\r
<step>\r
-<para>The 970 holdings tag is set up with the actual provider to contain the following <link linkend="holding-subfield">subfields</link>:</para>\r
-<itemizedlist>\r
-<listitem>\r
-<para>b: barcode</para>\r
-</listitem>\r
-<listitem>\r
-<para>c: call number</para>\r
-</listitem>\r
-<listitem>\r
-<para>m: circ modifier</para>\r
-</listitem>\r
-<listitem>\r
-<para>l: copy location</para>\r
-</listitem>\r
-<listitem>\r
-<para>e: estimated price</para>\r
-</listitem>\r
-<listitem>\r
-<para>f: fund code</para>\r
-</listitem>\r
-<listitem>\r
-<para>n: note</para>\r
-</listitem>\r
-<listitem>\r
-<para>o: owning library</para>\r
-</listitem>\r
-<listitem>\r
-<para>q: quantity</para>\r
-</listitem>\r
-</itemizedlist>\r
+<para>Selector downloads the MARC records for the items in the cart. Contact your provider if you require assistance on how to do this.</para>\r
+</step>\r
+\r
+<step>\r
+<para>Clear the cart. Do NOT submit the cart as an order to your provider via their website.</para>\r
</step>\r
</procedure>\r
\r
-<para>The subfields used will depend on the provider. $o must always be used.</para> \r
</simplesect>\r
\r
<simplesect xml:id="workflow-three-load-marc">\r
<title>Load MARC Order Records</title>\r
\r
<procedure>\r
+\r
<step>\r
<para>Selector/Cataloguer <link linkend="marc-order-records">uploads the MARC record file</link> from the provider.</para>\r
<itemizedlist>\r
<para>A purchase order or selection list may be created out of the MARC records.</para>\r
</listitem>\r
<listitem>\r
-<para>If subfields l, e, f, o, and q are used in the 970 field a purchase order can be created and activated at this time.</para>\r
+<para>If subfields l, e, f, o, and q are used in the <link linkend="workflow-three-admin">970 field</link>\r
+ a purchase order can be created and activated at this time.</para>\r
</listitem>\r
</itemizedlist>\r
</step>\r
<para>Selector/Cataloguer uses the <link linkend="load-bib-vandelay">Vandelay interface</link> to import the bibliographic records into the catalogue.</para>\r
</step>\r
<step>\r
-<para>If not supplied through the 970 field Selector adds the following information to each line item on the purchase order or selection list:</para>\r
+<para>If not supplied through the <link linked="workflow-three-admin">970 field</link> Selector adds \r
+the following information to each line item on the purchase order or selection list:</para>\r
<itemizedlist>\r
<listitem>\r
<para><link linkend="lineitem-estimated-price">estimated price</link></para>\r
</step>\r
</procedure>\r
</simplesect>\r
+\r
+<simplesect xml:id="workflow-three-admin">\r
+<title>Admin</title>\r
+\r
+<procedure>\r
+<step>\r
+<para>A 970 holdings tag is set up in the <link linkend="provider-profile">provider's record</link>.</para>\r
+</step>\r
+<step>\r
+<para>The 970 holdings tag is set up with the actual provider to contain the following <link linkend="holding-subfield">subfields</link>:</para>\r
+<itemizedlist>\r
+<listitem>\r
+<para>b: barcode</para>\r
+</listitem>\r
+<listitem>\r
+<para>c: call number</para>\r
+</listitem>\r
+<listitem>\r
+<para>m: circ modifier</para>\r
+</listitem>\r
+<listitem>\r
+<para>l: copy location</para>\r
+</listitem>\r
+<listitem>\r
+<para>e: estimated price</para>\r
+</listitem>\r
+<listitem>\r
+<para>f: fund code</para>\r
+</listitem>\r
+<listitem>\r
+<para>n: note</para>\r
+</listitem>\r
+<listitem>\r
+<para>o: owning library</para>\r
+</listitem>\r
+<listitem>\r
+<para>q: quantity</para>\r
+</listitem>\r
+</itemizedlist>\r
+</step>\r
+</procedure>\r
+\r
+<para>The subfields used will depend on the provider. $o must always be used.</para> \r
+</simplesect>\r
+\r
+\r
</section>\r
\r
<section xml:id="acq-workflow-preview-items">\r
\r
<copyright>\r
\r
- <year>2014</year>\r
+ <year>2015</year>\r
<holder>BC Libraries Cooperative</holder>\r
</copyright>\r
<legalnotice>\r
</imageobject>\r
</inlinemediaobject>\r
</link></para>\r
- <para>Last updated <date>July 2, 2014</date></para> \r
+ <para>Last updated <date>January 5, 2015</date></para> \r
\r
<?dbhtml-include href="search-box.html"?> \r
\r
font-size: 0.9em;\r
color: #3d3a3a;\r
line-height: 1.2;\r
-background-image: url(sitka.jpg);\r
+background-image: url(sitka.png);\r
background-repeat: no-repeat;\r
background-position: top left;\r
background-color: white;\r
SITKA Public Git / sitka / doc / acquisitions.git / commitdiff
