SIP2: Protocol for self-checkout
(UXPROD-1001)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | SIP2: Protocol for self-checkout |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Björn Muschall | Assignee: | Tim Auger |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | external_sys_int, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Epic Link: | SIP2: Protocol for self-checkout | ||||||||
| Development Team: | Volaris | ||||||||
| PO Rank: | 0 | ||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||
| Description |
|
Current situation or problem: In Settings/Circulation/General/Other settings it is possible to select multiple patron IDs for checkout scanning, i.e. Barcode, External system ID, Username, Custom field. This configuration only relates to UI-checkout and not for identifiers used by SIP2. According to SIP2-83 on SIP2 checkout the patron can be identified by scanning barcode, externalSystemId or user name. On a tenant level it should be possible to define which of these fields are used by SIP2 checkout as Patron Identifier (AA) to avoid conflicts among ID spaces. In scope Out of scope Use case(s) Proposed solution/stories Configuration of used identifier(s) in a SIP configuration file. Links to additional info Questions |
| Comments |
| Comment by Khalilah Gambrell [ 09/Sep/22 ] |
|
Hey Tim Auger - I just noticed this SIP2 feature and assigned it to you for your review. |
| Comment by Brooks Travis [ 05/Feb/24 ] |
|
I wonder if this should be extended to include the ability to specify a custom field for lookup, just like the UI, as well. This would be critical to supporting things like NFC ID cards on phones and watches, where a patron can have way more than three identifiers they would expect to be able to use with self-check. |