Policy and Procedure for Libraries Considering Library Management Products
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:
- Self-checkout stations
- PC Time Management Systems that require access to patron accounts
- E-book providers who need to authenticate against the PINES patron database
- RFID systems, including security gates that automatically check out items
- Collection Management software that requires data extracted from the PINES system
- Cataloging/Bibliographic database cleanup vendors who need staff client access and/or bibliographic data extracts
- Added content providers who depend on modifications to the Evergreen OPAC
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 PINES Helpdesk for access.
Submit the following information to the PINES HelpDesk 30 days prior to making a purchase decision for evaluation of functionality and support by PINES.
- What need are you trying to fulfill? (PC reservation, Internet Access, print management, etc.)
- What are the requirements for your product to interface with PINES? (SIP2 connection, data extracts, etc.)
Some things to keep in mind when selecting a product:
- If customization is required in order for Library Management products to work, the cost of developing and supporting those customizations will fall to the library purchasing the product and/or the vendor.
- Software upgrades frequently break these external connections. Libraries may want to consider using a product that does not depend on the PINES server.
- During PINES system upgrades or downtimes, Evergreen functionality will be the priority. Maintenance to external connection(s) will be prioritized accordingly after Evergreen is stabilized.
- If it is determined that a third-party software product or service is causing system instability or other problems, the GPLS/PINES staff reserves the right to remove access to that product or service until the issues are resolved by the procuct or service provider.
- In the event of vendor error or damage, the PINES staff will consult and recommend how to clean up any problems. Some types of problems may be solved by PINES staff, but the PINES Program Director may request that the vendor make the repair/corrections or contract with approved vendors (such as Emerald Data Networks for ESI for example) to complete this work.
PINES policy approved September 2002. Updated December 2012.