1 / 20

USG Institutional Billing Process In GIL Express

USG Institutional Billing Process In GIL Express. Bob Trotter University System of Georgia Developer Meets Developer March 25-26, 2009. Technical Overview. GIL 35 USG Libraries GA Archives Atlanta History Ctr Technical Colleges. Technical Overview. Georgia Tech. Supported at:

ardith
Télécharger la présentation

USG Institutional Billing Process In GIL Express

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. USG Institutional Billing ProcessIn GIL Express Bob Trotter University System of Georgia Developer Meets Developer March 25-26, 2009

  2. Technical Overview • GIL • 35 USG Libraries • GA Archives • Atlanta History Ctr • Technical Colleges

  3. Technical Overview Georgia Tech • Supported at: • Georgia State • 8 Servers • 20 DBs • UC • UGA • 4 Servers • 16 DBs • Georgia Tech • 1 Server/DB Athens UGA Atlanta Georgia State Medical College Augusta

  4. Technical Overview Voyager Server Browser library.fil Georgia Tech HTMLSSL Apache PHP SQL Oracle TNS tnsnames.ora Georgia State Peachnet xxxdb Medical College University Of Georgia

  5. Technical Overview • Apache/HTML - presentation • SSL Certificates - Security • PHP – business logic • SQL – interface to Oracle • Oracle/SQLNet/TNS – access to other Voyager databases

  6. Technical Overview • TNS Entries • Add a section, with a unique TNS name, for each server in the consortium: UGA1 = (DESCRIPTION = (ADDRESS = (PROTOCOL= TCP) (Host=gil1.usg.edu)(Port= 1521)) (CONNECT_DATA = (SID = VGER))

  7. Technical Overview • Database identification file • A file containing the DB_KEY, database name, database password, and tns name of all the databases in the consortium. • Used for relating a DB_ID from some UB related table to the server and database it belongs to.

  8. Billing / Analysis • USG Institutional Billing Summary

  9. Billing / Analysis • Institutional Billing Process • Annual Reconciliation for lost items • Includes books with a lost status date in range

  10. Billing / Analysis • Uses price in item record or Boker’s Price Index (MySQL DB (updated annually)).

  11. Billing / Analysis • Maintain a MySQL DB of GE contact/billing information • Can either send Informational email, or upload report to send official annual bill to Library whose patron lost your book.

  12. Billing / Analysis

  13. Billing / Analysis

  14. Billing / Analysis • GIL Express Request Analysis • Counts GE items requested and charged by Library’s patrons. • Being updated to click to Titles within each LC class.

  15. Questions? • gil.usg.edu – GIL Project Homepage • giluc.usg.edu – GIL Universal Catalog • gilexpress.usg.edu – GIL Express Information page • rwt@mail.libs.uga.edu - My email

  16. Technical Overview • DB_KEY • A field in the VOYAGER_DATABASES table used to uniquely identify a UB database. • When the UB Database checkbox is checked, the system goes and gets that database’s DBKEY, and puts it in the DBKEY field of that definition.

  17. Background Processes • Blocking local patrons who have become blocked in GE • Perl program using DBD::Oracle • Looks at UB_CHARGE and UB_FINE_FEE tables • Keeps list of blocked patrons for comparison • Unblocks patrons when they have cleared • Uses Pptrnupdt to Expire/Unexpire patron

  18. Background Processes • GE Block process (cont.) • Sends email to list of staff showing who was blocked and unblocked, and the list of currently blocked patrons • Log also placed on GIL Web Reports site

  19. Background Processes • Sync Barcode process • Syncs all Stub barcodes against Home barcode • If patron group changed, checks if eligible and mapped • Log placed on web reports site

  20. Background Processes • Reset Stub patron record Purge Date • Purge dates in Stub come from Home record and vary greatly • Circjob 29 purges stubs only if Purge date is less than current date • Process set Purge date in Stub to current date

More Related