OPAC Settings and Widgets
OPAC Settings and Widgets
This is an old revision of the document!
Many PINES libraries contract with what are termed “third-party” software vendors (because they are outside of the purview of the PINES/GPLS relationship with the PINES library system) for products that need to connect with the PINES software to work. This is governed by PINES policy (see section below) which requires that libraries expecting full compatibility with PINES software must consult PINES/ GPLS staff in all negotiations with vendors to ensure that their products are compatible. Assurances from other users of the product or from the third-party vendor that the product will work as expected should not be taken at face value.
In certain cases, software development is required to make the third-party's product connect correctly with PINES. In these cases, the cost of developing, supporting, and maintaining the custom interface will fall to the library purchasing the product. When contracting out for SIP-specific technology, it is responsibility of the third-party vendor to build the crosswalks necessary for compatibility with Evergreen, as it is the responsibility of the vendor when providing compatible technology for any ILS. In order to collaborate with the PINES libraries in contracting for 3rd party technology, PINES/GPLS will provide a test environment within which the library and/or the vendor may develop and test the crosswalks necessary in order to insure compatibility with Evergreen.
Once the third-party product has been proven to work with Evergreen and for those products that are currently in use, PINES/GPLS staff is responsible for Evergreen server-side administration. Support for the third-party product continues to be the purchasing library’s responsibility.
Policy & Procedure for Libraries considering third-party products that need an interface with PINES (i.e. Library Management Products)
The PINES staff has been asked to make the PINES database available to outside vendors via library management products. The PINES staff should be consulted during all negotiations with vendors to ensure that their product(s) are compatible with the PINES Database.
Some examples of third-party software and/or services that require access to PINES resources:
In order to collaborate with the PINES libraries in contracting for 3rd party technology, PINES will provide a test environment within which the library and/or the vendor may develop and test the crosswalks necessary in order to insure compatibility with Evergreen. Contact the Help Desk for access.
Submit the following information to the Help Desk at least 30 days prior to making a purchase decision for evaluation of functionality and support by PINES.
Some things to keep in mind when selecting a product:
PINES policy approved September 2002. Updated December 2012.
To add a new SIP device, you will need a couple of pieces of information:
transactions. This will be created by PINES/GPLS staff for you.
Include as much information as you can in a Help Desk ticket and PINES/GPLS staff will assist.