Notes
New features
You’ve previously been able to see principal investigators only on grants, but you can now also see them on gifts, projects, and programs. Note that most gifts, projects, and programs don’t have a principal investigator (unlike grants), so in most cases these new fields will be empty. If there is a PI assigned, though, you’ll now be able to see their name and ID in the API results.
You can now use the FDM validation endpoint with combinations that include a grant cost share. These combos will include multiple driver worktags: the grant cost share, plus one of either gift, project, or program. You can submit them normally, and you’ll receive informative error messages if you have too many or not enough driver worktags.
You can now filter cost centers by their immediate parent hierarchy (ie. their level 8 hierarchy). If you want to filter by a different hierarchy levels (say, you want to get all the cost centers in a level 5 hierarchy), you’ll first need to use the descendantOf filter on the hierarchies endpoint to get a list of level 8 hierarchies, then query the cost centers endpoint using the IDs of those level 8 hierarchies.
Cost centers now list the IDs of their managers and leadership role assignees. Every cost center should have exactly one manager: no more, no less. Leadership role assignees may or may not be present, and there can be more than one. If you need more details on one of these people (like their name or position), use the ID to query the Person API.
We’ve completed work to bring in new data for sponsor invoices, and we’ll work on making that available in the API in the next sprint.
We’re using a new set of internal end-to-end tests to ensure that all our endpoints respond correctly. These won’t be visible to API users, but will help us ensure the API’s reliability while we continue to expand it.
Bugfixes
The Awards endpoint had a bug that resulted in duplicate records for coinvestigators. That bug is now fixed. If you were importing coinvestigators into your own system without checking for uniqueness, you may want to check your records to see if they need a cleanup.
Previously, if you left out some of the required fields when submitting an FDM combination to the FDM validator, you’d get a status code 500 response instead of a detailed validation error message. If you’d submitted multiple combinations, you wouldn’t have a way of knowing which one triggered the 500 response. That bug has been fixed, and you’ll get line-by-line detailed error messages even if you don’t include some of the required fields.
API changes
- Gifts, programs, and projects now include
principalInvestigatorIdandprincipalInvestigatorName validateFdmnow validates cost share grants and gives new error messages for combinations with multiple driversvalidateFdmno longer returns a 500 status if you leave out certain required fields- New
parentHierarchyIdfilter on cost centers - New attributes for
managerIdandleadershipRoleAssigneeson cost centers