This document discusses the statistics program for electronic government publications (e-govpubs) at San Jose State University. It provides details on: - How the in-house program works by collecting data from a text file and government publications database to generate statistics. - The architecture of the program which uses ColdFusion and SQL Server and retrieves data through a front-end interface and stores it in a back-end database. - The process for modifying bibliographic records by identifying the record number, adding tracking information to the URL, and using scripts to batch update a large number of records. It estimates the initial time required to update 37,000 records was at least 2 weeks.

1. Electronic Government Publications Handout: How our statistics program works Susan Kendall San Jose State University October 18, 2011

2. How we derived our e-govpub statistics A quick review on SJSU’s statistics program for e-govpubs We developed an in-house program We currently do not use Google Analytics for this project We do use Google Analytics for web site analysis

4. SuDoc #

5. class

7. suDoc#

8. class

9. titleMS SQL DB Server insert into Redirect to vendor website * Extract data using cfhttp to initiate a one-way request from information from a remote server (the library catalog) http://mill1.sjlibrary.org/search/.bibNum/.bibNum/1,1,1,B/marc~bibNum Lyna Nguyen

11. bibNum

12. suDoc #

13. class

15. suDoc#

16. class

17. titleMS SQL DB Server display to web browser query data connect to db Lyna Nguyen

18. Steps to Modifying the Bibliographic Record Identify the Bibliographic Record Number TITLE: Earthquakes in Arkansas and vicinity 1699-2010 B4153005 – Bibliographic Record Number

19. Catalog view

21. How to Change the Database(using character based version)

22. Next step: Use a script/macro to copy the bibliographic record number for each record Add the prefix to the URL. Use a “do loop” in the script to perform batch changes Majority of records can be batch processed with the script/macro

23. Govt URL Batch Process (simplified) Start Look for review file to change Log on INNOPAC Found? yes no Go to first record Send an error message Look for uhttp://purl no Found? Go to next page yes Grab the 856 Line# Found? yes no Grab the bib# Beginning of page? no Change the URL yes More lines to change? yes no Make changes permanent Last record ? no Go to next record yes Log off End EXIT Shirley H. Hwang 5/9/05

24. Time required for initial run 37,000 bibliographic records / 50,000 – 856 fields Minimum of 2 weeks to run initial database change Many records had non standard URLs attached

25. On-going monthly maintenance Search for records to be changed after downloading monthly Marcive records Use script to do an automatic search Scan the records to check URLs Run a script/macro to batch change the records

26. On-going monthly maintenance and time consideration Total staff time: approximately 30 to 60 minutes Total Machine time: approximately 2 to 4 hours