<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>MnLINK VDX Blog</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/" />
    <link rel="self" type="application/atom+xml" href="http://blogs.minitex.umn.edu/mnlink/atom.xml" />
   <id>tag:blogs.minitex.umn.edu,2008:/mnlink/8</id>
    <link rel="service.post" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8" title="MnLINK VDX Blog" />
    <updated>2007-08-31T20:35:04Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.34</generator>
 
<entry>
    <title>ZPortal Sign In</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2007/08/zportal_sign_in.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=1568" title="ZPortal Sign In" />
    <id>tag:blogs.minitex.umn.edu,2007:/mnlink//8.1568</id>
    
    <published>2007-08-31T20:34:10Z</published>
    <updated>2007-08-31T20:35:04Z</updated>
    
    <summary><![CDATA[This is an important issue that relates to everyone.&nbsp; I get this regularly from people where they say &ldquo;what happened to the requests I placed at my library&rdquo;?&nbsp; Because of the way we utilize the system Sign In authentication, sometimes...]]></summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Login" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p><font size="2" face="Arial" color="black"><span style="font-size: 11pt; color: black; font-family: Arial;">This is an important issue that relates to everyone.&nbsp; I get this regularly from  people where they say &ldquo;what happened to the requests I placed at my library&rdquo;?&nbsp;  Because of the way we utilize the system Sign In authentication, sometimes  people are confused.&nbsp; The Sign In Pickup Location of My Library will  authenticate your library card for the home library system, UNLESS you are using  a computer at an IP authenticated alternate library system.&nbsp; What happened in  this case, the user has a card issued by Minneapolis Public Library.&nbsp; When the  user visits a Hennepin County Library and Signs In to the MnLINK Gateway the  Pickup Location is left as the default My Library.&nbsp; The system knows that the  computer is inside a Hennepin County Library and automatically makes My Library  the Hennepin County Library, not Minneapolis Public.&nbsp; The user places requests.&nbsp;  When the user goes home or at work checks the status of the requests and Signs  In the same way, the system now authenticates the card as Minneapolis Public.&nbsp;  The requests are not viewable with the card authenticating as Minneapolis  Public.&nbsp; If the user changes the Pickup Location to Hennepin County Library the  requests are now viewable again.<o:p></o:p></span></font></p>]]>
        
    </content>
</entry>
<entry>
    <title>Changing Service Type</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2007/05/changing_service_type.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=1291" title="Changing Service Type" />
    <id>tag:blogs.minitex.umn.edu,2007:/mnlink//8.1291</id>
    
    <published>2007-05-30T22:30:48Z</published>
    <updated>2007-05-31T17:28:10Z</updated>
    
    <summary><![CDATA[Loan vs. Copy non returnable.&nbsp; These are the 2 Service Types that define whether a request will end when it is Checked In by the Lender or end when it is Received by the Borrower.&nbsp; The Service Type Copy non...]]></summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Service Type" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>Loan vs. Copy non returnable.&nbsp; These are the 2 Service Types that define whether a request will end when it is Checked In by the Lender or end when it is Received by the Borrower.&nbsp; The Service Type <strong>Copy non returnable</strong> defaults for requests with the Material Type Serial.&nbsp; The Service Type <strong>Loan</strong> will default for the other Material Types.&nbsp; Some Serial requests will be filled with a reel of microfilm and need to be returned.&nbsp; There are some other Material Types, such as Government Publication, that may be filled by a non returnable copy.&nbsp; The Lender can change this in the process of Shipping or the Borrower can change this when the Receive it.</p>
<p>The Lender can change the Service Type after they select the Action Shipped.&nbsp; Midway down the following page is the Service Type drop-down menu.&nbsp; Select the appropriate option and click Submit.&nbsp; You can also change the Service Type when doing Bulk Action Shipped.</p>
<p>The Borrower can change the Service Type after they select the Action Received.&nbsp; Change the Service Type 1 drop-down menu option and click Submit.&nbsp; You can also change the Service Type when doing Bulk Action Received.</p>]]>
        
    </content>
