[UXPROD-991] NCIP: Protocol for ILL, Resource Sharing and Self Checkout Created: 09/Jul/18 Updated: 17/Sep/20 Resolved: 06/Jan/20 |
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q4 2019 |
| Type: | Epic | Priority: | P3 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Michelle Suranofsky |
| Resolution: | Done | Votes: | 0 |
| Labels: | external_sys_int, library_dependent, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||
| Epic Name: | NCIP: Protocol for ILL, Resource Sharing and Self Checkout | ||||||||||||||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||
| Front End Estimator: | Jakub Skoczen | ||||||||||||||||||||||||||||
| Back End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||
| Back End Estimator: | Jakub Skoczen | ||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | Assuming front-end only for settings. | ||||||||||||||||||||||||||||
| Development Team: | Lehigh | ||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R1 | ||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R1 | ||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||||||||||||||
| Start date (migrated): | |||||||||||||||||||||||||||||
| End date: | |||||||||||||||||||||||||||||
| Description |
|
NCIP is one protocol used to make service requests and to fulfill the same requests. See: http://www.ncip.info/introduction-to-ncip.html. This protocol covers several ILL and resource sharing scenarios as well as self-check stations. Notes: This is probably a must have for V1. ARL: This must be in place from the get go. OLE partners rely on it for self-check, D2D, etc. Also, it is vital that FOLIO demonstrate that it will be standards complaint from the outset. THis really depends on the 1st libraries to adopt FOLIO. THis is very important, but could be delayed if the 1st library does not need it. FMID: ID492, ID493 |
| Comments |
| Comment by Michelle Suranofsky [ 12/Jul/18 ] |
|
Cate Boerema NCIP and SIP/SIP2 should be broken into two jiras. I'm not sure if this should be at the epic or feature level? We'll only be working on NCIP at Lehigh. thank you! |
| Comment by Cate Boerema (Inactive) [ 12/Jul/18 ] |
|
All set. Thanks! |
| Comment by Cate Boerema (Inactive) [ 03/Sep/18 ] |
|
Hi Michelle Suranofsky! I am wondering if the stories you have linked here should actually be transformed into features. Features are the level at which we do release planning. We assign features to releases (Fix versions in JIRA UXPROD project). Features also get included in the quarterly Gap Analysis survey in which we ask early adopter institutions to submit their priorities. Finally, we also collect t-shirt size estimates on features for our capacity plan. Would it be okay with you if we changed these stories into features? If so, we'd then need to apply a targeted Fix version to each as well as development estimates. Let me know your thoughts. |
| Comment by Michelle Suranofsky [ 05/Sep/18 ] |
|
Hi Cate Boerema ...sounds fine to me. I'll work on the estimates. I do have a decent start on the base project (no functionality yet). I've created an edge module which accepts a request via OKAPI and attempts to pass the request to the NCIP internal module. I'm working on setting up the key properly so the internal NCIP module can validate it. (just an update) |
| Comment by Cate Boerema (Inactive) [ 06/Sep/18 ] |
|
Thanks Michelle Suranofsky! I went ahead and changed these to features. If you could get the estimates in by end of week, that would be great, as we will be updating our overall project and capacity planning document from JIRA this weekend. |
| Comment by Erin Nettifee [ 07/May/19 ] |
|
I see this is currently slotted for Q4. One comment from Duke is about considering the NCIP implementation in Alma - it goes beyond the basic functions to offer additional information about the transaction through NCIP key/value pairs. Duke uses NCIP in consortia with institutions that use Alma, so we would be interested in being able to go beyond the bare-bones implementation in the same ways. |
| Comment by Michelle Suranofsky [ 07/May/19 ] |
|
emailed Erin Nettifee to set up a time to discuss. |
| Comment by Michelle Suranofsky [ 30/Dec/19 ] |
|
The code is in GibHub (links below). I'm working with Jakub to put the Extensible Catalog jar files in a Maven repo. https://github.com/folio-org/mod-ncip |
| Comment by Michelle Suranofsky [ 06/Jan/20 ] |
|
Coding is complete so I am closing this jira. Module tested with a Dec. version of Q4. Will test again with the final release. |