1 / 69

Circulation 12.3 - 14.2 Upgrade

Circulation 12.3 - 14.2 Upgrade. Session outline. General features Table driven check routines Circulation librarian override levels User Ids management Intra-library loan and cross library cash management Proxy functionality Cash management Other changes. General Features

stussey
Download Presentation

Circulation 12.3 - 14.2 Upgrade

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Circulation 12.3 - 14.2 Upgrade

  2. Session outline General features Table driven check routines Circulation librarian override levels User Ids management Intra-library loan and cross library cash management Proxy functionality Cash management Other changes

  3. General Features 12.3 – 14.2 Upgrade

  4. UNICODE ALEPH • Data (bibliographic + administrative) is stored in UTF-8 • GUI client is UNICODE compatible • No need for character conversion for input and display • ALPHA loses most of its meaning

  5. All Modules - New Features • New Window design

  6. All Modules - New Features • Transaction log

  7. Navigation Window • The OPAC navigation window is now multi BIB. A user can add a new BIB to the window by clicking the “Add to Nav Map” button in the Full window. • Two extra buttons were added to the Nav Map window: • Remove BIB • Delete BIB

  8. Navigation Window • The new architecture of the navigation window provides tools for catalog deduplication. • You can now “drag & drop” items, orders or subscriptions from one ADM record to another. • For example, you might do this when you need to move orders from duplicate BIB records.

  9. Navigation Window

  10. Navigation Window • Associated records are also moved. For example, when moving an order, items linked to this order are moved as well. • Loans, hold requests and photocopy requests are moved together with the items.

  11. Navigation Window • Delete bib allows you to remove bibliographic records after deduplication. • This function passes all cataloging checks and password controls.

  12. Retrieval - New Features • Get function has disappeared • Direct index (z11) still exists • Possible ways of retrieval are: Find by direct and Browse by direct

  13. When in doubt.. . • Right click!

  14. Circulation

  15. General trend of circulation development : • Gain flexibility by splitting hardcoded routines into small functional blocks • Modular, table-driven structure • Enriched functionality • Complicated configuration

  16. Table-driven check routines

  17. tab_block_circ • This table defines the allowed maximum for three parameters: • No. of overdue loans • No. of recalled overdue loans • Amount of debt to library

  18. HOLD AND PHOTOCOPY REQUEST MANAGEMENT POLICY

  19. Hold Request processing Recall of Hold requests placed by users from the web -- Type of recall is now defaulted in www_server_defaults Holds on Items with “Item Processing Status” -- These are treated as “unavailable” so no hold request slip is printed.

  20. tab_hold_request This table defines checks for hold requests. The checks can influence: - display (or not) of the Request link on the list of items - display of information regarding the group of items and the patron's place in the request queue - display of meaningful messages concerning the reason why a request is refused.

  21. tab_hold_request There are 5 separate instances defined for when a check is made: - PRE is used when the list of items is displayed in the WWW OPAC - PRE_GUI is used when the list of items is displayed in the GUI OPAC - INFO is used when displaying the hold request fill-in form - POST is used when the user sends the request to the server - CIRC is used in the Circulation client

  22. tab_hold_request – check routines examples

  23. tab_hold_request Multiple possibilities, BUT……… When setting PRE checks, take into account the system resourcesrequired for checks that are made when the items list displays. If the checks require comparing item records and existingrequests, and there are many item records, this can create an undesirableload on the server. If a check is listed for PRE, it need not be listed forINFO or POST, since the INFO/POST scenario will not happen.

  24. tab_photo_request This table sets the checks that will be performed when a photocopy requestis placed on an item.

  25. Modular structure makes the the system much more flexible, but….. Be careful with configuration

  26. Overriding Loan and Renewal Restrictions

  27. Overriding Loan and Renew Restrictions Circ override level defines the staff user’s privilege to override a circulation transaction that has been trapped by a circulation check procedure.

  28. Overriding Loan and Renew Restrictions How does it work? Tab_check_circ defines sets the checks to be performed when an item is loaned or renewed.

  29. Overriding Loan and Renew Restrictions How does it work? The text of messages associated with the checks is defined in /alephe/error_eng/check_circ.

  30. Overriding Loan and Renew Restrictions How does it work? check_circ_override - defines the minimum password level that is required in order to be able to override a circulation transaction

  31. Overriding Loan and Renew Restrictions How does it work? A minimum password level is defined for each check procedure. The check procedure is identified by using the number of the number of the error message that displays when the check procedure traps the transaction.

  32. User IDs Management

  33. tab_user_id & Z30 • The management of the various patron ID fields is now handled by tab_user_id.lng and Z308.

  34. tab_user_id & Z308 GUI interface for Ids updated/creation

  35. tab_user_id & Z308 • Column 9: Update in WWW • This column lists the type of verification that can be • updated in the Web OPAC. NOTE: It is possible to update only ONE verification at any given time.

  36. Intra-library loan and Cross library Cash Management

  37. tab_attr_sub_library • This table was formerly tab_ip_sub_library. • This table defines, for a particular workstation, or • group of workstations, which sub-libraries come • under their jurisdiction and what activities can be • performed on items belonging to that sub-library.

  38. tab_attr_sub_library • There are five types of attributes you can assign a • sub-library in a workstation: • Type 1 • If the item’s sub-library is one of the sub-libraries • listed as type 1, the item can be loaned out • and returned at this workstation.

  39. tab_attr_sub_library • Type 2 • If the item’s sub-library matches one of the sub- • libraries listed as type 2, the item can be returned, • but not loaned, at this workstation.

  40. tab_attr_sub_library • Type 3 • Home Sub-library: • If the item's sub-library is not listed in the type 3 • group, when a return is performed, the return is • considered a "transfer” return. • A message is displayed, and a transfer slip is • printed. The item will appear, as “In Transit” • until it is returned at its home sub-library.

  41. tab_attr_sub_library • Type 3 • There is special treatment for the z37 hold request if the pickup sub-library is type 3 (HOME or BOX in tab_sub_library). • When an item is returned, and the item sub-library is not the same as the return sub-library, and there is a request for type 3 pickup library, the z37 request will NOT be handled. • The system will require that the item be returned to the item sub-library. In other words, the return action will create an "in transfer" return, and the z37 request will be handled by the item's sub-library.

  42. tab_attr_sub_library • Type 4 • This type is used for the Reading Room client, and • allows Reading Room transactions. • You cannot list more than one sub-library of type 4. • When there is a Reading Room sub-library • defined for IP address it means that all the loan • transactions preformed at this IP address will be • treated as Reading Room loans (will create z310)

  43. tab_attr_sub_library • The item’s sub-library will change to the Reading • Room, and remain so as long as the item is on loan. • Therefore, it is recommended that the Reading • Room sub-library have its own workstation that • is used only for this purpose otherwise the whole • system will be affected.

  44. tab_attr_sub_library • Type 5 • This type is used for cash transactions that are not • item specific. • When a transaction of this type (e.g. photocopy • request, ILL processing) occurs at the IP address, • the sub-library registered here will be written in • the cash record. You cannot list more than one • sub-library of type 5.

  45. tab_attr_sub_library • Type 6 • Filtering of cash transactions. When a sub-library is registered as type 6, in the Cash tab of the User Information window it is only possible to see the transactions belonging to that sub-library. • The Sum to Pay will also be updated according to that sub-library. • When there are cash transactions that do not belong to a specific sub-library, they will be automatically registered with GBL in Z31-SUB-LIBRARY. If you wish to see these transactions, • enter GBL as type 6.

  46. tab_attr_sub_library

  47. Proxy Functionality 14.2

  48. Proxy Functionality • Proxy functionality is active now: • The library may allow a user to borrow items for someone else who acts as his sponsor. • It is also possible to define which circulation activities will be attributed to the sponsor, and which will be attributed to the User ID. 14.2

  49. Proxy Functionality

More Related