</entry>
<entry>
    <title>SQL error</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2007/03/sql_error.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=1127" title="SQL error" />
    <id>tag:blogs.minitex.umn.edu,2007:/mnlink//8.1127</id>
    
    <published>2007-03-26T20:14:57Z</published>
    <updated>2007-03-26T20:16:28Z</updated>
    
    <summary>There is a known issue which causes an SQL error to occur. If the UPC character string is more than 14 digits this error occurs. Most UPC codes are entered either as 10, 11 or 12 numeric digits. Sometimes there...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>There is a known issue which causes an SQL error to occur.  If the UPC character string is more than 14 digits this error occurs.  Most UPC codes are entered either as 10, 11 or 12 numeric digits.  Sometimes there is additional information which causes the UPC field to run longer than 14 characters, such as the additional information (set) or vol. 1.  The SQL error will go away if you delete all info after the numeric UPC in the UPC field, Authority field and Key field.  The issue has been forwarded to OCLC PICA development to fix.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Request title search problems</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2007/03/request_title_search_problems.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=1106" title="Request title search problems" />
    <id>tag:blogs.minitex.umn.edu,2007:/mnlink//8.1106</id>
    
    <published>2007-03-13T21:02:42Z</published>
    <updated>2007-03-13T21:04:28Z</updated>
    
    <summary>There is an issue with request title searching. This only affects requests placed prior to the upgrade. Requests placed since the upgrade should not be affected by the title searching problem. You may want to try searching by author or...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Request searching" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>There is an issue with request title searching.  This only affects requests placed prior to the upgrade.  Requests placed since the upgrade should not be affected by the title searching problem.</p>

<p>You may want to try searching by author or ISBN instead of title if you can’t find something.  Use the Request Advanced Search option.  Select the Borrower or Lender radio button to help limit your search.  You may need to further limit by checking the Display Not Supplied requests box or selecting the Authorization Status of Complete.  Choose the option of Author or ISBN from the drop-down menu options and enter your search term.  If you choose to search by author you may want to try truncation like with title searching, for example %grisham.  </p>

<p>Don’t hesitate to ask if you have any questions.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Responding to questions</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2007/01/responding_to_questions.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=981" title="Responding to questions" />
    <id>tag:blogs.minitex.umn.edu,2007:/mnlink//8.981</id>
    
    <published>2007-01-04T20:30:30Z</published>
    <updated>2007-01-09T18:28:33Z</updated>
    
    <summary>I&apos;ve heard occasionally that some libraries aren&apos;t responding to questions in a timely manner. When you don&apos;t respond to messages or perform a responsive action you may be putting people at another library in a tough situation. For example, when...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Cancel requests" />
            <category term="Conditional requests" />
            <category term="Note field" />
            <category term="Renewals" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>I've heard occasionally that some libraries aren't responding to questions in a timely manner.  When you don't respond to messages or perform a responsive action you may be putting people at another library in a tough situation.  For example, when your Lender Cancel Pending queue has requests in the file it is very important to respond.  If you do not give a responsive action, the end user can't request another item.  </p>

<p>It's also very important to respond to Borrower Conditional requests.  Make sure to perform the responsive action Conditional Reply-Yes or No.  Do not just send a Message or the other party will not be able to update the request.  If you are contacting your patron for more information you may want to change the Authorization to Acknowledged for the request as a way to let yourself know that something has been done.  You can do this by selecting the Acknowledge button on the results display.  Do something to move the request along, because someone has taken the time to ask you a question and they are now waiting for a response.</p>

<p>Renewals are a similar matter.  As I explain in detail with my Sept. 26 blog posting <a href="http://blogs.minitex.umn.edu/mnlink/2006/09/renewals.html">http://blogs.minitex.umn.edu/mnlink/2006/09/renewals.html</a> if you don't respond to a renewal request it is common practice to assume that the renewal has been granted.</p>

<p>The Messages at the bottom of the Lender and Borrower queues may also require a response.  When one party chooses the Message option it will show up here.  At the very least there will be some communication that will need to be followed up on with these Messages.</p>

<p>If you have any questions about this posting or any others, don't hesitate to contact me.  If you find that you are always struggling to catch up on your workload, please let me know.  I'll try to help in any way I can.</p>]]>
        
    </content>
