JIRA-Tickets for this project: Epic UXPROD-991, Feature UXPROD-557 et.al. The project is in a "rough draft" status. The lookup user service is working, lacking some error handling....in need of a code review. (Michelle will find out who to approach for that) It was suggested early on that the NCIP module be an 'edge' module. I think this edge module may be able to serve as the 'edge' project for both the SIP and NCIP services...so I'm calling the edge module 'edge-circapi'. Nothing set in stone...just a thought. The edge module is working...set up with a key as required. Requests are made with the key. The edge module passes the request through to the NCIP module. The NCIP module is using the XC NCIP Toolkit. Items to note in the project: - The XC NCIP Toolkit does make use of a configuration file. Example (open question Michelle will look into: will this remain a config 'file' or managed through the Folio UX?)
- property file allows you to map each service (e.g. LookupUser) to a class
- lets you point the Toolkit to the RemoteServiceManager class you want to use...a utility class passed through to all requests
- This option in the property file can be used in case the incoming XML does not include a nameSpace:
- NCIPServiceValidatorConfiguration.AddDefaultNamespaceURI=true
- Mechanics of the Toolkit:
- The XML in the request indicates the service being called. The toolkit transforms the XML into a RequestDataObject and instantiates the class that will process the request (both based on the service type indicated in the XML).
- The toolkit can than transform the ResponseDataObject (populated with data) back into XML to send in the response.
- Provided a demo
- Michelle has some functional questions (she'll reach out to Cate about). For example...the lookup user expects a response indicating whether or not a patron can borrow. Is the only indicator of this (right now) the active indicator? Will there be rules to determine if a patron can borrow? (for example fines over $150 = they cannot borrow)
|