Edge API Core (Common Infrastructure)
(UXPROD-994)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Edge API Core (Common Infrastructure) |
| Type: | New Feature | Priority: | P3 |
| Reporter: | VBar | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | NFR, edgeapi, external_sys_int, suppress-from-capplan | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Edge API Core (Common Infrastructure) | ||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Small < 3 days | ||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | VBar | ||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | VBar | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Edge APIs: Edge APIs for Folio are designed to allow external systems to integrate with Folio. These are distinct from the internal APIs used by Folio and implemented though Okapi. It is not recommended that external systems integrate directly with Folio/Okapi APIs. Edge APIs....
The scope of this feature is the implementation of common infrastructure to all Edge APIs. Specifically, it is an NFR optimization to avoid the code duplication (and inconsistencies) that might occur across various Edge API implementations. It is not a blocker for the implementation of those implementations. Estimates from stories:
Not included in roll-up:
|
| 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 VBar [ 26/Apr/18 ] |
|
This is something that stands apart from all those. "Edge API" should be its own project in exactly the same way that Stripes is its own project - it is an alternative to Stripes. |
| 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) [ 09/Jul/18 ] |
|
Actually, I should leave these as features and clone them to create epics. I will change this back to a feature and associate it with this new, cloned epic:
|
| Comment by Cate Boerema (Inactive) [ 24/Sep/18 ] |
|
VBar is this feature still needed as a separate work item or is the common infrastructure now being addressed as we implement purpose-built APIs? |
| Comment by VBar [ 28/Sep/18 ] |
|
Yes, it represents the work encapsulated in "edge-common" which is a library/framework with its own repo in GitHub. |
| Comment by Cate Boerema (Inactive) [ 10/Oct/18 ] |
|
VBar, what would be the impact to Chalmers if this feature was not ready at go-live? |
| Comment by Cate Boerema (Inactive) [ 21/Nov/18 ] |
|
Per FOLIO team meeting yesterday, this is an NFR and shouldn't be ranked. I will remove the early implementer rankings (all were "go-live"). VBar will adjust the feature description, if needed. |
| Comment by VBar [ 21/Nov/18 ] |
|
This feature does not block the implementation of individual Edge APIs. |