</entry>
<entry>
    <title>More Conditionals</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2007/01/more_conditionals.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=978" title="More Conditionals" />
    <id>tag:blogs.minitex.umn.edu,2007:/mnlink//8.978</id>
    
    <published>2007-01-02T18:54:09Z</published>
    <updated>2007-01-04T20:26:35Z</updated>
    
    <summary>Conditional requests can be helpful in getting a request filled with the correct material or to check if an alternate version is OK. As a Lender when you choose the Answer Conditional option there are a couple of important things...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Conditional requests" />
            <category term="In Process requests" />
            <category term="Note field" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>Conditional requests can be helpful in getting a request filled with the correct material or to check if an alternate version is OK.  As a Lender when you choose the Answer Conditional option there are a couple of important things to remember to make the process work correctly.  </p>

<p>First, it is important to clearly state what your conditional question is.  There is a list of Reasons in a drop-down menu when you select Answer Conditional, but it is better to add a note.  You can do both.  When you add a note, leave the New Note Type as ToCurrnt Lndr.</p>

<p>Second, your conditional request will expire the next day if you do not change the Answer Date.  I would suggest that you add 14 days to the Answer Date.  2 weeks should be enough time for the end user to be contacted and the Borrower to respond.  If the Conditional expires the request will move on to the next lender in the rota.  The Borrower will see the Answer Date information in the Audit Answer Details and also in the Service tab it will display as Date in Answer.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Bulk Action</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2006/12/bulk_action.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=940" title="Bulk Action" />
    <id>tag:blogs.minitex.umn.edu,2006:/mnlink//8.940</id>
    
    <published>2006-12-11T19:57:35Z</published>
    <updated>2006-12-12T14:49:22Z</updated>
    
    <summary>Bulk Action for requests can be accessed in two different ways. You can Action or Complete more than a hundred items at once. Remember that the more items you Bulk Action, the longer it will take to process. One way...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Bulk Action" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>Bulk Action for requests can be accessed in two different ways.  You can Action or Complete more than a hundred items at once.  Remember that the more items you Bulk Action, the longer it will take to process.  </p>

<p>One way to use Bulk Action is to first select the Requests button, and then select the Bulk Action option at the top of the screen.  You would use this method when you will be scanning or manually entering barcodes into the ILL Numbers box.  If you're scanning numbers it will likely enter a new number on a new line.  If you're typing numbers in, you can just separate each number with a space.  When you have populated the box with the request numbers you would like to Action, choose the appropriate Action from the drop-down menu and click Submit.  </p>

<p>The other method for using Bulk Action is to bring up a Work Queue file, such as Borrower Not Supplied.  On the far right hand side of the screen check the boxes of the items you want to Action, or use the Select all option at the top of the page.  Click Submit when you have all the items you want to Bulk Action.  The request numbers you have checked will populate the ILL Numbers box.  Choose the appropriate Action or Complete.</p>

<p>After Submitting the Action, an appropriate second screen will follow.  You will sometimes see the option to select Service Type.  <strong>DO NOT</strong> select a Service Type from the drop down menu.  If you're going to change the Service Type from Loan to Copy non returnable or vice versa, you should probably do it one at a time.  </p>

<p>When the processing of the requests is finished, your request numbers will be listed as Successful.  Occasionally some of the requests will not process correctly and they will be listed as Failed.  Requests will come back as Failed if the Action was not valid for that specific request or if there was some other problem with the request.  </p>

<p>Make sure to assign the Due Date if you are marking the item Shipped.</p>

<p>If you are using the Action ANSWER NONSUPPLY don't forget to select a reason.  In the past I have had some people ask me about the reason and I suggested that it wasn't that important.  I have come to realize that it is very important to add a reason if possible.  Many libraries forward this information to their users.</p>

<p>When using Bulk Action for Returns (or any time you process Returns), it is very important to make sure that the paperwork matches the item you are Returning.  Also make sure all parts are included.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Pick slips</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2006/12/pick_slips.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=929" title="Pick slips" />
    <id>tag:blogs.minitex.umn.edu,2006:/mnlink//8.929</id>
    
    <published>2006-12-04T19:43:50Z</published>
    <updated>2006-12-05T22:26:45Z</updated>
    
    <summary>I hear from some of you from time to time about the wrong item being sent with a request. You ask, what can we do to eliminate these errors. The Pick slips generally have all of the information that we...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Conditional requests" />
            <category term="In Process requests" />
            <category term="Note field" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>I hear from some of you from time to time about the wrong item being sent with a request.  You ask, what can we do to eliminate these errors.</p>

