9xx ordering for Acquisitions (Using ipage) Workflows 3.2 Java Client

Transcription

1 9xx ordering for Acquisitions (Using ipage) Workflows 3.2 Java Client Last Updated September 23, 2009

2 Contents Introduction...3 Setting up 9xx...3 Using 9XX...3 Uploading File to Workflows...4 Loading Bibs with Order Info Report...12 Load Bibs with Order Info Report Log... Error! Bookmark not defined. Load Flat Order Records Report...17 Load Flat Order Record report log... Error! Bookmark not defined. 9xx order loading Java Workflows 3.2 2

3 Introduction 9xx ordering is only available with Ingram s image. If you do not have an account setup with Ingram, you will need to contact Ingram. Setting up 9xx There is some setup that needs to be done on ipage for the 9xx ordering to work with our system. There are specific MARC tags that need to be setup. Please contact SAILS. Using 9XX Once ipage has been setup for ordering, you can create and download your order to your computer. This file will be uploaded and then loaded on Workflows. A MARC record will be loaded or a Call Number will be attached to an existing record in Workflows. You have the option of entering a PO number at the time of download from ipage. Since you are not using Acquisitions then I would recommend letting the report auto-generate an order id since it will not be loading anyway. There are four steps to this process: 1. Downloading the file from ipage to your computer 2. Upload the file from your computer to Workflows 3. Run the Load Bibs with Orders info report (Report template will be setup by SAILS) 4. Run the Load Flat Order Records report (Report template will be setup by SAILS) To be able to view the MARC records downloaded from Ingram, you will need to download the free MARC editing program. This is available at: 9xx order loading Java Workflows 3.2 3

4 Uploading File to Workflows 1. Click on the Utility Toolbar. The Utility wizards will open. 2. Click on MARC Order Import wizard. MARC Order input screen will open. 9xx order loading Java Workflows 3.2 4

5 Click on the gadget to find the source file on your computer. This is the file that was downloaded from ipage. 9xx order loading Java Workflows 3.2 5

6 3. Once you locate the source file. Click OK. 9xx order loading Java Workflows 3.2 6

7 4. You need to enter a destination file name. Name the file something that will be easily remembered. Example would be RA Do not begin the file name with a Click on Import. You will be asked if the diskette is ready. 9xx order loading Java Workflows 3.2 7

8 6. Click Yes. You will be asked if there are any more files to upload. 9xx order loading Java Workflows 3.2 8

9 7. Click No. The Source file and destination file will be cleared from the screen. 9xx order loading Java Workflows 3.2 9

10 8. To verify that your Bibliographic file loaded. Click on the Bib files to load tab. 9xx order loading Java Workflows

11 9. The file that you uploaded should appear here. 10. If the file appears in this list then Click Cancel. 9xx order loading Java Workflows

12 Loading Bibs with Order Info Report 1. Click on the Reports toolbar. 2. Click on Schedule New Reports, the reports templates tab will open. Your Load reports should appear in this tab. 9xx order loading Java Workflows

13 3. Highlight the Load Bibs with Orders info. 4. Click on Setup and Schedule. The report template will open to the basic tab. 9xx order loading Java Workflows

14 5. Click on the Load tab. The load options screen open. 9xx order loading Java Workflows

15 6. Click on the File to load. Select the file that you uploaded (destination file). Please do not change any of the other options in this report. Changing these options may result in your order not being loaded correctly or duplicate bib records. 7. Click Run Now. 8. Click on the Finished Reports wizard. 9xx order loading Java Workflows

16 9. Verify that Load Bibs with Order Info report that you ran has the status of OK. 10. Click View to display the report log. If your Records or Call Numbers are not added please contact SAILS. 11. The Report log will always contain a few errors because you are not using Acquisitions. Following errors may appear: **Cannot link order to fund: fund ID not found 4 order record(s) read. 4 bad input record(s) encountered. 0 New order record(s) created. 0 existing order record(s) updated. 0 orderline record(s) created. 9xx order loading Java Workflows

