Questions? Just contact us!

Login

Username

Password

Remember Login

Forgot your password?

Not a member? Click here to register

SPOT Meeting Minutes 2009-11-16

SPOT Agenda for OCLC Call - November 16, 2009

Present:
(OCLC) Ed, Jennifer, Ron, Sam, Christa
(Summit) Kyle, Nancy, Al, Bill, Rick, Heidi (others from SPOT were unable to be added to the conference; had wrong access code listed in the agenda)
 
  1. How do Article/Copy requests get into NRE? Examples: Rick & Heidi

    Determined by WCL configuration on requesting/borrowing side.  Sites should be able to alter behavior in Self Configuration module.  For example, can set WCL to handle annuals as monographs.  If it is set up to handle them as periodicals and the Summit Request button is displayed (as is the case at L&C), the request will go to NRE as a "Copy non returnable."

    L&C will test this and report back so we can get instructions out to each site.

  2. Unship - Ron & Ralph do we know the status of the Circulation Gateway And Its Role When This is Used

    There is no relationship between the Unship action and the Circulation Gateway.  Nothing is "undone" on the ILS side. 
    Ed said that OCLC was working on creating some relationship for other consortia, but we agreed that it's best to leave it as is for now (As Nancy pointed out, a fix would only apply to some sites, depending on their configuration.  Also, different reasons for updating to Unship may require different actions on the ILS side.)

  3. Staff interface in NRE: how to place requests on behalf of patrons same as in Illiad

    When we try to request something on behalf of patrons now, the requests have weird associations with different staff logins.
    Ed: Ralph writing up a solution for this.  We'll have to talk to him for an update. 



  4. Status of ezproxy - looks like there will will be a hosted option in January 2010.

    Jennifer said someone is working on details and will get additional info, including a timeline, to us this week.
  5. Batch printing of paging slips - do Ed and team realize why and importance of batches. Do they need a diagram/explanation.

    Kyle explained need for batch printing.  Since info for paging slip comes from Circ Gateway, shouldn't we be able to batch print directly from NRE?
    Nancy: Sites rely on the ability to sort by location and call number 

    Ed: If it's in the request, it can be in the slips.  Need rules for sorting from us so they can see if it can be done. 

  6. Help modules going to be installed on December 13th?

    This has to do with the new patron login interface coming at the same time.  They won't see it until the change is made.
    Additional staff help will arrive in February.

  7. Telnet menus, what is the current status?

    Ron: OCLC is still working on solving issues with check-in on the lending side.  Testing this with BCL group, not Summit sites.

  8. Patron UI: OCLC: to send requirements and spec for their February install this week

    Jennifer confirmed that they're sending to John, Kyle, Anya this week

  9. Statistics: The Alliance is interested in getting reports that allow the members to know what loan titles are being requested, how many times, and by whom (other member libraries)
Basic reports are now available via www.stats.oclc.org  Should be a navigator tab at the top with all we need.  Does go to title level.  OCLC is still working on the "reasons for no" sections.  Contact Christa Starck with questions or concerns.
 

           Our current stats since out letter:

            • 13% decline in total requests is about the same
            • 80% fill rate is now 82% fill rate
            • 28% decline is now 26%

  10. Documentation:

This will be discussed on the next SPOT call.


    a) list of all error or service problem messages, what they mean, and what someone is supposed to do when they see it (how to interpret it, action to take, or to create a problem report)
   
    b) documentation on "discovery" or requesting side - when patrons, or staff helping them, can't understand message or response when trying to request. This one is particularly bad since the log message is "Item was not located" but the item is right there in the display! In common language: of course there's an item, and we know where it is.
    c) Brief written explanation of how multiple-OCLC no. problem was defined, where OCLC numbers were identified in records, and how the problem was resolved.