<p>The Pick slips generally have all of the information that we should need to identify a specific item that is being requested.  The information that is on the Pick slip comes from the bibliographic record chosen by the end user.  This can be found by looking at the Database/# line on the Pick slip.  The Title line should display the title and the subtitle and series information.  The rest of the information on the Pick slips is fairly self explanatory.  Remember to look at the Request notes to see what special instructions have been provided to assist in filling the request with the correct item.  Occasionally with compact discs your catalog will have more than one title match for classical music and other CDs.  Look at the Publisher Info to make sure that you have the correct item.  Look at the Description to make sure the item has the correct number of discs.  The Database/# line will also have a publisher number for the requested item.  All of these together will help you supply the correct item.</p>

<p>Sometimes there just isn't enough information on the Pick slip to identify what is needed.  This would be a good time to use Conditional and ask for more specific information.  As important as it is to use Conditional to ask for more information, it is equally important to respond in a timely manner to Conditional questions as a Borrower.  For more information about using Conditional check out my June 20, 2006 posting. <a href="http://blogs.minitex.umn.edu/mnlink/conditional_requests/">http://blogs.minitex.umn.edu/mnlink/conditional_requests/</a></p>]]>
        
    </content>
</entry>
<entry>
    <title>Not Supplied requests</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2006/12/not_supplied_requests.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=928" title="Not Supplied requests" />
    <id>tag:blogs.minitex.umn.edu,2006:/mnlink//8.928</id>
    
    <published>2006-12-01T16:53:53Z</published>
    <updated>2006-12-01T16:56:43Z</updated>
    
    <summary>Question: I know this has been covered many times before, but I don’t remember the answer to the question. A request comes back as non-supplied. How long is that information accessible on MnLINK so the patron can check their account...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Completed requests" />
            <category term="Remove old requests" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>Question:  I know this has been covered many times before, but I don’t remember the answer to the question. A request comes back as non-supplied. How long is that information accessible on MnLINK so the patron can check their account and see that the item is not available anywhere?</p>

<p>Response:  Once the last possible lender in the rota responds ANSWER NONSUPPLY the request moves into the Borrower’s Not Supplied work queue.  In ZPortal they do not see Not Supplied, the user sees the status Currently unavailable through MnLINK.  30 days after the request moves into the Borrower Not Supplied queue the system will automatically Complete the request.  Your library has the option of Completing the request sooner.  Once the request is marked Complete, either manually by your library or with the 30 day default Complete, the request is no longer viewable by your user in their ZPortal account.</p>

<p>Just an added note, 30 days after any request has been marked Complete the Client Name and Client Barcode are removed from the Borrower Details of the request.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Patron barcode changes</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2006/12/patron_barcode_changes.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=927" title="Patron barcode changes" />
    <id>tag:blogs.minitex.umn.edu,2006:/mnlink//8.927</id>
    
    <published>2006-12-01T16:47:31Z</published>
    <updated>2006-12-01T16:52:00Z</updated>
    
    <summary>Question: We have a patron who had to get a new card for some reason (old one was lost, stolen, whatever). He had placed 10-15 requests on the old card. Because that card is no longer valid in our ILS,...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="In Process requests" />
            <category term="Request searching" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>Question:  We have a patron who had to get a new card for some reason (old one was lost, stolen, whatever). He had placed 10-15 requests on the old card. Because that card is no longer valid in our ILS, it doesn’t validate in MnLINK. His new card validates, but there are no requests attached to it. What happens to his requests that are still in process in MnLINK? Will they ever arrive? Will we be able to connect them to him?</p>

<p>Response:  Good question.  The requests previously placed are still active.  Those requests have the name and barcode used for requesting attached in the Borrower Details.  You can do a Client Barcode search for that user in VDX to locate all of the requests if your user contacts you about their status, but the user can not access the account via ZPortal.  On your circulation system’s end, if you remove the barcode from the user account you will only be able to match the MnLINK request up with the patron by looking at the Borrower Details.  If your library leaves old barcodes attached to the patron circulation record and somehow denotes that it is invalid, you may still be able to search by the barcode on the bottom of the Pick slip depending on your system’s capabilities.</p>

<p>To search in VDX for Client Barcode, you can either do a Simple Search or Advanced Search, and format the search with your 3 letter code, hyphen, patron barcode (e.g. cce-22086000000000).</p>]]>
        
    </content>
