RTAC Support
(UXPROD-1004)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q3 2018 | Parent: | RTAC Support |
| Type: | New Feature | Priority: | P3 |
| Reporter: | VBar | Assignee: | Mark Veksler |
| Resolution: | Done | Votes: | 0 |
| Labels: | edgeapi, external_sys_int, patronportal | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||
| Epic Link: | RTAC Support | ||||||||||||||||||||||||
| Front End Estimate: | Small < 3 days | ||||||||||||||||||||||||
| Front End Estimator: | VBar | ||||||||||||||||||||||||
| Back End Estimate: | XL < 15 days | ||||||||||||||||||||||||
| Back End Estimator: | VBar | ||||||||||||||||||||||||
| Development Team: | EBSCO - FSE | ||||||||||||||||||||||||
| Rank: BNCF (MVP Feb 2020): | R1 | ||||||||||||||||||||||||
| 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: GBV (MVP Sum 2020): | 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 | ||||||||||||||||||||||||
| Description |
|
RTAC stands for Real Time Availability Check. Its purpose is to allow an OPAC or Discovery system to augment its search results by running additional queries against the ILS to establish the status of the item shown in the result: is it available?; on hold? already checked out? etc.. This is accomplished by having the ILS provide a few externally facing API endpoints that the OPAC/Discovery system can integrate with. It’s something available from all ILSes in one form or another.
|
| Comments |
| Comment by Cate Boerema (Inactive) [ 26/Apr/18 ] |
|
VBar, I need to tag this with a project. Is it Analytics, GDPR, something else? |
| Comment by Cate Boerema (Inactive) [ 09/Jul/18 ] |
|
Changing all the external system integration features into epics. While this will extend the epic list by 7 items, these really are all mini-projects that can be assigned to teams and have POs and priorities. In that regard, they make sense as epics. I will deprecate the old External Systems Integrations epic. |
| Comment by Cate Boerema (Inactive) [ 16/Jul/18 ] |
|
Actually, I should clone these to make epics. Changing this back to a new feature and linking up to a new, cloned epic:
|
| Comment by Cate Boerema (Inactive) [ 18/Sep/18 ] |
|
Mark Veksler, this feature is in draft which means the PO (you) is working on completing the story definition. Is that accurate or are the stories defined here all there is? If the latter, then this feature should be closed (as all the stories it contains are closed). |
| Comment by Cate Boerema (Inactive) [ 10/Oct/18 ] |
|
Mark Veksler, what's the status on this? Looks like all the related stories are completed. Can we close this feature as done? If so, we also need to give it a fix version. Thanks! |