The Koha sip implementation returns a field PI described in one comment as 'Custom protocol extension to report patron internet privileges', in another as an unknown extension and in a third as 'Envisionware extension'. There appears to be no code elsewhere to set this (Sip returns Y for a valid patron N otherwise). Does anyone know of any code using this or is it a software fossil? -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 208 366 1295 (phone) +44 (0) 7759 633626 (mobile) colin.campbell@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com
Hi, On Apr 1, 2010, at 7:35 AM, Colin Campbell wrote:
The Koha sip implementation returns a field PI described in one comment as 'Custom protocol extension to report patron internet privileges', in another as an unknown extension and in a third as 'Envisionware extension'. There appears to be no code elsewhere to set this (Sip returns Y for a valid patron N otherwise). Does anyone know of any code using this or is it a software fossil?
It's a fossil as far as Koha is concerned, but there's a bit of relevant history - Koha's SIP2 support comes via a copy of OpenNCIP, which is meant to be an independent module that provides SIP2 services for an abstract ILS. In principle, the Right Thing to do would be to rip OpenNCIP out of Koha's tree and contribute any base SIP2 code changes to OpenNCIP, leaving just the ILS connector code in Koha's source. The extension for reporting internet privileges is actively used by Evergreen. Regards, Galen -- Galen Charlton VP, Data Services Equinox Software, Inc. / Your Library's Guide to Open Source email: gmc@esilibrary.com direct: +1 352-215-7548 skype: gmcharlt web: http://www.esilibrary.com/
On 01/04/10 12:51, Galen Charlton wrote:
Hi,
On Apr 1, 2010, at 7:35 AM, Colin Campbell wrote:
The Koha sip implementation returns a field PI described in one comment as 'Custom protocol extension to report patron internet privileges', in another as an unknown extension and in a third as 'Envisionware extension'.
It's a fossil as far as Koha is concerned, In the spirit of Jurassic Park I'm taking it on board as an enhancement to implement. A lot of UK public libraries are using SIP2 to allow access to library owned computing resources and need an internet flag especially for child tickets.
In principle, the Right Thing to do would be to rip OpenNCIP out of Koha's tree and contribute any base SIP2 code changes to OpenNCIP, leaving just the ILS connector code in Koha's source.
The problem is its hard to abstract koha as some logic is in the C4 routines, some in the modules and even for something like discharge an item its a long journey to trace where x becomes y, the sip ILS routines attempt to give you the cleaner interface that was a design decision in the OpenILS interfaces, hopefully in 3.4 we can clean things up and make it easier to interface things to core engine. Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 208 366 1295 (phone) +44 (0) 7759 633626 (mobile) colin.campbell@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com
participants (2)
-
Colin Campbell -
Galen Charlton