Talis Forums Archive

A place to discuss all your library issues
It is currently Sat Dec 16, 2017 7:33 pm

All times are UTC [ DST ]




Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 5 posts ] 
Author Message
 Post subject: Issue stats off 3m 6210s
PostPosted: Mon Sep 19, 2005 10:24 am 

Joined: Thu Apr 15, 2004 10:09 pm
Posts: 6
Location: Trafford Libraries
Is there a reliable way of getting statistics for self issues on the 3M 6210’s? We assumed the statistics that you can print directly off the machines would be the most accurate, but we’ve found these unreliable.

Getting self issue stats off Talis via Business Objects doesn’t seem straightforward either. At the moment we run a report for each site with ‘loan activity breakdown’ object set to self issue. But this reports self issues at sites with no self issue machines. So the report is run again with the operator object and when the operator stats are subtracted from the non operator stats this produces 0 for our non self issue sites.

But are the numbers produced this way ‘true’ self issues for our self issue sites? and these numbers don’t look anything like the statistics we pull off the machines for the same periods.

What do other people do?


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Wed Sep 21, 2005 5:21 pm 

Joined: Tue Nov 02, 2004 5:09 pm
Posts: 25
Location: Talis
Dear Brian,

what sort of statistics are you interested in? We have had similar requests from other libraries. Can you tell us what are the stats that would be most useful to your library?

Regards,

Zak

--
Zak Koufakis
Talis Information Ltd
zak.koufakis@talis.com
phone: 0870 400 5078


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Thu Sep 22, 2005 4:08 pm 

Joined: Thu Apr 15, 2004 10:09 pm
Posts: 6
Location: Trafford Libraries
Hi Zak

Issues, renewals and discharges are all we're after. The problem is getting figures we feel are reliable and reflect the machines use.

Thanks
Brian


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Thu Sep 22, 2005 4:52 pm 

Joined: Tue Nov 02, 2004 5:09 pm
Posts: 25
Location: Talis
Brian,

we are providing these but they are not well thought out because nobody has been interested in these until very recently - they are embedded in the server's log files and are difficult to find. In other words, we have never had any requirements for them. There are two ways to do it:

1) Create a new database table that gets updated by the server. Then you will need a Talis LMS menu option to access it - unless sql is adequate or you are using business objects.

2) The server creates terminal usage statistics in separate files. In what time periods? Daily, weekly, monthly? What format? What about success rates? Reasons for operation(checkin/checkout/renew) failure? Thinking about the possibilities will increase your appetite - I am sure.

Please, think carefully and submit a PER.

Regards,

Zak


Top
 Profile  
Reply with quote  
PostPosted: Fri Sep 23, 2005 11:26 am 

Joined: Wed Aug 04, 2004 3:49 pm
Posts: 449
Location: Talis
The loan information is in the prod_talis database and while we don't store the self issue terminal information there is a way around this. For information about failures and the actual messages sent as Zak said that would require another approach.

It would be interesting for me if you let me know more details of the type of information you would like to see in terms of self issue and their use e.g. statutory/corporate statistics, level of use or in response to customer issues.

The best way of identifying a row in the LOAN table that would identify a terminal (or individual for that matter) that created the row is the OPERATOR_ID in the the LOAN table. The configuration file for a SIP2 server process allows you to define which OPERATOR_ID is used when a loan transaction is inserted into the LOAN table. When we ship the configuration files the default OPERATOR_ID is "Self Issue" as defined by TAL_LOAN_OPERATOR variable in the cfg file. If a configuration file is set up for each machine then this default value can be changed to whatever they want in order to identify the machine (subject to a limit on length of 10 characters). The operators then need to be entered into the list of operators in Alto. It would then be possible to report in BusinessObjects using the loan operator as a condition. If the operators are not entered into Alto then BusinessObjects will not be able to report on the loan rows with that operator as it does an inner join between the OPERATOR and LOAN table in any report using the "Loan operator" object.

It would also be possible to set up separate sites to assign to each machine and report by that although this approach requires more on-line configuration to set up the sites etc.

The "Loan activity breakdown" object just looks at the ACTION_ID (for self issue this is CLIS) and was designed as a high level approach to identifying transaction types.

I have checked your system and the SIP2 processes are all set up to use the default "Self Issue" operator. I would advise you to modify the configuration files with new operators to identify the machines. If more than one machine uses a configuration file then new files can be created so the operator can be unique for each machine. These operators ahould then be added into the list of Operators in Alto. It is likely that you don't want anyone to use this operators in Alto so ensure they have a password. You should be able to report by machine in BusinessObjects. This change will only allow you to report on loans created after the change and not on loans already created.

I also noted that there is no operator called "Self Issue" in the Alto operator table so you would have had a problem in BusinessObjects anyway. If you add this operator they will be able to report on self issue transactions that have already happened although you will not be able to report at the machine level you will be able to report on self issue transactions on a site by site basis.

Thanks

_________________
Brian Crampton
Consultant, Talis


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 5 posts ] 

All times are UTC [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group