[MODUSERS-35] Refactor proxyFor field into separate endpoint - FOLIO Issue Tracker

XML

Word

Printable

Details

Type: Task
Status: Closed (View Workflow)
Priority: P3
Resolution: Done
Affects Version/s: None
Fix Version/s: 15.2.0
Labels:

Template:

Description

Proxies are requiring associated metadata for the relationship and the requirements are exceeding what can be cleanly implemented as a single field in the user object. It makes sense to give proxy information its own endpoint, e.g. /userproxy

Potential data fields for a proxy entry might be:

{
  "userId" : "ca678eec-ad11-11e7-abc4-cec278b6b50a",
  "proxyForId" : "ca679162-ad11-11e7-abc4-cec278b6b50a",
  "meta" : {
    ...
  }
}

TestRail: Results

Attachments

Issue Links

blocks

CIRC-42 Support Users Interface Version 15.0

Closed

MODNOTES-28 Upgrade to mod-users 15

Closed

MODNOTIFY-14 Upgrade to mod-users 15

Closed

MODUSERBL-19 Incorporate proxy information in returned composite object

Closed

UIU-181 Assign Proxy v2: Sponsor Sub-Section

Closed

UIU-199 Assign Proxy v2: Proxy Sub-Section

Closed

UIU-292 rewire proxy selection with the new /proxiesfor endpoint

Closed

(2 blocks)

Activity

People

Assignee:: Kurt Nordstrom

Reporter:: Kurt Nordstrom

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 09/Oct/17 4:50 PM

Updated:: 18/Sep/18 8:03 PM

Resolved:: 07/Nov/17 12:52 PM

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

4d 2h

Refactor proxyFor field into separate endpoint