John,
Thanks for the pointers. I've got a fistful of links for NCIP, but I don't
think I had that one for the Implementation Group.
One problem with the existing application profiles, which I mentioned to
Ted Koppel in Nashville, is that they require support for Implementation
Profile 1, the current XML-based protocol, with no clear text indicating
how they will cope with any implementation profiles that may be created in
the future.
I'm glad to hear that I only need to create code for the services required
by the particular application profile(s) that I plan on supporting. I do
find it a bit odd that the fairly restrictive "Self Service Unmediated
Online Circulation" profile requires more services (14) than the general
inter-agency "Circ/ILL" profile that you tell me requires 8 services.
Once all the non-technical issues surrounding this project are all lined
up, I will definitely be asking lots of questions.
- David
John Bodfish wrote:
David:
When you begin planning your NCIP work you should review the NCIP
Implementation Group's web site (http://ncip.envisionware.com),
especially the Road Map to NCIP (in the "Documents" section). It
explains that you don't implement NCIP as such, in the sense of
implementing all 45+ services, let alone all the optional elements
within them.
The expectation was, and still is, that implementations conform to
"Application Profiles" such as the Circ/ILL Application Profile (see
http://vdxipedia.fdusa.com/index.php/Main_Page#NCIP_Interop_Information
for that profile and supporting documentation). That profile uses only 8
of the 45 services, and does not use many of the optional elements
within those services' messages. There are other Application Profiles
that cover other areas of NCIP usage listed on the NCIP IG's site.
If you have any questions I'm happy to answer them.
John Bodfish
Senior Technical Designer/Developer
OCLC PICA Inc.
-----Original Message-----
From: Code for Libraries [mailto:[EMAIL PROTECTED] On Behalf Of
David J. Fiander
Sent: Monday, January 08, 2007 7:45 AM
To: [email protected]
Subject: Re: [CODE4LIB] NCIP API?
David Kane wrote:
I did get a reply on the list from Joshua Ferraro of LibLime, who said
that they began development on an open source SIP2 API, which was to
be
extended to NCIP functionality. This extension to NCIP did not
happen.
This SIP2 api is now in use in the EvergreenILS and soon to be used in
the Koha ILS.
David,
I'm the person that wrote the Evergreen SIP2 code, and will probably be
the
person writing NCIP code in the future. NCIP is a very large, very
complicated standard, so even once work starts on NCIP, it's going to
take
a while to complete.
- David
--
David J. Fiander
Digital Services Librarian
--
David J. Fiander
Digital Services Librarian