</entry>
<entry>
    <title>Removing active requests from patron account</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2006/11/complete.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=923" title="Removing active requests from patron account" />
    <id>tag:blogs.minitex.umn.edu,2006:/mnlink//8.923</id>
    
    <published>2006-11-28T22:29:58Z</published>
    <updated>2006-11-30T21:23:39Z</updated>
    
    <summary>We don&apos;t want to penalize our users for problems on our end. They don&apos;t always understand all of the intricacies that go on behind the scenes to make their material appear at their library. This situation arose the other day....</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Completed requests" />
            <category term="Remove old requests" />
            <category term="Request limits" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>We don't want to penalize our users for problems on our end.  They don't always understand all of the intricacies that go on behind the scenes to make their material appear at their library.  </p>

<p>This situation arose the other day.  A request is Shipped by the Lender to the Borrower.  The material subsequently is lost while in transit to the Borrower.  This request will continue to count against the user's request limit until the request is removed from your patron's account.  </p>

<p>An option would be to remove the patron name from the request.  You can not delete the patron name from a request, but you can replace it.  To do this you would need to have a valid library card.  Most likely you would use a dummy or test card.  You need to choose Local Change Request Details as the Action.  Select the Borrower tab and enter the new card number in the Client Barcode box and click on the Validate button.  This should change the Client Name and in turn remove the item from the previous patron when you click on the Submit button.  </p>

<p>Another option would be for the Borrower to manually Complete the request.  It is usually not a good idea to Complete an active request.  Completing the request will remove the request from the user's account, but it will still be open for the Lender.  You may want to add a Local Note with an explanation about why the request is Complete.  If the Lender sends a Message, the request will reopen for the Borrower even though it has been Completed.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Changing Pickup Location</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2006/11/changing_pickup_location.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=917" title="Changing Pickup Location" />
    <id>tag:blogs.minitex.umn.edu,2006:/mnlink//8.917</id>
    
    <published>2006-11-20T21:37:29Z</published>
    <updated>2006-11-30T21:22:50Z</updated>
    
    <summary>Luckily it doesn&apos;t happen very often, but when it does what a pain it is to deal with. You know what i mean, the user who accidentally chose the wrong Pickup Location. There is no easy way to deal with...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Cancel requests" />
            <category term="Changing request information" />
            <category term="In Process requests" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>Luckily it doesn't happen very often, but when it does what a pain it is to deal with.  You know what i mean, the user who accidentally chose the wrong Pickup Location.  There is no easy way to deal with this one because even though you can change information in the request with the action Local Change Request Details the information on the Lender's Pick Slip does not change.  When the material arrives the only way to know the changed Pickup Location is to select Details and look under the Borrower tab.  Who wants to do that on every request?  So what is the best way to handle these changes?</p>

<p>With the introduction of the Cancel button on ZPortal we can always tell our users to Cancel a request that has the wrong Pickup Location and place another request.  This option works best if the request is not Shipped.  Once the item is already Shipped by the Lender and another request is created that copy is unavailable to fill the new request.</p>

<p>Another option is to wait for the request to arrive and the patron is notified that their request is available.  You can have your patron contact their library and have them ship it to another location for pick-up.</p>

<p>Of course you can always use my old tried and true method of sticking Post-it note reminders around the edge of your computer monitor to remind you of the many important changes that need to be made and things that need to be done.  </p>

<p>The reason I bring this issue up is I am asked this question occasionally by our users and I don't have a real good answer for this one.  I refer these questions back to your library and you're the people who need to know what to do with the information.  If someone has a good way to handle this type of problem let us all know.  Somebody out there must certainly have a better suggestions than mine.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Understanding keyword &amp; phrase searching</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2006/10/keyword_phrase_searching.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=880" title="Understanding keyword &amp; phrase searching" />
    <id>tag:blogs.minitex.umn.edu,2006:/mnlink//8.880</id>
    
    <published>2006-10-24T20:57:36Z</published>
    <updated>2006-10-25T18:18:36Z</updated>
    
    <summary>When you are placing requests on the MnLINK Gateway it is important to understand some of the basics of our searches. If you are using the Basic search it is a Keyword search. It will search for your term(s) anywhere...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Searching the Gateway" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>When you are placing requests on the MnLINK Gateway it is important to understand some of the basics of our searches.  </p>

