[UISE-28] Short but rigorous document specifying the Codex provider contract - FOLIO Issue Tracker

XML

Word

Printable

Details

Type: Task
Status: Closed (View Workflow)
Priority: P1
Resolution: Done
Affects Version/s: None
Fix Version/s: 1.2.0
Labels:
- sprint28

Template:

Description

Once we have this, several other other UISE issues will become more grounded: it will become possible for me to write UI code against the spec in the knowledge that it will work correctly when the providers become available.

It will link to (and probably comment on) the machine-readable schemas:

TestRail: Results

Attachments

Issue Links

blocks

UISE-2 Search Type Picker: Navigate between All/Local/KB

Closed

UISE-3 Search Type Picker. Search constrained to instances in the Inventory app

Closed

UISE-4 Search Type Picker: Search constrained to KB-instances in the eHolding app

Closed

relates to

MODCXINV-3 expose CODEX instance endpoint

Closed

UISE-27 Figure out which Codex fields supply the source-DB and ID

Closed

Activity

People

Assignee:: Mike Taylor

Reporter:: Mike Taylor

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 11/Dec/17 5:29 PM

Updated:: 18/Dec/17 12:36 PM

Resolved:: 13/Dec/17 1:11 AM

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

1d 2h

Short but rigorous document specifying the Codex provider contract