17 Example of a Load Bib with Orders Report Log Report Log for Catalog Load and Order Record Extraction Report biborderload scheduled as Load Bibs with Order Info Load bib records and extract order records. UNICORN Flatskip9xx Records started on Friday, March 27, 2009, 10:17 AM MARC records will be read from standard input. MARC records will be written to standard output. The default record format will be MARC. 0 marc record(s) read. 4 marc record(s) processed. 0 marc record(s) in error. 4 record(s) written. UNICORN Flatskip9xx Records finished on Friday, March 27, 2009, 10:17 AM UNICORN marc Prep started on Friday, March 27, 2009, 10:17 AM Raw MARC records will be read from standard input. Raw MARC records will be written to standard output. MARC records with errors will be saved in /s/sirsi/unicorn/rpttemp/rpt28367.pr eperr. 4 PLAINVILLE ACQPL item(s) encountered. 4 Total item(s) encountered. 4 marcin record(s) read. 4 marc record(s) read. 0 marc record(s) in error. 4 marc record(s) output. UNICORN marc Prep finished on Friday, March 27, 2009, 10:17 AM UNICORN Catalog Match started on Friday, March 27, 2009, 10:17 AM Records will be interpreted according to the following format: ACQ. The flexible key will be output in 035. Bibliographic records will be matched by flexible key OR the text index. The OCLC number (001) will be used as the flexible key. The ISBN (020) will be used as the flexible key. The LCCN (010) will be used as the flexible key. The ISSN (022) will be used as the flexible key. The local number (035) will be used as is for the flexible key. Bibliographic records will be matched by ISBN (020). Bibliographic records will be matched by LC Control Number. Bibliographic records will be matched by Other standard identifier (024). Bibliographic records will be matched by Publisher number (028). All occurrences of the specified flexible key fields will be compared to the flexible key index for matching. MARC records will be read from standard input. MARC records will be written to standard output. MARC records with errors will be saved in /s/sirsi/unicorn/rpttemp/rpt28367.ma tcherr. Matched MARC records will be saved in /s/sirsi/unicorn/marcordimp/bibs/work/ma tched MARC records with no match will be saved in /s/sirsi/unicorn/marcordimp/bibs/w ork/unmatched BRS/Search-Engine v.62 started for catmatch1 4 line(s) read. 9xx order loading Java Workflows

18 4 catalog record(s) read. 0 catalog record(s) in error. 3 catalog record(s) matched. UNICORN Catalog Match finished on Friday, March 27, 2009, 10:17 AM UNICORN Catalog MARC Load started on Friday, March 27, 2009, 10:17 AM Records will be interpreted according to the following format: ACQ. The item number will be updated. The MARC record will be updated. The price will be updated. The year of publication will be updated. Records not matched will be loaded, but records which match will be rejected. Bibliographic records will be matched by flexible key. MARC records will be read from standard input. ACQPL will be used as the default holding code. Bibliographic records will be matched by flexible key OR the text index. The OCLC number (001) will be used as the flexible key. The ISBN (020) will be used as the flexible key. The LCCN (010) will be used as the flexible key. The ISSN (022) will be used as the flexible key. The local number (035) will be used as is for the flexible key. All occurrences of the specified flexible key fields will be compared to the flexible key index for matching. Bibliographic records will be matched by ISBN (020). Bibliographic records will be matched by LC Control Number. Bibliographic records will be matched by Other standard identifier (024). Bibliographic records will be matched by Publisher number (028). Matching MARC records that contain a "d" in the Leader/05 will be loaded. Items will be created only based on SIRSI <u>view Holdings</u> entry 999. An AUTO item call number will be generated by UNICORN. The call number will include only subfields a. An AUTO item call number will be generated by UNICORN. All subfields will be included in the call number. MARC records with errors will be saved in /s/sirsi/unicorn/rpttemp/rpt28367.lo aderr. Entries/tags listed in the junk tag file junktag will be removed. Subject headings with second indicator of 2, 1, 3, 4, 5, 7, or 6 will be removed BRS/Search-Engine v.62 started for catload1 1 PLAINVILLE ACQPL item(s) created. 1 Total item(s) created. 0 Total item(s) ignored. 1 callnum(s) created. 1 bib record(s) read. 0 bib record(s) in error. 1 bib record(s) loaded. 0 bib record(s) cancelled. 0 full bib record(s) replaced. UNICORN Catalog MARC Load finished on Friday, March 27, 2009, 10:17 AM UNICORN Catalog Merge started on Friday, March 27, 2009, 10:17 AM Records will be interpreted according to the following format: ACQ. The SIRSI number (035) will be used as the flexible key. All occurrences of the specified flexible key fields will be compared to the flexible key index for matching. Bibliographic records will be matched by flexible key. MARC records will be read from standard input. 9xx order loading Java Workflows

