GET /v1/opportunities/<opportunityId>
- If rules are configured on a per opportunity basis, we should list all the rules without needing to make another request:
Current rules object in opportunities:
"rules": { "opportunityId": 531659, "canSubmitNewRequest": true, "noAvailableActionsReason": [], "resourceIdsAvailableForNewRequest": [ 530903, 530185, 530201, 530275, 530902 ], "gracePeriod": 1, "availableActionRequests": [] }
- Currently, in the person request we don't have role_types or any roles for the user. This would beneficial to have within the person object so that the front-end can display something like the displayRoleType.
Current person object looks like this:
{ "message": null, "result": { "username": "metzger", "firstName": "Luis", "middleName": null, "lastName": "Metzger", "email": "luismetzger@me.com", "phone": "303-591-3076", "academicStatus": "Industrial User", "residenceCountry": null, "organization": "UCAR" } }
- For supporting grants, we require several API requests to GET certain data, such as:
Funding Agencies:
{ "fundingAgencyId":1, "fundingAgencyName":"National Science Foundation (NSF)", "fundingAgencyAbbr":"NSF", "relativeOrder":1 }
Unit types:
{ "unitTypeId":1, "unitType":"Dollars", "displayUnitType":"Dollars" }
FOS types:
{ "fosTypeId":1, "fosName":"Mathematical and Physical Sciences", "fosAbbr":"MPS", "fosNum":100, "fosTypeParentId":null, "isActive":true }
- Anyway we can combine this to allow for a decrease in supporting Grants?
- Possible Solutions:
- Funding Agencies can have nested attributes of what is required for each.
- Possible Solutions: