TUG Stats & Reports Spring Meeting

May 27/2009 @ 1:30-4:00 p.m.

Instruction Room, Wilfrid Laurier University Library

Minutes

A. Approval of Minutes from last meeting.

The minutes of January 27th, 2009 were approved.

B. Approval of Agenda

The agenda was approved as circulated.

C. Business Arising and Announcements

Verdi- Ron will follow up with Scott (UG) from the OCUL perspective to see if any inroads have been made with Report Analysis. Gail reported that extracting data from Verdi for 2008-09 was once again cumbersome. There has been no word on anything from OCUL on this account according to Scott. Ron may have to go straight to Scholars Portal to get insights.

D. Cognos Updates

a. The upgrade to Cognos 8 for the TUG libraries has been deferred. The TUG Stats and Reports Group will be asked to develop a more detailed plan to move to a Cognos 8 solution. Much training and support through informal and formal ways will need to be provided. The Team will develop a proactive instead of a reactive approach for the move to Cognos 8. It has been pointed out that training works best when it is used. Cognos User Days is very inexpensive and will be a means for team members to continue to enrich their knowledge of Cognos 8. Week long courses where one is fully immersed in the program are best. Other reporting tools such as BI intelligence, Pentahoe and Analyzer are also to be explored.

b. WLU adoption of C8 status / update- no news on the status of Cognos 8. There is an external review of the IT department at Laurier which may or may not have a bearing on the adoption of C8 on campus (update -Vera)

c. UW and C8 status (update - Gail) – nothing to report.

E. Library Data Mart update at UG (Ron)

a. Progress to date- Staff were asked what kinds of reporting needs were most important to them. Interviews have been completed. A process plan is next in line. Statistics will include TRELLIS, gate counts (minute by minute granularity) and other counts such as reference statistics. Statistics will all feed into the same database. The result will be a system that will not only be cost effective but will extract usage patterns, financial data, archival and reference statistics.

b. Discussion of Jonathan’s prototype. Jonathan’s prototype for Reference Desk data capture is a system that is not expandable. Ron suggested that a TUG group be formed to expand on Jonathan’s and UG’s work. A Laurier representative(s) will also be appointed to to the group. The data warehouse would be a separate one for each of the three libraries but the expertise of all the team members would be invaluable to all three institutions.

Action: 1. Ron will send some samples of initial screens. This is still up in the air with Associate Librarians at UG. The ReOrg has impacted on the ability to get some focus and momentum.

2. Send names of interested parties to Ron

F. TUG reports review-Access services/User services update (Vera)

Access Services/User Services at the TUG libraries reviewed the Impromptu reports. The report has been submitted to TSR.

Action: Vera will send a gentle reminder to other TUG members asking them to review the reports.

G. Training session updates (Gail, Bill)

a. Outcome of recent training session (redesign)

Gail and Bill held two sessions. The first session was a training session for PowerPlay cubes, the second session concentrated on the content of the cubes. The sessions were geared for new trainers at the TUG libraries. UW and WLU trainers attended.

b. Future sessions. A third session will be held on June 10 at 1:30 at UW Davis Centre for those trainers who could not attend the first training session.

H. UW/TUG test and production servers update (Gail)

a. Test server virtualization and testing results. The test server is up and running, no problems reported. Synchronized testing of the server will happen across TUG and is scheduled for mid-June.

b. Production server upgrade plans. There are no plans at the moment to upgrade the production server. Cloning of the production server on to a virtual server may be in the plans for the future if

the virtual test server remains stable.

I. Voyager Analyzer (Gail)

Gail has been following the discussions on Voyager-l. Most have been positive. Voyager Analyzer is restricted to the Voyager database, pre-built packages and reports.

Next Meeting

At UG