Spike: Define technical approach for using RM API to filter results by tags

Spike Work
Review rmapiedge micro service to support following 5 POST end points which needs to be exposed to external customers for supporting filtering results by tags
a. POST /rm/rmaccounts/{epcustomerid}/packages (Should accept array of packageIDs and POST response should match with corresponding GET response)
b. POST /rm/rmaccounts/{custid}/vendors (Should accept array of VendorIDs and POST response should match with corresponding GET response)
c. POST /rm/rmaccounts/{custid}/titles (Should accept array of KBIDs and POST response should match with corresponding GET response)
d. POST /{custid}/vendors/{vendorid}/packages (Should accept array of packageIDs and POST response should match with corresponding GET response)
e. POST /{custid}/vendors/{vendorid}/packages/{packageid}/titles (Should accept array of KBIDs and POST response should match with corresponding GET response)

• Also consider if a different approach should be recommended to support the best user experience for filtering results by tags.

Deliverables

• Define technical approach for filtering by tags
  • All options should be reviewed with Vince.
  • Consider large results sets and sorting (may need to consider fetching/paging and sort will be by Name (A-Z)
  • And consider that number of customers in the next 3 years maybe ~15
• Present findings and approach to team (include pros/cons) for recommended approach

Timebox 5 days