19 LC call number will come from the first tag 050. All subfields will be included in the call number. The entry will be merged if the entry ID is 999, 949, or 949 An entry will not be merged if an identical entry is already present. Existing occurrences of merged entries will be deleted. MARC records with errors will be saved in /s/sirsi/unicorn/rpttemp/rpt28367.me rgeerr. 3 line(s) read. 3 catalog record(s) read. 0 catalog record(s) in error. 3 catalog record(s) replaced. UNICORN Catalog Merge finished on Friday, March 27, 2009, 10:17 AM UNICORN extract MARC orders started on Friday, March 27, 2009, 10:17 AM MARC records will be read from standard input. Flat records will be written to standard output. Records with errors will be saved in /s/sirsi/unicorn/rpttemp/rpt28367.orderer r. Orders will be created for vendor INGRAM. One order ID will be assigned for all records. Orders will be created for the new fiscal cycle The order library will be set to PLAINVILLE. Orders created will be of type FIRM. The batch user ID for transactions will be KRISTIN. The batch workstation name for transactions will be PCGUI-EDIT. The currency will be set to US. The order date mailed will be updated to the current date. The order date to claim will be set if it is not already entered. The order date to cancel will be set if it is not already entered. 4 catalog record(s) read. 0 bad record(s) encountered. 2 callnum(s) created. 4 order record(s) written. UNICORN extract MARC orders finished on Friday, March 27, 2009, 10:17 AM ***************************************************************************** ** ***************************************************************************** ** Flat order records have been written to /s/sirsi/unicorn/marcordimp/orders/ o ***************************************************************************** ** ***************************************************************************** ** 9xx order loading Java Workflows

20 UNICORN load orders started on Friday, March 27, 2009, 10:17 AM Flat records will be read from standard input. Batch server transactions will be written to the apiserver. Keys of new or updated orders will be written to standard output. Records not matched will be loaded, and records which match will be updated. The batch user ID for transactions will be KRISTIN. The batch workstation name for transactions will be PCGUI-EDIT. The default library will be PLAINVILLE. Test mode: no changes will be made to the databases. **Cannot link order to fund: fund ID not found *** DOCUMENT BOUNDARY *** FORM=LDORDER.ORDR_ID. apo-4.vend_id. aingram.ordr_libr. aplainville.fiscal_cycle. a2009.ordr_type. afirm.ordr_date_ready. a ordr_date_mailed. a line_item_begin..line_item_id. a line_titleid. a line_vend_curr. aus.line_copies. a1.line_date_mailed. a line_item_end..fund_segment_begin..line_fund_id. apladult.line_fund_copies. a1.fund_segment_end..dist_segment_begin..holding_code. aacqpl.line_dist_copies. a1.dist_segment_end. **Cannot link order to fund: fund ID not found *** DOCUMENT BOUNDARY *** FORM=LDORDER.ORDR_ID. apo-4.vend_id. aingram.ordr_libr. aplainville.fiscal_cycle. a2009.ordr_type. afirm.ordr_date_ready. a ordr_date_mailed. a line_item_begin..line_item_id. a line_titleid. a line_vend_curr. aus.line_copies. a1.line_date_mailed. a line_item_end..fund_segment_begin..line_fund_id. apladult.line_fund_copies. a1.fund_segment_end..dist_segment_begin..holding_code. aacqpl.line_dist_copies. a1 9xx order loading Java Workflows

21 .DIST_SEGMENT_END. **Cannot link order to fund: fund ID not found *** DOCUMENT BOUNDARY *** FORM=LDORDER.ORDR_ID. apo-4.vend_id. aingram.ordr_libr. aplainville.fiscal_cycle. a2009.ordr_type. afirm.ordr_date_ready. a ordr_date_mailed. a line_item_begin..line_callnum. axx( ).line_titleid. a line_vend_curr. aus.line_copies. a1.line_date_mailed. a line_item_end..fund_segment_begin..line_fund_id. apladult.line_fund_copies. a1.fund_segment_end..dist_segment_begin..holding_code. aacqpl.line_dist_copies. a1.dist_segment_end. **Cannot link order to fund: fund ID not found *** DOCUMENT BOUNDARY *** FORM=LDORDER.ORDR_ID. apo-4.vend_id. aingram.ordr_libr. aplainville.fiscal_cycle. a2009.ordr_type. afirm.ordr_date_ready. a ordr_date_mailed. a line_item_begin..line_callnum. axx( ).line_titleid. a line_vend_curr. aus.line_copies. a1.line_date_mailed. a line_item_end..fund_segment_begin..line_fund_id. apladult.line_fund_copies. a1.fund_segment_end..dist_segment_begin..holding_code. aacqpl.line_dist_copies. a1.dist_segment_end. 96 line(s) read. 4 order record(s) read. 4 bad input record(s) encountered. 0 New order record(s) created. 0 existing order record(s) updated. 0 orderline record(s) created. UNICORN load orders finished on Friday, March 27, 2009, 10:17 AM 9xx order loading Java Workflows

