-
Notifications
You must be signed in to change notification settings - Fork 6
ConnectorExpectations
cedelis edited this page Oct 16, 2015
·
1 revision
This page outlines the general expectations for a developer thinking about writing or modifying an ILS connection driver.
An outstanding overview (and story) of what is involved in building a new connector can be found at http://journal.code4lib.org/articles/5608. It details the work that Lehigh University did to write a connector for Symphony.
- Expertise with the ILS to know how to deal with the desired NCIP messages
- Familiar with Java to write back end connector
- Staff with understanding of ILS operations and work-flows in order to load test records, load test patron information
- Server to test read/write operations of the toolkit (so as to not effect a production ILS)
- Willingness to provide basic support for connector developed (ideally answering questions and providing quidance that may arise after release)
- Willingness to participate in XC NCIP toolkit developer community
- Ability to contribute code under MIT license is a MUST
- Attend XC NCIP toolkit developer meetings as needed
Subscribe to XC NCIP toolkit developer's mailing list - http://lists.xcproject.org/mailman/listinfo/ncip-toolkit
- Overview of NCIP Toolkit
- Services - Overview and Detail Notes
- Installation
- Configuration
- FAQs
- Testing and Test Bed
- Developer Information
- ILS Connector Developers Expectations
- Copyright and License Information
- Class Diagram for NCIP Toolkit
- How to add a new NCIP Service
- How to write an ILS Connector for an NCIP Service
- How to setup your development environment to develop a connector
- How to write an NCIP Initiator (client)
- Voyager connector project
- Millennium Connector Project
- Developer Meeting Minutes
- Release Notes