Setting up a New ILLiad User - University of Montana



System INSTRUCTIONMANUALFORILLIADBYPAT GAUCINOVEMBER 2, 2012Table of Contents TOC \o "1-4" \h \z \u Setting up a New ILLiad User PAGEREF _Toc339611658 \h 5Client Side PAGEREF _Toc339611659 \h 51.Install ILLiad Client PAGEREF _Toc339611660 \h 51a. What is ILLiad PAGEREF _Toc339611661 \h 51b. Run ILLiad Client Executable PAGEREF _Toc339611662 \h 51c. Setup Atlas SQL Alias Manager PAGEREF _Toc339611663 \h 52.Add User to ILLiad Staff Manager PAGEREF _Toc339611664 \h 63.Add ILLiad Addons PAGEREF _Toc339611665 \h 64.Odyssey Helper PAGEREF _Toc339611666 \h 65.Map Drives – Use Same Lettering as ILLiad users refer to these by letter PAGEREF _Toc339611667 \h 76.Setup ILL Email in Outlook PAGEREF _Toc339611668 \h 77.Give user Administrative Rights on the local machine PAGEREF _Toc339611669 \h 78.Access to Voyager Catalog PAGEREF _Toc339611670 \h 7Server side PAGEREF _Toc339611671 \h 7Upgrading ILLiad PAGEREF _Toc339611672 \h 8Server Side PAGEREF _Toc339611673 \h 8Client Side PAGEREF _Toc339611674 \h 9ILLiad Printing PAGEREF _Toc339611675 \h 9Components of ILLiad Printing PAGEREF _Toc339611676 \h 9Customizing ILLiad Printer Templates PAGEREF _Toc339611677 \h 13Atlas ILLiad 8.3 Documentation for Customizing Printer Templates PAGEREF _Toc339611678 \h 13Customization Manager Key - printdocumentspath PAGEREF _Toc339611679 \h 13Modifying Microsoft Word 2010 ILLiad Printer Templates PAGEREF _Toc339611680 \h 13Location of Print Templates PAGEREF _Toc339611681 \h 17Customizing ILLiad Email Templates PAGEREF _Toc339611682 \h 17Email Templates PAGEREF _Toc339611683 \h 17Reporting PAGEREF _Toc339611684 \h 19Annual Statistical Report for Interlibrary Loan PAGEREF _Toc339611685 \h 20Example of Annual Statistical Report PAGEREF _Toc339611686 \h 20Explanation of Annual Statistical Report PAGEREF _Toc339611687 \h 22Courier Reports PAGEREF _Toc339611688 \h 22Example of Courier Report PAGEREF _Toc339611689 \h 23MZK Reports PAGEREF _Toc339611690 \h 24FY Reports PAGEREF _Toc339611691 \h 24Misc Reports PAGEREF _Toc339611692 \h 24Configuring Email Routing PAGEREF _Toc339611693 \h 24Overview PAGEREF _Toc339611694 \h 24Adding Records to the EmailRouting Table PAGEREF _Toc339611695 \h 25Understanding the FileNameLoan and FileNameArticle Columns PAGEREF _Toc339611696 \h 25System Routing Rules PAGEREF _Toc339611697 \h 26System Routing PAGEREF _Toc339611698 \h 26The Routing Table PAGEREF _Toc339611699 \h 26The Match String PAGEREF _Toc339611700 \h 27Double Quotation Marks in ILLiad Routing Rules PAGEREF _Toc339611701 \h 27Creating a New Routing Rule PAGEREF _Toc339611702 \h 28Using an Existing Rule as a Template PAGEREF _Toc339611703 \h 28Creating a Routing Rule from Scratch PAGEREF _Toc339611704 \h 28General Guidelines for Creating Routing Rules PAGEREF _Toc339611705 \h 29Creating Custom Queues PAGEREF _Toc339611706 \h 30Manage Addons PAGEREF _Toc339611707 \h 30OCLC Article Exchange Rule PAGEREF _Toc339611708 \h 31CCC GetItNow PAGEREF _Toc339611709 \h 31Distributing Addons PAGEREF _Toc339611710 \h 31What is Article Exchange PAGEREF _Toc339611711 \h 31How it works: PAGEREF _Toc339611712 \h 32ILLiad Addon Technical Overview PAGEREF _Toc339611713 \h 32Addon Folder Structure PAGEREF _Toc339611714 \h 32Lua Files PAGEREF _Toc339611715 \h 33Config.xml PAGEREF _Toc339611716 \h 33Local Settings PAGEREF _Toc339611717 \h 34Distributing Addons PAGEREF _Toc339611718 \h 34Default Addons PAGEREF _Toc339611719 \h 36ILLiad on the Web PAGEREF _Toc339611720 \h 36Web Pages that were Changed – using text messaging PAGEREF _Toc339611721 \h 36Web Pages that are changed the Most PAGEREF _Toc339611722 \h 37Web Pages that need to be corrected PAGEREF _Toc339611723 \h 37“Not Wanted After” Date PAGEREF _Toc339611724 \h 38Database Manager PAGEREF _Toc339611725 \h 38Miscellaneous Information PAGEREF _Toc339611726 \h 39Directory of Butte and Dillon for ILLiad PAGEREF _Toc339611727 \h 39Locked Out User PAGEREF _Toc339611728 \h 40Web Alerts PAGEREF _Toc339611729 \h 40Connection Manager and/or Odyssey Manager PAGEREF _Toc339611730 \h 42No Incoming Requests in Awaiting Lending Request Processing PAGEREF _Toc339611731 \h 43ERROR 1625 – When user is running a ILLiad Client Upgrade PAGEREF _Toc339611732 \h 43Items Delivered to Web PAGEREF _Toc339611733 \h 43Butte and Dillon PAGEREF _Toc339611734 \h 43New Server for ILLiad PAGEREF _Toc339611735 \h 44Latest ILLiad Server Upgrade PAGEREF _Toc339611736 \h 44ODBC – Is needed to connect Microsoft Access with Illiad database PAGEREF _Toc339611737 \h 44SQL Server management Studio on Forms Server PAGEREF _Toc339611738 \h 44Contact OCLC ILLiad Support PAGEREF _Toc339611739 \h 45Examples of ILLiad Web Reports PAGEREF _Toc339611740 \h 45Flow of Scanned files and Odyssey PAGEREF _Toc339611741 \h 45Setting up a New ILLiad UserClient SideInstall ILLiad ClientWhat is ILLiadRun ILLiad Client ExecutableSetup Atlas SQL Alias ManagerAdd user to ILLiad Staff ManagerAddonsOdyssey HelperMap DrivesSetup ILL Email in OutlookGive user Administrative Rights on the local machineAccess to Voyager CatalogInstall ILLiad Client 1a. What is ILLiadOCLC ILLiad is a model, implemented in software, of the interlibrary loan process. The Interlibrary loan is a system whereby libraries lend and borrow material to and from each other for their patrons. There are two sides to the ILL process: Supplying materials to other libraries for their users (Lending) and obtaining materials from other libraries for Mansfield Library users (Borrowing).1b. Run ILLiad Client ExecutableThe client executable can be found at the following places:\\fileserve\datafile\NEWPCs\illiad\ This has been manually downloaded by a Systems ILLiad Staff person from the atlas website and placed here for easy access by other Systems people.\\forms\illiad\Client_Exe_files Atlas Website under “Looking for the latest product documentation?” Click on the ILLiad n.n (latest version) and find the Client Executable Files.Run the ILLiad Client Executable clicking next when prompted and using the default settings. If the software won’t install then right click on the executable and run as administrator.1c. Setup Atlas SQL Alias ManagerEnter the following information.Database ConnectionServer : 10.8.150.216Database Name: ILLDataConnect Timeout: 15Username : leave blankPassword: leave blankLogon Accounts Click the Logon.txt Button (nothing will open)Type the following in the lower right portionUsername: MTGPassword: MTGPasswordClick the right most Save button. You will now see MTG appear under Logon AccountsClick the Save button (third button from left). A window opens to save file. Name file “logon” (without the quotes) and save to the root of the ILLiad folder. Lastly click the Set Default button.*If you need to access Atlas SQL Alias Manager once you exit, right click on icon and run as administrator.Add User to ILLiad Staff ManagerCopy another MTG ILLiad user (pmarek is a good one to copy) giving new user a Username and Password. This gives the user access to ILLiad and what Transaction Permissions they have. Do not give a regular user access to Customization, Database or Staff Manager Access.Add ILLiad AddonsThis process has been automated by the AddonDirectory key in the Customization Manager. The only file that needs to be added to the new user is the LocalSettings.xml. Copy this file from another regular ILLiad user and place it in the same location on new computer. The location is c:\program file (x86)\ILLiad\Addons. If the user does not have the program file (x86) folder then use program file. For more information, see Manage Addons.Odyssey HelperThis is now included by default with the ILLiad client installer and the OdsseyHelper.exe file is installed to the ILLiad\Odyssey folder, and a shortcut is created on the desktop.Two keys in the Customization Manager set the designated folder for the TIF and PDF files used by Odyssey. These have already been set.OdysseyHelperImagesPathDocDelOdysseyHelperImagesPathLendingMap Drives – Use Same Lettering as ILLiad users refer to these by letterH\\forms\convertJ\\fileserve\lendingK\\forms\pdfM\\fileserve\illN\\fileserve\odysseyS\\fileserve\illiadscansW\\fileserve\workZ\\forms\mtgprintSetup ILL Email in OutlookYour Name: Mansfield LibraryEmail Address: library.ill@umontana.eduAccount Type: IMAPIncoming Mail Server: mail.lib.umt.eduOutgoing Mail Server: smtp.umt.eduUser Name: library.illPassword: 1llstudentDirections for setting up ILL EmailGo into Account Settings from the File Tab of Outlook 2010.Click on the E-mail tab and click New. Select E-mail Account and select Next. Select manually configure server settings or additional server types and select Next. Select Internet E-Mail then Next. Enter information, select Next then Finish.Give user Administrative Rights on the local machineThis is necessary so that user can do the client ILLiad upgrades and use ILLiad.Access to Voyager CatalogThis should already be done as part of Systems general image install.Server sideBe sure that the user has been added to the ILLiad Group on the Jefferson server.Upgrading ILLiadWhenever there is an upgrade there will be release notes on the Atlas website. Email the link to the Release Notes to the ILLiad department users. There are minor and major upgrades. Minor ones are usually fixes and minor enhancements. Minor upgrades involve upgrading the ILLiad client software whereas major upgrades could impact the ILLiad database, Connection Manager Customization Manager, System Manager, Staff Manager, Web Interface, Web Reports, Odyssey, Odyssey Manager and Odyssey Helper. Major upgrades should be communicated with the ILLiad users and scheduled. Doing a major upgrade will impact not only our users but also the users at Butte (MZJ) – Montana Tech and Dillon (MZK) The University of Montana Western. There contact information is listed in the Directory of Butte and Dillon for ILLiad.Server SideSteps to Upgrade ILLiad:Remote into the Forms Server.Run the c:\illiad\Admin\ILLiadUpdate.exe file. This updates the ILLiadUpdate.exe file.When there is an option to backup the database, do so. 91440048641000Enter the sa password. This is found in the ILLiad Passwords.txt file found in the tech$ folder on the fileserve server.The next screen will look similar to this window, but will have, I believe, the ILLiadUpdate.exe file listed and maybe others. Click the “Start ILLiad Server Update” button, bottom right.6985-17589500Next, run the c:\illiad\Admin\ILLiadUpdate.exe file again and go through steps b and c again. This time many files will be listed in the Available Updates window and the actual update will occur. Client SideWhen users start the ILLiad client they will get a notice to upgrade the client and will select Yes. Occasionally there are some issues with Admin permissions. If so, go to the ILLiad Client from the Start Bar (not a shortcut on desktop), right click and choose Run as Administrator.ILLiad PrintingComponents of ILLiad PrintingIn order to print most ILLiad documents used in the course of processing Borrowing, Document Delivery, and Lending requests, ILLiad uses a combination of document templates (Word Documents) and output data files (.xls files). During each print process, the data files and the document templates are merged together to create the new, complete document to be printed. The ways that these different documents and files interact are outlined in the charts that follow:BorrowingPrint ProcessFrom this QueuePerform this ActionMerges with this Word DocData File UsedALA RequestAwaiting ALA Request ProcessingFrom Borrowing Ribbon (Processing Group): Print ALA RequestsBorrowingALARequests.docALA.xlsArticle LabelsAwaiting Post Receipt ProcessingFrom Borrowing Ribbon (Receive Requests Group): Print ReceivesBorrowingArticleLabels.docArticle.xlsArticle SlipsAwaiting Post Receipt ProcessingFrom Borrowing Ribbon (Receive Requests Group): Print ReceivesBorrowingArticleSlips.docArticle.xlsLoan LabelsAwaiting Post Receipt ProcessingFrom Borrowing Ribbon (Receive Requests Group): Print ReceivesBorrowingLoanLabels.docLoan.xlsLoan SlipsAwaiting Post Receipt ProcessingFrom Borrowing Ribbon (Receive Requests Group): Print ReceivesBorrowingLoanSlips.docLoan.xlsNotification LetterAwaiting Customer ContactFrom Customer Contact Screen. Customer Contact Ribbon (Process Group): Print NotificationsBorrowingNotify.docBorrowingNotifications.xlsPrint CancellationN/AFrom Borrowing Processing Ribbon (Process Group): Cancel Request. Check Move to Print Queue and click Cancel RequestBorrowingPrintCancellation.doc Note: This document is not included in the default ILLiad installation. It must be created by the Institution wishing to use it.BCancel.xlsPrint Multiple RequestsN/AFrom Request Form. Borrowing Processing Ribbon (Printing Group): Add to Print QueueBorrowingPrintRequest.doc Note: This default template must be opened and merged manually when batch printing.Printed.xlsReturn Address LabelsAwaiting Return Label PrintingFrom Borrowing Ribbon (Returns Group): Print ReturnsBorrowingReturnAddressLabels.docReturnsL.xlsReturn SlipsAwaiting Return Label PrintingFrom Borrowing Ribbon (Returns Group): Print ReturnsBorrowingReturnSlips.docReturns.xlsPrint RequestN/AFrom Request Form. Borrowing Processing Ribbon (Printing Group): Print RequestPrintRequest.docPrintRequest.xlsDocument DeliveryPrint ProcessFrom this QueuePerform this ActionMerges with this Word DocData File UsedArticle SlipsAwaiting DD Stacks SearchingFrom Document Delivery Ribbon (Search Stacks Group): Print Pull SlipsDocDelArticleSlips.docDocDelP.xlsArticle Mailing LabelsAwaiting DD Stacks SearchingFrom Document Delivery Ribbon (Search Stacks Group): Print Pull SlipsDocDelArticleMailingLabels.docDocDelP.xlsLoan LabelsAwaiting DD Stacks SearchingFrom Document Delivery Ribbon (Search Stacks Group): Print Pull SlipsDocDelLoanLabels.docDocDelL.xlsLoan Mailing LabelsAwaiting DD Stacks SearchingFrom Document Delivery Ribbon (Search Stacks Group): Print Pull SlipsDocDelLoanMailingLabels.docDocDelL.xlsInvoiceN/A See Note 2 Below.From Document Delivery Ribbon (Billing Group): Move Invoices to Print Queue There are two ways to generate invoices: Item by Item and by Time Period.DocDelInvoice.docDocDelBill.xlsLendingPrint ProcessFrom this QueuePerform this ActionMerges with this Word DocData File UsedArticle SlipsAwaiting Stacks SearchingFrom Lending Ribbon (Search Stacks Group): Print Stacks Search ItemsLendingArticleSlips.docStacksP.xlsLoan SlipsAwaiting Stacks SearchingFrom Lending Ribbon (Stacks Search Group): Print Stacks Search ItemsLendingLoandSlips.docStacksL.xlsLoan LabelsAwaiting Stacks SearchingFrom Lending Ribbon (Search Stacks Group): Print Stacks Search ItemsLendingLoanLabels.docStacksL.xlsLoan Shipping LabelsAwaiting Shipping Label PrintingFrom Lending Ribbon (Search Stacks Group): Print Shipping LabelsLendingLoanShippingLabels. docShpStkL.xlsArticle Shipping LabelsAwaiting Shipping Label PrintingFrom Lending Ribbon (Search Stacks Group): Print Shipping LabelsLendingArticleShippingLabels .docShpStkP.xlsShipping Labels - All See Note 1 Below.Awaiting Shipping Label PrintingFrom Lending Ribbon (Search Stacks Group): Print Shipping LabelsLendingLoanShippingLabels.doc OR LendingArticleShippingLabels.docShpStk.xlsOverdue Letter 1Item ShippedFrom Lending Overdues Form: Lending Overdues Ribbon (Process Group): Send Overdue NoticesLendingOverdueLetter1.docLendingOverdues1.xlsOverdue Letter 2Item ShippedFrom Lending Overdues Form: Lending Overdues Ribbon (Process Group): Send Overdue NoticesLendingOverdueLetter2.docLendingOverdues2.xlsOverdue Letter 3Item ShippedFrom Lending Overdues Form: Lending Overdues Ribbon (Process Group): Send Overdue NoticesLendingOverdueLetter3.docLendingOverdues3.xlsInvoiceN/A See Note 2 Below.From Lending Ribbon (Billing Group): Move Invoices to Print Queue See Note 3 Below.LendingInvoice.docLendBill.xlsPrint RequestN/AFrom Request Form. Lending Processing Ribbon (Printing Group): Print RequestPrintRequest.docPrintRequest.xlsPrint Multiple RequestsN/AFrom Request Form. Lending Processing Ribbon (Printing Group): Add to Print QueueLendingPrintRequest.doc Note: Note: This default template must be opened and merged manually when batch printingLPrinted.xlsNotes About Printing.Note 1. If you wish to combine the Article and Loan Shipping Labels into one print document rather than handling them separately, you may use either the LendingLoanShippingLabels.doc or the LendingArticleShippingLabels.doc. Whichever you use will need to be altered to look for the ShipStk.xls data file.Note 2. When printing Lending or Document Delivery Invoices, the current queue or status of the transaction does not matter as long as the transaction has been marked as found and the billing charges have been applied. Invoices may be generated at any point in the process after that.Note 3. There are two ways to generate invoices:1. Item by Item: Invoices are printed after the requested item has been marked as found (at the same time as the Address Labels).2. By Time Period & Lender Symbol (Bulk): Invoices are generated and printed at any time after the item has been sent to the requesting institution.If Billing for Document Delivery or Lending is turned on for your institution, your method of invoicing may be set to one or the other using the Customization Manager.Customizing ILLiad Printer TemplatesAtlas ILLiad 8.3 Documentation for Customizing Printer Templates Manager Key - printdocumentspathThe PrintDocumentsPath key tells were the Print Templates are located. This is currently set to \\10.8.150.216\MTGPrint.Modifying Microsoft Word 2010 ILLiad Printer TemplatesIf modifying template(s) from a computer that doesn’t use ILLiad on a daily basic then copy the xls file(s) from an active ILLiad user to your computer.The specific xls file to copy, based on the template to be changed, is listed in the Components of ILLiad Printing and in the Atlas documentation. Use the link above.The location to copy the xls file from is c:\users\(username)\my documents\ILLiad\Print and paste it to the same location on your computer.Copy Template from \\forms\MTGPrint (sharename) or \\forms\illiad\print\ to local computer.Open document in Microsoft Word. A window similar to this will be displayed: Select YesAfter selecting Yes, an Error window similar to this will be displayed: Take careful note of the filename with the .xls extension. This should match the file you copied in step 1b. In this example it is DocDelP.xls, click OK.A third Window called Data Link Properties will open: Click OK.The Fourth Window - After selecting OK the Error window from Step 5 will display again:Click OK.The Fifth Window “Microsoft Word” will now display: Click on Find Data Source…Browse on local computer to Documents – ILLiad – Print and choose filename and choose the xls file you noted from step 6.Now select the proper Table name. Either LegacyQueue$ or PrintQueue$. For MTG’s templates use PrintQueue$. The LegacyQueue worksheet exists in the .xls files so that Word templates created for ILLiad 7.4 and prior will still work without changing merge field names. We suggest using the PrintQueue worksheet for any new Word templates you create as they have more complete and clear field names, e.g., Transactions.TransactionNumber versus TRANSACTIO.Next choose SAVE AS. Give Template a different name and save to local computer. This step is very necessary for the location of the .xls file to be saved. If you just choose Save this information will not be saved with the document. Close Document.Open New Template you created in step 14.The following window will open:Select Yes.The document will now open so modifications can be made.To add a Merge Field click on Mailings and then Insert Merge Field.To see all the Merge Codes press Alt-F9After all changes are made Save document and then rename to the original document name, test and then save to the MTGPrint sharename or (\\forms\ILLiad\Print) directory.NOTE: Adding New Merge FieldsILLiad exports certain tables to the .xls files for Microsoft Word to read into the templates. Usually those tables include:Transactions: Data related to specific requestsUsers: Data related to patrons using ILLiadLenderAddresses: Data related to other libraries, both borrowing and lendingLocalInfo: Data related to your libraryYou can add any ILLiad field related to the current record by clicking the Insert Merge Field drop-down box on the Mailings tab of the Word template.Clicking a field name on the list will add the record to the mail merge document and show a merge tag within the template.The word merge fields for a specific print template can be viewed in the PrintQueue worksheet of that template's .xls file.For example, to view the merge fields available in the PrintRequest.doc Word template, look in the PrintQueue of the PrintRequest.xls file.Note that if the xls file does not exist, you will have to print the document once to generate the .xls file in order to view the PrintQueue worksheet.Editing is easier if the MERGEFIELD coding is not visible. To toggle the codes off and on, use Alt F9.See the images to the right for examples of adding merge fields, the fields in the XLS file and in the document.Location of Print Templates \\10.8.150.216\MTGPrint or \\forms\MTGPRINTThere are several locations that you will find these templates on the local computer, but none of them are used because only the templates on the Forms server are used as indicated by the PrintDocumentsPath key in the Customization Manager. These different locations were from older versions of ILLiad and whenever a new client install is done the print templates are put in the following folder: Program Files or Program Files (x86), ILLiad, Print. Customizing ILLiad Email TemplatesEmail TemplatesMTG Email Location: On Forms server at C:\illiad\Email, \\Forms\MTGEmail\ (Sharename)Borrowing E-MailsIs In Customization ManagerE-mail Process From This Queue Action Performed Email Template We use TemplateYBorrowing-EmailArticle Received - Hold for Pickup Awaiting Customer Contact Contact Customers illart.txt YNArticle Received - Mailed to Address Awaiting Customer Contact Contact Customers illartdel.txt NYBorrowing-EmailLoan Received - Hold for Pickup Awaiting Customer Contact Contact Customers illloan.txt YNLoan Received - Mailed to Address Awaiting Customer Contact Contact Customers illloandel.txt NNMultiple Items Received Awaiting Customer Contact Contact Customers illmnotify.txt NYOdyssey–EmailUnder 2 subheadingsElectronic Delivery In Electronic Delivery Processing Deliver Electronic Article ElecDel.txt YYBorrowing-CancellationsCancel Request Varies Cancel Request Cancel.txt YNNE-mail Route Article Varies E-mail Routing routeart.txt, branchart.txt NNNNE-mail Route Loan Varies E-mail Routing routeloan.txt, branchloan.txt NNYBorrowing-Customer ClearanceCustomer Clearance N/A Customer Cleared clearcus.txt NNCustomer Clearance N/A Automatically Clears the Customer autoclearcust.txt NYBorrowing-Customer ClearanceCustomer Clearance N/A Customer Disavowed disavow.txt NNMerge Customers N/A Customer Records Merged mergecus.txt NYBorrowing-OverduesOverdues Checked out to Customer Overdue Notification 1 Sent overdue1.txt YYBorrowing-OverduesOverdues Checked out to Customer Overdue Notification 2 Sent overdue2.txt YYBorrowing-OverduesOverdues Checked Out to Customer Overdue Notification 3 Sent overdue3.txt YYWeb Interface-Authentication Under 2 subheadings Password Reset N/A Resets the Borrowing Password passwordreset.txt YDocument Delivery E-MailsIs In Customization ManagerE-mail Process From This Queue Action Performed Email Template We use TemplateYDoc Del-EMailArticle Received - Hold for Pickup Awaiting Doc Del Customer Contact Contact Customers illddart.txt YNArticle Received - Mailed to Address Awaiting Doc Del Customer Contact Contact Customers illddartdel.txt NYDoc Del-EMailLoan Received - Hold for Pickup Awaiting Doc Del Customer Contact Contact Customers illddloan.txt YNLoan Received - Mailed to Address Awaiting Doc Del Customer Contact Contact Customers illddloandel.txt NNMultiple Items Received Awaiting Doc Del Customer Contact Contact Customers ddmnotify.txt NYOdyssey-Email OdysseyOdyssey-Email DocDelElectronic Delivery Awaiting Document Delivery Scanning Scan and Deliver Article ElecDel.txt YYBorrowing-CancellationsCancel Request Varies Cancel Request Cancel.txt YLending E-MailsIs In Customization ManagerE-mail Process From This Queue Action Performed Email Template We use TemplateYLending-CancellationsCancel Request Varies Cancel Request lendingcancel.txt NYLending-CancellationsPassword Reset N/A Resets the Lending Password lendpasswordreset.txt YYLending-OverduesOverdues Checked out to Customer Overdue Notification 1 Sent lendingoverdue1.txt YYLending-OverduesOverdues Checked out to Customer Overdue Notification 2 Sent lendingoverdue2.txt YYLending-OverduesOverdues Checked Out to Customer Overdue Notification 3 Sent lendingoverdue3.txt YYLending-CancellationsCancel Request Varies Cancel Request Cancel.txt YReportingQueries are run from the ILLiad Access database. The database is located here: \\fileserve\tech$\illiad reporting\ILLiad.accdb. Web Reports are ran by the ILLiad Manager and can be accessed within ILLiad or through a browser at this URL address: previous Reports and Stats are located in the sub folder called Reports and Stats. \\fileserve\tech$\illiad reporting\Reports and Stats.Each time you open the Access database and choose to run a report it will ask for the SQL Server Login ID and password. The Login ID is: illiadlink. The password is stored in the \\fileserve\tech$\illiad report\ILLiad passwords.txt file.Annual Statistical Report for Interlibrary LoanExample of Annual Statistical ReportANNUAL STATISTICAL REPORTINTERLIBRARY LOANJULY 1, 2009 – JUNE 30, 2010Year2005-20062006-20072007-20082008-20092009-2010Total Requests Processed41,33538,19035,58833,35632,341Query – FY Total Requests ProcessedTotal Requests Unfilled644156111261061838Query – FY Total Requests UnfilledUnfilled request % of total1%4%3%3%2.5%DETAILED FILLED BORROWING TRANSACTIONSRequests2005-20062006-20072007-20082008-20092009-2010Web ReportsArticles/nonreturnables82966984575950333997Borrowing – Requests Finished and Cancelled-Article-MTGTotal Number of Requests:Loans/returnables90338053948869276467Borrowing – Requests Finished and Cancelled-Loan-MTGTotal Number of Requests:Document Delivery7901095131315512470Document Delivery – Requests Finished and Cancelled-Both—MTGTotal Number of Requests:TOTALS18,11916,13216,56013,51112,934DETAILED FILLED LENDING TRANSACTIONSRequests2005-20062006-20072007-20082008-20092009-2010Web ReportsArticles/nonreturnables13,19111,265865293029699Lending – Requests Filled and Unfilled-Article-MTG-AllTotal Number of Requests:Loans/returnables93819232925094828912Lending – Requests Filled and Unfilled-Loan-MTG-AllTotal Number of Requests:TOTALS22,57220,49717,90218,78418,611MT STATE REIMBURSEMENT TRANSACTIONSRequests2005-20062006-20072007-20082008-20092009-2010Loaned to other libraries5,6575,027339547194861Query – Fy MT Reimbursement Lending TotalBorrowed from other libraries1,8531,587142715061691Query – Fy MT Reimbursement Borrowing TotalFY 2010 ILL Transactions by User Type: Query – FY Total Active ILL users 1 (Percentages provided by ILLiad Manager) Report gives total amounts.Total number of active ILL users in ILLiad 1142 (about % of total number UM students, staff, faculty)Total number of active Grad ILLiad users 423 (about 37% of total ILL users)Total number of active Undergrad ILLiad users 408 (about 36% of total ILL users)Total number of active Faculty ILLiad users 201 (about 18% of total ILL users)Total number of active Staff ILLiad users 84 (about 7% of total ILL users)In FY 1990 ILL Transactions by User Type = 48% Grad Students31% Faculty 15% Undergrad Students 6% StaffExplanation of Annual Statistical ReportThe last column explains how the information was gathered. FY Total Requests Processed Query – Open the Fiscal Year Query in design mode and change the TransactionDate date, save and close. Next run the FY Total Requests Processed Query. Export the report to Excel. Send to ILLiad Manager.FY Total Requests Unfilled Query - Open the Fiscal Year Query in design mode and change the TransactionDate date, save and close. Next run the FT Total Requests Unfilled Query. Export the report to Excel. Send to ILLiad Manager.FY MT Reimbursement Lending Total Query - Open the Fy MT Reimbursement Lending Total Query in design mode and change the date, save and then run the report. Take note of the total, no need to export report. Send total to ILLiad Manager.FY MT Reimbursement Borrowing Total Query – Open the Query in design mode and change the date, save and then run the report. Take note of the total, no need to export report. Send total to ILLiad Manager.FY Total Active ILL Users 1 Query – Open the FY Total Active ILL Users Query in design mode and change the TransactionDate date, save and close. Next run the FY Total Active ILL Users 1 Query. Export the report to Excel. Open the Excel report and total the CountOfUse column. This is the Total number of active ILL users in ILLiad total. Send total to ILLiad Manager.Courier ReportsThe ILLiad Assistant Manager will contact the Systems ILLiad staff person with a list of libraries Code participating in the Courier Program and what month(s) for the report. The resulting report is then emailed to the ILLiad Assistant Manager.Open the Courier Libraries Preliminary Query in design mode and enter the list of library Codes in the LendingLibrary field. Enter the date in the TransactionDate field, save and close query.Run the Courier Libraries for Monthly Report. Export the report to Excel.There is a third query called Courier libraries Detail Info which was used by the Systems ILLiad staff person for verifying purposes only. This is not needed for the Courier Report.Open the Excel Monthly Report. We need to have borrowing and lending separated with totals as well as have them grouped together by library with totals. Copy the information and paste it below the information that is already there. Then you can sort this copied information by Lending Library and then by ProcessType. There is a template called Courier Libraries template.xlsx that you can copy and paste information into. The graphs will need to have the series and the Axis Labels reset. This is done by selecting the graph and then selecting “Select Data” from the Design tab on the Chart Tools Tab.Example of Courier ReportMZK ReportsThere are three reports that are run each month for the month before and sent to Denice Rust d_rust@umwestern.edu. MZK Borrowing, MZK Cancelled and MZK Lending. Access the queries through the ILLaid Access database. Open each query, change the TranacationDate date, run the query, export to Excel and email.FY ReportsThere are several FY reports in the ILLiad Access database too numerous to list here. Each one gives a good description in the title. Open the one you want to run in design mode to see if it’s calling another query and what information needs to be changed such as the date field.Misc Reports There are two queries in the ILLiad Access database called Borrowing Turnaround time and Lending Turnaround time which call several other queries. This is NOT working correctly but left them in the list of queries for future development. Currently the ILLiad Manager is using the ILLiad Web Reports for the Turnaround time reports.Many other queries are available. Some have been used once and others many times. These can be used as is or used to develop other queries.Configuring Email Routing This information was taken from Atlas’ documentation: Email routing is a tool that allows you to use email templates in ILLiad to standardize communications between ILL staff and ILLiad users while simultaneously routing items to the appropriate status.OverviewEmail routing is a tool that allows you to use email templates in ILLiad to standardize communications between ILL staff and ILLiad users while simultaneously routing items to the appropriate status.Sending a message to a user to notify them that an item request has been cancelled is an example of what can be done with email routing.Email routing is configured using the EmailRouting table located in the System | Email section of the configuration manager. The email templates used in item email routing are the default .txt templates or the email templates created under the E-mail Templates tab in the customization manager.See Creating and Editing Email Templates for an overview and guidelines on creating and working with email templates.See Routing Items Using Email Routing to learn how to route items in the client using email routing. Adding Records to the EmailRouting TableIn order for the email routing feature to work, the EmailRouting table record must include the process type, a name for the email routing rule, the status you want the item to be routed to when the email is sent, and the specific email templates to be used for articles and loans. You can also specify a default subject line and default To and From address information. If no information is supplied in the address columns it will be filled in with the information from the Request form. Add a new entry to the EmailRouting table by placing correct values in the columns listed below. Process Type: Borrowing or LendingName: The name of the new email routing rule. This will show in the dropdown menu box of the Send E-mail command in the client.Default To Address: Use if you want the email to go to a specific email address.Default To Name: Use if you want the email to be addressed to a specific person or department.Default CC Address: Use if you want the email to CC to a specific email address.Default Subject: Use this line to specify the purpose for the email. While not a required field, it is convenient to have this line automatically entered on the email form.Default From Address: Use if you want the email to go to a specific email address. If left blank, defaults to the address value in EmailFromAddress.Default From Name: Use if you want the email to go to a specific email address. If left blank, defaults to the address value in EmailFromName.Default Status: The status that you want the item to route to when the email is sent.File Name Loan: The email template to use with the email routing rule when the item is a Loan.File Name Article: The email template to use with the email routing rule when the item is an Article.Understanding the FileNameLoan and FileNameArticle ColumnsThe FileNameLoan and FileNameArticle columns allow you to create one routing rule for two separate article and loan email templates. If you have two distinct templates that you use for a routing process for your articles and loans, entering the names of the templates into these columns tells ILLiad which template to used based off of whether the Loan or Article type is selected in the Request form. Note that the complete email template filename needs to be entered as a value in these fields. For example, a .TXT email template called AwaitingSpecialProcessing.txt needs to be entered as AwaitingSpecialProcessing.txt. An email template created in the customization manager does not have a .txt suffix and should be entered as AwaitingSpecialProcessing.System Routing RulesThis information was taken from Atlas’ documentation: System RoutingThe process of automatically routing transactions to other statuses or process types in ILLiad using the Routing table and routing rules is referred to as System Routing. System Routing is one of the most powerful functions of the ILLiad system. By using the Routing table, you can change default ILLiad processes by having the system automatically skip or add steps to the basic ILL process.The Routing TableThe Routing table, located at System | Routing | Routing, stores any routing rules that are created for your ILLiad system. As various functions are performed in ILLiad, these rules are applied according to the criteria specified in each rule definition. The Routing table is made up of several fields and associated values. These are:Field NameDescriptionRuleNoThis is a unique rule number that you assign to the rules. The first rule that applies to a given transaction based on the rule definition is applied to the transaction.RuleActiveThis is set to Yes or No, activating or deactivating this rule. A rule with a RuleActive value of No will be ignored by the system.ProcessTypeThis specifies the ProcessType (Borrowing, Lending or Doc Del) to which a given rule applies. A transaction must have a matching ProcessType value before the rule will be applied.TransactionStatusThis specifies the TransactionStatus to which a given rule applies. A transaction must have a matching TransactionStatus value before the rule will be applied. This value may be any legitimate ILLiad status, including any existing Custom Queues.MatchStringThis specifies the remainder of the query string that must be matched by a transaction before the rule is applied. For Borrowing, this query string should only reference the Users(ALL) and Transactions tables, unless a compound routing rule is used. For Lending, this query string should only reference the LenderAddresses(ALL) and Transactions tables, unless a compound routing rule is used. See further explanation below.NewProcessTypeThis specifies the new process type to which the transaction will be routed when the rule is applied. This value does not usually need to change. It is possible to route transactions back and forth between Borrowing and Doc Del. Lending transactions cannot change RequestType.NewTransactionStatusThis specifies the new Transaction Status to which the transaction will be routed when the rule is applied. This value may be any legitimate ILLiad status, including any existing Custom Queues.RuleDescriptionThis describes what the rule is intended to do.The Match StringThe Match String is arguably the most important piece of the Routing table. Each time the status of a transaction is changed by the ILLiad client, the system also runs a query to cycle through any rules that exist in the Routing table and determine if any active routing rules should be applied to that transaction. When the system runs this query, it attaches the MatchString value for each active routing rule to the end of the query to determine what rule, if any, should be applied to each transaction at that time.The query used to apply routing rules is as follows:Select * from Transactions t, Users u where t.Username = u.Username and t.TransactionNumber =? andIn the above query, the value is replaced by the actual TransactionNumber value of the transaction being processed. Likewise, the value is replaced by the actual MatchString value for each Routing rule in turn.Thus the Matchstring value is where you may set the conditions that distinguish one routing rule from another. These conditions, coupled with the other conditions specified in a routing rule, determine which transactions are impacted by the rule and which are not.As stated in the above table, in Borrowing, this query string should only reference the Users(ALL) and Transactions tables, unless a compound routing rule is used. In Lending, this query string should only reference the LenderAddresses(ALL) and Transactions tables, unless a compound routing rule is used.Double Quotation Marks in ILLiad Routing RulesIn accordance with current SQL query standards, ILLiad 8.0 does not support the use of double quotation marks in routing rule match strings. Any quotation marks being used in existing routing rule match strings should be replaced with single quotation marks as shown in following example.Old routing rule match string that uses double quotation marks:u.Status = "Faculty" AND t.RequestType = "Loan"New routing rule match string after changing double quotation marks to single quotation marks:u.Status = 'Faculty' AND t.RequestType = 'Loan'If an existing routing rule is matching against a value that contains a single quotation mark in the value string (ie: u.LastName = "D'Angelo"), the double quotation marks should be replaced with single quotation marks and the existing single quotation mark should be replaced with two single quotation marks as shown in the following example.Old routing rule match string that uses double quotation marks:u.Status = 'Faculty' AND u.LastName = "D'Angelo"New routing rule match string after changing double quotation marks to single quotation marks. Note that the formatting for the u.LastName value here is [single quote]D[single quote][single quote]Angelo[single quote]:u.Status = 'Faculty' AND u.LastName = 'D''Angelo'These changes can be made by opening the ILLiad Customization Manager and navigating to the Routing table under System | Routing.Creating a New Routing RuleOpen the Customization Manager and go to System | Routing | Routing. This will display the Routing table. You can use the New Record and Copy Record buttons in the Table Options section of the Home Ribbon to create a new Routing Rule from scratch or copy an existing record as use it as a template.Using an Existing Rule as a TemplateTo use an existing routing rule as a template for a new one, select a rule that is as similar as possible to the one you wish to create and click the Copy Record button.This will copy the existing rule as a new rule and allow you to edit the fields in the Edit Row grid before adding it to the table. Change the keys as appropriate to create the new routing rule. Once you have the rule set up as you desire, click the Save button to add it to your Routing table.Creating a Routing Rule from ScratchTo create a new routing rule, click the New Record button to open a blank Edit Row grid below the table. Edit the fields in the grid, completing the keys as appropriate to create the new routing rule. Once you have the rule set up as you desire, click the Save button to add it to your Routing table.General Guidelines for Creating Routing RulesRouting Rules should be created so that no two routing rules apply to the same transaction at the same time. This means that the ProcessType, TransactionStatus, and MatchString values, taken collectively, should be unique for each rule in the table.Routing Rules should be created so that they are unique to your process tracking. In other words, the same rule should not apply to the same transaction multiple times during the course of standard processing. Routing Rules should be created to be unique to a specific step of your process.Routing Rules should only reference the Users(ALL), Transactions, and/or LenderAddresses(ALL) table.The Routing Rule MatchString value cannot exceed 255 characters.TIP. Routing Rules Across Modules SUMMARYWhen setting up ILLiad routing rules that originate in the Borrowing module and route transactions to the Doc Del module (or vice versa), the ProcessType value in the Routing table should be set to the transaction's original module and the NewProcessType value should be set to the destination module. EXAMPLESTo route a transaction to a special status in Document Delivery when it is routed to Doc Del from Borrowing, you would need to set up a routing rule like the following example: Field NameValue| RuleNo | 6 |RuleActiveYesProcessTypeBorrowingTransactionStatusAwaiting Document Delivery ProcessingMatchStringWhatever your criteria might be. Example: u.Status = 'Faculty'NewProcessTypeDoc DelNewTransactionStatusAwaiting Special Doc Del ProcessingRuleDescriptionMoves transactions meeting my criteria to Awaiting Special Doc Del Processing when routed to Doc Del from Borrowing.To route a transaction to a special status in Borrowing when it is routed back to Borrowing from Doc Del, you would need to set up a routing rule like the following example: Field NameValue| RuleNo | 6 |RuleActiveYesProcessTypeDoc DelTransactionStatusAwaiting Request ProcessingMatchStringWhatever your criteria might be. Example: u.Status = 'Faculty'NewProcessTypeBorrowingNewTransactionStatusAwaiting Failed Doc Del Faculty ProcessingRuleDescriptionMoves transactions meeting my criteria to Awaiting Failed Doc Del Faculty Processing when routed to Borrowing from Doc Del.Creating Custom QueuesCustom Queues allow you to set up holding queues to which you can route transactions in the ILLiad client. These queues are available in each module of ILLiad and, once created, appear in the Request Groups on the Home Page and under the Route menu on the Request Form. They also are used by the EMailRouting and Routing table as destination queues.For example, to create a queue called "Awaiting Reference Staff Processing" so that your reference staff would be able to review certain requests when needed, you would add a custom queue in the CustomQueues table.First, open the Customization Manager and select System | Custom Queues, then the Custom Queues table. The table will be displayed on the right.Choose New Record from the Table Options on the Home Ribbon to create a blank form for entering the queue, or copy a record to use as a template by choosing Copy Record. Type or edit the Queue Name (i.e. Awaiting Reference Staff Processing), the ProcessType (Borrowing, Lending or Doc Del) and the NVTGC field.For non-shared server sites, the NVTGC field would be ILL for Borrowing and Document Delivery and Lending for Lending. For shared server sites, the NVTGC field would be your processing site code.Choose Save to add your Custom Queue to the table. You must exit and restart the ILLiad Client before you will see the addition of any new queues.Manage AddonsTwo ADDONS, OCLC Article Exchange and CCC GetItNow have been added to the ILLiad system. For Article Exchange a rule was setup in Customization Manager under System, Routing, shown as Rule No. 14 below.OCLC Article Exchange RuleCCC GetItNowDistributing AddonsAddons are being distributed automatically as described below. They are located here: \\fileserve\ill\ILL Share Folder\Addon. The only file that needs to be added to the local computer is the LocalSettings.xml. Copy this file from another regular ILLiad user and place it in the same location for the new user. The location is c:\program file (x86)\ILLiad\Addons. If the user does not have the program file (x86) folder then use program file. See for more information.What is Article ExchangeArticle Exchange: Secure, copyright-compliant delivery of documentsThe Article Exchange document-sharing site provides a single, secure location where lending libraries can place requested documents and library users can retrieve articles or book chapters obtained for them via interlibrary loan. This site adds convenience, security and enhanced copyright compliance to article sharing through interlibrary loan. Article Exchange is accessible from within the WorldCat Resource Sharing service and through an ILLiad Addon.Article Exchange:Eliminates security issues often encountered when documents are transmitted through email. Files up to 60 MB – including high resolution documents – can be placed on the site for pick-up by library users.Supports compliance with copyright guidelines with automatic deletion of files. Viewed files are deleted after 5 days or 5 views and unviewed files are deleted after 30 days.Minimizes local technical support because the Web site requires no software download or special arrangements for access through a local firewall.Provides platform-independent access from PCs, MACs or any operating system.Article Exchange supports delivery of documents in the following formats: BMP, GIF,J2K, JIF, JFI, JFIF, JP2,JPE, JPEG, JPF, JPM, JPX, JPG, MDI, MJ2, PEG/JFIF, JPEG 2000, PDF, PNG, PSD, TIF, TIFF, TGA, TPIC and WEBP.How it works:Borrowing libraries use the "Borrowing Notes" field of the request form to indicate their desire to retrieve a document from this site. Lending libraries scan documents and upload them to the site for retrieval by users. They have two ways to inform borrowing libraries of a document's availability:The site generates a unique tinyURL and password for each document. Cut and paste the tinyurl and password in the Lending Notes or Alert field of the request form and update the request status to SHPPED.Use the email function within Article Exchange. When they upload the file, the site generates a unique tinyURL and password for each document. An email button is also present so the lender can click on the email button, insert the borrower's email address and send the link and password directly to the borrower.Once a file has been retrieved, it remains available for 5 days or 5 views. After 5 days, the file will be removed. A file can be picked up a maximum of five times for each URL/password combination. Files not retrieved remain available for 30 days.ILLiad Addon Technical OverviewThis information was taken from The Atlas ILLiad documentation last edited on Aug 13, 2012 Folder StructureThe ILLiad Addon system follows a simple one folder per addon structure.? Each addon should have a separate folder in the "[ILLiadClientFolder]\Addons" directory.? This folder is referred to as the base folder for the addon, and it should have a unique name that is descriptive of the addon it contains.? Inside the base folder for each addon should be at the minimum one configuration file named config.xml and one Lua script file.? The directory structure inside the addon folder can be designed in whatever way makes management and maintenance of the addon easiest.? The only limitation is that the config.xml file be in the addon's base folder.? This same folder structure should be used for addons stored on a shared server, substituting the directory defined by the "AddonDirectory" key for the "Addons" directory.Lua FilesEach addon should have at least one lua file.? Lua files are plain text files with a .lua extension that contain the script text for an addon.? The script text for a single addon can be divided between as many Lua files as desired for easier management and maintenance of the addon.? Regardless of how many Lua files are used for an addon, all of the files must be included in the files list in the addon's config.xml file in order to be automatically included when the addon is loaded.Config.xmlThe config.xml file required for all addons contains the basic descriptive information required to make the addon run properly.? In the config.xml file, a number of values such as Name, author, version, settings, files and associated forms are defined.? A sample configuration file can be found here.? The elements allowed in the configuration file and what they do are as follows:Name - The name of the addon.? This should be unique between addons.Author - The name of the person or organization responsible for the creation and maintenance of the addon.Version - The current version of the addon.?? This is vital for allowing automatic downloads of updated scripts from a network share.? The only time an existing addon will be replaced on a local machine by a script from a server share is if the version number in the configuration file of the server share version is higher than that of the local version.Active - This determines whether or not the addon should be loaded into the system.? Inactive addons may still be downloaded from server shares.Description - A description of the addon's purpose.Forms -A list of Form elements which define the names of the forms in ILLiad that the addon should be loaded on.? Currently, the only form supported is FormRequest.Settings - A list of setting elements that define the name, default value, type, and description of all settings used by the addon.? Descriptions of these elements can be found below.Files - A list of File elements which define the location of each file that should be automatically included when the addon is loaded.? There must be at least one file listed for all addons, and one of the files listed must contain a function named Init(), which will be called when the addon loads.? The entries may be either rooted (full path) or relative to the config.xml file; for files in the same folder as the config.xml file, only the file name is necessary.The following attributes and elements are required for each Setting element in the configuration file:Name (Attribute) - The name that will be used for referencing the setting in the Manage Addons interface and when calling the GetSetting method in the addon's script files.Value (Attribute) - The default value of the setting.Type (Attribute) - The data type for the setting.? Allowed types include string, boolean, and number.Description (Element) - A brief description of the setting's purpose.Local SettingsIn addition to the default settings for an addon, which can be defined in the settings section of the addon's configuration file, users are able to modify the value of each setting in a given addon.? These values are then persisted as Local Settings.? The settings for addons can be changed via the Manage Addons interface in ILLiad.? Once they have been changed, they are saved to a joint Local Settings file (shared by all addons) named LocalSettings.xml, which is independent of the addon's config.xml file and is stored in the "Addons" folder on the client machine.? This allows addons to be easily updated by simply replacing the entire folder without having to worry about losing your local settings.? It also enables users to easily copy the LocalSettings.xml file to other machines in order to easily distribute custom settings.Distributing AddonsThe ILLiad Addon system contains a feature that allows for easy distribution of addons to client machines using a server share.? By simply setting the value of a customization key named "AddonDirectory" (see image, Creating the AddonDirectory Customization Key), users can drop all desired addons into the directory specified in the "AddonDirectory" key, and the addons will be automatically downloaded and used by all client machines capable of accessing the directory.? In addition, each addon is able to define a version, which allows the sharing system to detect updated addons in the shared directory.? Updated scripts are downloaded automatically to replace outdated local versions.? This occurs every time ILLiad is loaded and each time the Refresh Cache button is clicked in the Manage Addons interface, ensuring that all users are always using the latest addon versions.Creating the AddonDirectory Customization KeyNote that if you have a shared server installation, you can specify a different location for each NVTGC site code or use the same. You just need to create the key for each symbol.In addition to the automated distribution of addons via a server share, it is also possible to easily share addons with other institutions or users that cannot access a server share.? Simply distribute the entire addon folder using whatever distribution model (ftp server, download page, etc) is easiest.? Each user can place the addon folder in their local "Addons" folder and the addon will be picked up the next time ILLiad is opened or the Refresh Cache button is clicked in the Manage Addons interface.To create the AddonDirectory key in the ILLiad Customization Manager: 1. Navigate to the Customization table (located under System | General).2. Click the New Record button. 3. Enter the following values to create the key: Cust Key = AddonDirectoryValue = [actual directory – i.e. G:\ILLiad\Addons]Description = Remote directory for AddonsAdmin Cat = SystemAdmin Key = GeneralAdmin Type = StringValue4. Click the Save button to add the key to the Customization table. Default AddonsWith the release of the ILLiad Addon system came several addons that were written by Atlas and provided by default.? They are listed below.? All of these addons are considered by Atlas to be open for update.? In other words, future updates will operate under the assumption that these addons can be safely overwritten with new versions.? What this means for users is that in the event that changes to one of the addons below are necessary, the changes should be made by copying the addon files to a new base folder with a different name, updating the copied version and setting the original version to inactive (via the Active setting in the configuration file).? This will prevent the Atlas update system from deleting your changes in future ILLiad updates.AtlasAmazonSearchAtlasGoogleScholarSearchAtlasGoogleSearchAtlasTrackShippingAtlasWorldCatLocalSearchILLiad on the WebLocation of web pages - C:\Inetpub\wwwroot\illiad\mtg on the Forms serverWeb Pages that were Changed – using text messagingThe Text number (ie. 1234567890@) went in the EMailAddress field. If no Text number was used than the Official University Email address went in the EMailAddress field.When using a Text number, then the Official University Email address went in the Country field. This way the email templates would not have to be changed, but staff would still be able to see the email address in the Country field under Local/Mailing Address in ILLiad.Web Pages that are changed the MostWhen making changes to ILLiad web pages, first copy the file to local computer, test and then upload to the forms server.When changes are made to the ChangeUserInformation.html, NewAuthRegistration.html, or the NewUserRegistration.html the changes need to be made in all three files.Web Pages that need to be correctedChangeUserInformation.html, NewAuthRegistration.html, and NewUserRegistration.htmlSecondary Address Information is not a required field, but if you don’t put a zero in the Secondary Address Line 1 then an error message that says “Secondary Address is a required field. If you don’t have a campus address, please enter 0” and the Secondary Address Line 2 is highlighted in red.“Not Wanted After” DateThe date in the needbydate.txt file (C:\inetpub\wwwroot\illiad\mtg\) on the forms server needs to be changed every semester and the ILLiad Department will notify the ILLiad staff person to make this change. The field is called “Not Wanted After” in the ILLiad Client.Database ManagerDocumentation - from the Atlas Documentation:The ILLiad Database Manager is a tool that allows you to manage your ILLiad database by periodically deleting old data from your ILLiad database, including Transaction and Patron data.Transactions can be deleted according to a time period specified in the Customization Manager.Patrons can be deleted ONLY if they do not have any Transactions associated with them.Patrons can also be blocked to prohibit them from submitting requests.Important: Please be VERY aware that the ILLiad Database Manager is a tool specifically designed to DELETE data from your ILLiad database. This tool is NOT to be used lightly.Example of query to delete patrons using the Database Manager:Miscellaneous InformationDirectory of Butte and Dillon for ILLiadMZJButte – Montana Tech mtech.eduMarcia Lubickmlubick@mtech.edu496-4287Computer Support Spec I----------------------------------------------------------------------------------------Frances Holmesfholmes@mtech.edu496-4222Username: fholmesLibrary Tech II----------------------------------------------------------------------------------------Karen Gerhardtkgerhardt@mtech.eduUsername: kgerhardt----------------------------------------------------------------------------------------Username: librequests----------------------------------------------------------------------------------------MZKDillon – The University of Montana Westernumwestern.eduDenice Rustd_rust@umwestern.edu683-7491Username: d_rustTechnical Services-Libr----------------------------------------------------------------------------------------Bill Dwyerb_dwyer@umwestern.edu683-7164Username: b_dwyerComputer Technician----------------------------------------------------------------------------------------Locked Out UserButte - Montana Tech (MZJ) and Dillon Western (MZK) - locked (disabled) accountsInstructions are for the Forms server using Windows Server 2008. Use Remote Desktop Connections to access the Forms server.Go to Server Manager through Administrative Tools.Choose Users under Local Users and Groups.Right click on the user who is locked out and select properties.Under the General tab uncheck "Account is disabled" and click OK.Log off the Forms Server.Web AlertsWeb Alerts allow you a centralized place to communicate your business hours, special events or other timely and important information to your users.Connection Manager and/or Odyssey ManagerILLiad users can check to see if Connection Manager and/or Odyssey Manager are running. Look at the Alerts window on the main screen of ILLiad.54498241632026This many errors shown in the Connection Manager Alert is your first indication that it is not running. Double click on Connection Manager to see information about Connection Manager.This shows when Connection Manager was started. When it was last run and when the next run is scheduled. If you see something odd, you can put in a helpdesk request to check whether Connection Manager is running.This is the information for Odyssey Manager.No Incoming Requests in Awaiting Lending Request ProcessingThis most likely is an indication that the Connection Manager is not running. Systems can check on the forms server too. Occasionally it can appear to be started but really isn’t. You can stop and start it while others are working in the client.ERROR 1625 – When user is running a ILLiad Client UpgradeError 1625 – “This installation is forbidden by system policy”Run ILLiad Client as Administrator – to do this right click on the ILLiad Client from the Start menu, not a desktop shortcut, and choose Run as Administrator.Items Delivered to WebThese are not included in Request Finished. They are either deleted by customer or in 30 days, at which time they show as Request Finished.Butte and DillonNew users need to be added to “Users” and “Groups” in the Local Users and Groups part of Computer Management. Occasionally a user will become disabled. Go to “Users” in the Local Users and Groups part of Computer Management and check if “Account is disabled” in the properties windows.Map Drives at Butte and Dillon – walking a user through the setup processChoose a drive letterType in a folder name (see below for list of folders)Username will be - 10.8.150.216\username - the username used on Forms server in local usersPassword: this is the local password, same password as logging into illiadMapped DrivesFolder: \\10.8.150.216\illiad for bothFolder: \\10.8.150.216\MZJ for Buttefolder: \\10.8.150.216\MZJemail for Buttefolder: \\10.8.150.216\MZKEmail for Dillonfolder: \\10.8.150.216\pdf for bothfolder: \\10.8.150.216\print for Buttefolder: \\10.8.150.216\Western for DillonMZJ Butte usernames, passwords are kept in ILLiad passwords.txt file in tech$ folder on the fileserve server.fholmeskgerhardtlibrequestsMZK Dillon usernames, passwords are kept in ILLiad passwords.txt file in tech$ folder on the fileserve server.d_dwyerd_rustNew Server for ILLiadWas put into production on 10-12-2011Latest ILLiad Server UpgradeIlliad 8.3 was done on 9/23/2012. Minor client upgrades bring it to 8.3.4.0ODBC – Is needed to connect Microsoft Access with Illiad databaseDouble click on the Data Sources (ODBC) in the Administrative Tools in Control PanelSystem DSNName: illiadLinkDesc: Link to illiad SQL databaseServer: Forms.lib.umt.eduNextHow should SQL Server verify the authenticity of the login ID?With SQL Server NT authentication using a login ID and password entered by userConnect to SQL Server to obtain default setting for the additional configuration optionsLogin ID: illiadlinkPassword: see the ILLiad Passwords.txt file in the tech$ folder on the fileserve serverNextChange the default database to ILLDataNextFinishTest Data SourceSQL Server management Studio on Forms ServerThis can be used to run queries on the ILLiad database, to see the table names or column names within a table.Server type: Database EngineServer name: (local)Authentication: SQL Server AuthenticationLogin: illiadlinkPassword: see the ILLiad Passwords.txt file in the tech$ folder on the fileserve serverClick ConnectContact OCLC ILLiad SupportEmail: support@Phone: 1-800-848-5800Online Documentation: ILLiad Support, training and documentation: access or join the ILLiad listserve: of ILLiad Web Reports of Scanned files and Odyssey ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download