What Is RFID Library System Integration?
RFID library system integration connects RFID-enabled equipment with the software a library already uses to manage materials, patrons and circulation. Depending on the project, the equipment may include self-check kiosks, staff workstations, return systems, security gates or smart library cabinets.
The goal is to make the required hardware and software workflows work together reliably. Integration planning should begin with the existing ILS or LMS, the required functions and the interfaces available in that environment.
Common Integration Methods
Different projects require different communication methods. These options are not interchangeable in every situation, so the right choice should be confirmed against the software and equipment specifications.
SIP2
SIP2 is commonly used to exchange circulation-related messages between self-service equipment and a compatible library management system. Confirm the required transactions and configuration with the software provider.
NCIP
NCIP supports interoperability between library applications and services. Whether it fits a specific RFID workflow depends on the software environment, supported services and integration requirements.
API
APIs allow software systems to exchange data or trigger supported functions. Before development, confirm the available endpoints, authentication method, data format and permissions.
Open SDK
An SDK can provide software components, interfaces or documentation for developers building a connection to compatible hardware. Confirm the available SDK functions and supported development environment for each project.
Which ILS and Library Management Systems Can Be Considered?
Libraries use different integrated library systems (ILS) and library management systems (LMS). Examples include Koha, Evergreen, Ex Libris Alma, SirsiDynix Symphony, Sierra, Polaris, FOLIO and other regional or institution- specific platforms.
This is a list of software platforms that may be relevant when evaluating a project, not a claim that every platform or version has been tested with every HAOHAN product. Compatibility depends on the software version, available interfaces, equipment configuration and intended workflow.
If your library uses a different system, it is still worth discussing the project. The first step is to identify its integration capabilities rather than assuming that a particular brand name guarantees compatibility.
How to Check Compatibility Before Deployment
Before choosing equipment or starting development, use this checklist to clarify the technical scope with the library, software provider and equipment supplier.
- ✓Which ILS or library management system and version does the library use?
- ✓Which workflows are required: borrowing, returns, renewals, user identification or other functions?
- ✓Does the existing software support SIP2, NCIP, an API or another suitable interface?
- ✓Which RFID frequency, tags and equipment models will be used?
- ✓Who will implement the integration: the library software provider, the customer or HAOHAN's technical team?
- ✓Can a test environment or test program be used before deployment?
Who Should Handle the Integration?
There are two common approaches. Customers can request technical integration support from HAOHAN, or their own software provider and development team can work with available interfaces and documentation. The suitable approach depends on the project's technical resources, timeline and required functions.
Where possible, test the key workflows before full deployment. Confirm how errors are handled, which party maintains each interface and what technical support is included in the agreed project scope.
Learn More About HAOHAN Integration
Review the available SIP2, NCIP, Koha, API and Open SDK options, along with the two integration approaches.
View Software Integration Options →Frequently Asked Questions
Can RFID equipment connect to an existing ILS or LMS?
Integration may be possible when the library software, selected equipment and required workflows have compatible interfaces. The exact software version, communication method and project requirements should be evaluated before confirming compatibility.
Does library RFID integration always require SIP2?
No. SIP2 is one common option for circulation and self-service workflows, but the appropriate method depends on the existing software, supported interfaces and required functions. NCIP, APIs or other interfaces may be relevant in some projects.
Can HAOHAN integrate with Koha?
HAOHAN supports Koha integration projects. The connection method and scope should be confirmed according to the customer's Koha environment, selected hardware and required workflows.
Can a software provider develop its own integration?
Customers and system integrators can use available interfaces, API documentation and Open SDK documentation for their own development, subject to the capabilities available for the selected equipment and project.
Should compatibility be tested before purchasing equipment?
Yes. Confirming the software environment, hardware configuration, communication method and required workflows early can reduce implementation risks. Applicable test resources can be discussed with HAOHAN during project evaluation.
Planning a Library RFID Integration Project?
Tell us which library software you use, which equipment you need and what workflows you want to support. HAOHAN can help evaluate the appropriate integration approach.
Discuss Your Requirements