Thanks Kyle, we are acquiring the DCB product but are having some issues with NCIP agencyIDs. Sorry, I probably should have specified DCB server instead of Millennium. I'm hoping we can use a relay between systems to modify the agencyID as appropriate. I'll definitely keep in mind the need for responses to all NCIP messages originating from the DCB.
- - - - - - - - - - - - - - -
Systems Coordinator and Web Development Librarian
California State University San Marcos
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Kyle Banerjee
Sent: Tuesday, July 22, 2014 9:10 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] NCIP path on a Millennium server
One thing I forgot to mention is that their NCIP is an all or nothing
proposition -- you do not enable individual NCIP services at the III end.
This means that valid responses need to be sent in response to everything
(even if they only perform a null op at the responder end) or the system
will keep trying to resend the request.
On Tue, Jul 22, 2014 at 9:05 AM, Kyle Banerjee <[log in to unmask]>
> AFAIK, Mil doesn't support NCIP. Rather, the library has to have purchased
> the III's DCB product.
> There is a project to allow Evergreen libraries to communicate with DCB
> via NCIP at https://github.com/iNCIPit It works and is used by a few
> This will contain information both connection and the specific NCIP syntax
> you will need .
> On Tue, Jul 22, 2014 at 8:16 AM, Ian Chan <[log in to unmask]> wrote:
>> If you know the typical path and/or port on Millennium to which I would
>> send an NCIP message, would you mind sharing that with me?
>> Thank you in advance for your help.
>> - - - - - - - - - - - - - - -
>> Ian Chan
>> Systems Coordinator and Web Development Librarian
>> California State University San Marcos
>> KEL 1002
>> Skype: ian.t.chan