TUG Stats and Reports Group
Meeting
McLaughlin Library, Rm 103
November 15, 2010
1:30-4:00 p.m.

1. Approval of the Minutes of Wednesday March 10, 2010.
   -approved
   
   
2. Approval  of the Agenda
   -agenda was approved; items 4. & 7 moved to the end of the agenda.
   
   
3. Business Arising
   SFX development. It is hoped that at Scholars Portal Day, representatives from TUG Stats and Reports Group attendees will meet with Scholars Portal members to explore tangible solutions to continue SFX development. UW library systems audit continues. Gail was asked to supply a list of COGNOS users. Many users that left the employ of the university libraries have now been disabled in COGNOS.
   
   
4. New server implementation
   The new server has arrived. There are some issues with mounting into blade configuration. Carl Nagel and Chris Gray will move some of the servers into different slots. The operating system will be moved first then the COGNOS software. One of the issues is that COGNOS 7 does not run on Windows 2008 server. It runs off 2003 server. It is expected that the new server implementation date will be in the New Year.
   
   
5. UG Data mart update (UG)
   Cubes are being moved into the COGNOS 8 environment. On the issue of extracting TUG data for subsets, Ron will approach TUG Exec to see if approval is needed, however it was felt that there would be no patron security compromise.
   
   
6. Roles and terms
   In the long term, Ron is hoping to step down as Chair. Vera and Richard felt that they were not qualified or needed more time on the Committee to step up to the role of being Chair. WLU will be seeking new representation on this Committee.
   
   
7. Primo stats discussion
   TUG Stats & Reports Group met to discuss the Primo team's request for input into Primo stats reports. Discussions were based on Alison Hitchens' email outlining the Primo team's needs. With the changes in Primo 3's interface/display and processing of searches and requests, the ability of Google Analytics to analyze these data would be compromised. It would be difficult to compare the two sets of data. Also, there would probably not be an easy way to reconfigure or manipulate the Google Analytic data to suit.
   
   The BIRT-based reports are likely a better option since it might allow one to look at data and compare. That would be true if (and only if) the database target fields are the same. Using BIRT gives two possible options; use the BIRT "canned" reports or learn BIRT and create reports. Unfortunately, no one in group knows BIRT, so the effort and time to get up to speed with BIRT is an unknown.
   
   During our meeting, Gail Sperling showed us the cube she developed some time ago which included data collected up to mid-September. It contains a lot of pre-existing dimensions and variables and Voyager that may make it almost a turn-key process for the Primo team. The only difficulty is that data has not been available to COGNOS since mid-September. We don't know what happened at that time to limit COGNOS access to the data or database, but Gail and Charles Woods will engage the UW ITS folk to pursue re-establishing the COGNOS link to the data.
   
   If re-connecting to the data is fixed, the COGNOS reporting option would be the most efficient use of everyone's time since a significant amount of the work has already been done. Given the report support currently available, TSR recommends that the Primo team consider this option (if the links can be re-established). The COGNOS cube content we viewed looked reasonably comprehensive. We didn't think there would be much more needed. However, that is an issue the Primo group would have to gauge. We would certainly entertain discussions to develop and bridge any data gaps. If the COGNOS route is viable, it will then be a matter of then developing the reports to answer the systematic questions based on committee's goals and/or operational needs. From the group's perspective, accessing and utilizing these reports will require some basic COGNOS training. We believe, however, this is the most expedient and long-term effective solution to reporting and analysis needs. Operationally, it is the option for which we could provide the best support. Ron will send this memo to the TUG Primo Team.
   
   
8. LibQuest Demo
   Gail logged into the live database. LibQuest is a database now in full use at UW. LibQuest shows reference interactions over time. Staff at public service desks record: mode of communication (in-person, phone, chat, level of interaction (1, 2, 3) and the facet (RefWorks, Statistics and Data, etc.). Powerplay cubes have now been developed to create reports.
   
   
9. Budget (capital needs)
   -will be revisiting whether TUG libraries will be moving forward with COGNOS 8. There has been no news from COGNOS support on any new developments with 7 series.
   
   
10. Training
    -Continue to take advantage of opportunities to attend any training, user group days.
    
    
11. Next meeting
    -WLU in January