...
The data displayed by a dashboard widget isn’t likely just a single query, but can possibly contain data from a group of queries with results that contain human-legible strings associated with unique id’s (UUID’s). For the results to render in a human-legible way, each of the associated queries must finish execution. For example, items in the /users query contain a field for patron_group , which contains a UUID that’s associated with an item from results procured from the /group endpoint. https://s3.amazonaws.com/foliodocs/api/mod-users/r/users.html#users_get Registered components can be created to make their own requests - this currently happens in the licenses widget: https://github.com/folio-org/stripes-erm-components/blob/master/lib/InternalContactsArrayDisplay/InternalContactsArrayDisplay.js
The next major requirement for rendering is describing how the values should be represented in a useful way. Is the value to be rendered as a link? Where in the data does the label for the link or the href come from? If these questions are not fulfilled, the user will be likely presented by generic, meaningless representation such as [object Object] or possibly long UUID’s where meaningful data should be.
...