22 UNICORN item printing started on Friday, March 27, 2009, 10:17 AM The catalog key will be read from standard input. The output will be a record by record list. Catalog bibliographic information will be written to standard output. Entry IDs:ALL. Entry IDs will precede catalog data. Subfield codes will appear in output. The report title option will be used. 1 catalog record(s) printed. 0 catacnt record(s) printed. 0 call number record(s) printed. 0 item record(s) printed. 0 itemacnt record(s) printed. UNICORN item printing finished on Friday, March 27, 2009, 10:17 AM LOADED BIB RECORDS Produced Friday, March 27, 2009 at 10:17 AM 000: : aam5a0n 008: : a090326s : : a c$ : : a c$ : 00 : a : 1 : ahamilton, Laurell K. 245: 10 : aanita Blake, Vampire Hunter: The Laughing Corpse 260: : bmarvel Comics c : : ap. cm. 949: : fpladult hacqpl okstest p19.99 q1 950: : aa 999: : hacqpl.report..title. LOADED ORDERS.end. *** DOCUMENT BOUNDARY *** FORM=LDORDER.ORDR_ID. apo-4.vend_id. aingram.ordr_libr. aplainville.fiscal_cycle. a2009.ordr_type. afirm.ordr_date_ready. a ordr_date_mailed. a line_item_begin..line_item_id. a line_titleid. a line_vend_curr. aus.line_copies. a1.line_date_mailed. a line_item_end..fund_segment_begin..line_fund_id. apladult.line_fund_copies. a1.fund_segment_end..dist_segment_begin..holding_code. aacqpl.line_dist_copies. a1 9xx order loading Java Workflows

23 .DIST_SEGMENT_END. *** DOCUMENT BOUNDARY *** FORM=LDORDER.ORDR_ID. apo-4.vend_id. aingram.ordr_libr. aplainville.fiscal_cycle. a2009.ordr_type. afirm.ordr_date_ready. a ordr_date_mailed. a line_item_begin..line_item_id. a line_titleid. a line_vend_curr. aus.line_copies. a1.line_date_mailed. a line_item_end..fund_segment_begin..line_fund_id. apladult.line_fund_copies. a1.fund_segment_end..dist_segment_begin..holding_code. aacqpl.line_dist_copies. a1.dist_segment_end. *** DOCUMENT BOUNDARY *** FORM=LDORDER.ORDR_ID. apo-4.vend_id. aingram.ordr_libr. aplainville.fiscal_cycle. a2009.ordr_type. afirm.ordr_date_ready. a ordr_date_mailed. a line_item_begin..line_callnum. axx( ).line_titleid. a line_vend_curr. aus.line_copies. a1.line_date_mailed. a line_item_end..fund_segment_begin..line_fund_id. apladult.line_fund_copies. a1.fund_segment_end..dist_segment_begin..holding_code. aacqpl.line_dist_copies. a1.dist_segment_end. *** DOCUMENT BOUNDARY *** FORM=LDORDER.ORDR_ID. apo-4.vend_id. aingram LOADED BIB RECORDS Produced Friday, March 27, 2009 at 10:17 AM 9xx order loading Java Workflows

24 .ORDR_LIBR. aplainville.fiscal_cycle. a2009.ordr_type. afirm.ordr_date_ready. a ordr_date_mailed. a line_item_begin..line_callnum. axx( ).line_titleid. a line_vend_curr. aus.line_copies. a1.line_date_mailed. a line_item_end..fund_segment_begin..line_fund_id. apladult.line_fund_copies. a1.fund_segment_end..dist_segment_begin..holding_code. aacqpl.line_dist_copies. a1.dist_segment_end. LOADED BIB RECORDS Produced Friday, March 27, 2009 at 10:17 AM 9xx order loading Java Workflows

25 Load Flat Order Records Report 1. Click on Schedule New reports wizard. 9xx order loading Java Workflows

26 The reports template tab will open. The Load Flat Order Records Report will appear in this tab. 2. Highlight the Load Flat Order Records report. 3. Click on Setup and Schedule. The report template will open to the basic tab. 9xx order loading Java Workflows

27 4. Click on the Order File Selection tab. 9xx order loading Java Workflows

28 5. Click on the download arrow to choose the File to load. The file names are automatically created by Load bibs with order info report. File names are in this format 4 digit year month day 00 library policy no. file number o o You should only load files that have your library policy number. 9xx order loading Java Workflows

29 6. Click Run Now. 7. Click on the Finished reports button. 9xx order loading Java Workflows

30 8. Verify that the Load Flat Order Records reports status is OK. 9. Click on View to display the Report log. Be sure that the View log option is selected. 9xx order loading Java Workflows

31 9xx order loading Java Workflows