<p>If you are using the Basic search it is a Keyword search.  It will search for your term(s) anywhere in the bibliographic records of your chosen Search Profile.  Let's say you want to find the title <em>Beauty and the Beast</em>.  It often works best to pick out 2 or 3 main words when using the Basic Search.  Keyword searching tends to work best when you drop the less important words like conjunctions and articles.  In this case it would be best to search for the 2 words Beauty Beast.  If you are sure of a title phrase you can search for that by putting quotation marks around your search terms and the MnLINK Gateway will only look for those words in sequence.  In this situation you would enter the terms like this, "Beauty and the Beast".  Even though I am using them here, upper and lower case characters do not make a difference in searching.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Patron barcodes</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2006/10/patron_barcodes.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=868" title="Patron barcodes" />
    <id>tag:blogs.minitex.umn.edu,2006:/mnlink//8.868</id>
    
    <published>2006-10-16T22:21:58Z</published>
    <updated>2006-10-17T15:28:19Z</updated>
    
    <summary>What do you do when you have the patron barcode, but you need the request number? You can use that barcode with either Simple Search or Advanced Search. When you want to use Simple Search you change the radio button...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Request searching" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>What do you do when you have the patron barcode, but you need the request number?  You can use that barcode with either Simple Search or Advanced Search.  </p>

<p>When you want to use Simple Search you change the radio button under Borrower then you enter your library's 3 letter OCLC code, hyphen, barcode: e.g. hco-21972123456789.  You will get no results if you only enter the barcode.  This Simple Search will only look for active requests.</p>

<p>When you use the Advanced Search you change the ILL no. to Client Barcode and then format the search in the same manner as the Simple Search (3 letter OCLC code, hyphen, barcode).  With Advanced Search you can search for Not Supplied requests by the patron when you check the Display Not Supplied Requests.  You can also search for Complete requests using the Client Barcode by selecting the Authorization Status of Complete.  Remember, Complete requests will only retain the patron barcode for 30 days.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Request numbers</title>
    <link rel="alternate" type="text/html" href="http://blogs.minitex.umn.edu/mnlink/2006/10/request_numbers.html" />
    <link rel="service.edit" type="application/atom+xml" href="https://blogs.minitex.umn.edu/mtx-mt/mt-atom.cgi/weblog/blog_id=8/entry_id=863" title="Request numbers" />
    <id>tag:blogs.minitex.umn.edu,2006:/mnlink//8.863</id>
    
    <published>2006-10-10T20:25:56Z</published>
    <updated>2006-10-11T19:45:16Z</updated>
    
    <summary>Ah ILL request numbers, you can&apos;t live with them and you can&apos;t live without them. One of the most common questions I get is why does the request have 2 ILL numbers? Well, I&apos;ll make this as brief as I...</summary>
    <author>
        <name>Nick</name>
        <uri>httpw://www.mnlink.org/</uri>
    </author>
            <category term="Request searching" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.minitex.umn.edu/mnlink/">
        <![CDATA[<p>Ah ILL request numbers, you can't live with them and you can't live without them.  One of the most common questions I get is why does the request have 2 ILL numbers?  Well, I'll make this as brief as I possibly can.  There's this group called the ILL Protocol Implementers Group (IPIG) that defined the standards that are used by the VDX system.  IPIG decided that each request should have a Requester ID (ILL number), Transaction Group Qualifier (TGQ), Transaction Qualifier (TQ), & Subtransaction Qualifier (STQ).  </p>

<p>There are 2 important numbers here for us, the ILL number and the TGQ.  The ILL number is your party's identifying number when you are the Borrower or Lender.  This is the number you scan for searching and actioning a request.  The TGQ is the other party's ILL number when they are the Borrower or Lender.  TGQ is one of a drop-down Field search options for Advanced Request Search.  I don't believe anyone is using the TQ, and I am not aware of any place where the STQ is currently being utilized in our system.</p>

<p>For more information on the ILL Protocol Implementers Group, you can read all about the standards here <a href="http://www.arl.org/access/naildd/ipig/ipig.shtml">http://www.arl.org/access/naildd/ipig/ipig.shtml</a>.  </p>]]>
        
    </content>
</entry>

</feed> 

