NCIP: Alma and ILLiad Recommendation

Owned by Chris Lee (Unlicensed)
Last updated: Dec 01, 2017
2 min read

The NCIP addon in ILLiad allows us to easily copy requests to Alma for checkout. While this system provides great workflow improvements it does have some drawbacks. Currently the ILLiad due date in Alma is overwritten and replaced by CSU+ due date when a patron checks out the item. This is because resource sharing due dates are currently configured to be set at checkout. To change this would require every campus to individually reconfigure their Resource Sharing settings in exactly the same way. This change would also mean all Resource Sharing due dates would be decided by the lending institution before the item is shipped, which could substantially shorten CSU+ loan periods.

With the upcoming release of Tipasa, and the phasing out of ILLiad, the NCIP might not be available for more than a few years. Because of the complexity of a consortia wide change, and the potential loss of the NCIP, the Resource Sharing Functional Committee recommends each campus choose how they want to use the NCIP. Some of the NCIP configuration options include:

  1. Manually changing the due date after checkout. Collect ILLiad sign out slips from circulation and look up the patron in Alma. Manually change the due date Alma assigned to the due date set by the lending library. Patrons will get to keep the item for as long as the Lending library allows, but may be confused if they check the due date in Alma before the date is changed. You can also train student workers to change the due date when the patron checks out the book.
  2. Create an ILLiad “library” with a shortened due date. Another option is to make an ILLiad Library that sets a due date that is likely to fall within the time frame allowed by the lending library. This is the solution recommended by Ex Libris trainers. One CSU library has implemented this system and all ILLiad items automatically get a 3 week loan period starting at the point of checkout. While not a perfect solution it does allow the library to take advantage of the NCIP without increasing staff or student workflow.
  3. Don’t use the NCIP. A very simple solution is to simply not use the NCIP and continue with the workflow currently used by your library.

Hopefully one of these options concerning the NCIP works for you. If you think of another solution that is not listed please sharing it with the Resource Sharing Functional Committee so we can add it to the list.