search

hubmapconsortium / portal-ui

HuBMAP Data Portal front end
https://portal.hubmapconsortium.org
MIT License
12 stars 2 forks source link

Mock-up attribution details #36

Closed mccalluc closed 5 years ago

mccalluc commented 5 years ago

Assuming the API will be able to provide us with this information: (based on ENCODE)

Contributor Michael Snyder, Stanford Award U54HG006996 (Michael Snyder, Stanford) Project ENCODE Date submitted May 2, 2017 Internal release .... Public release May 17, 2017

shirey commented 5 years ago

@mccalluc For a data set you'll eventually get most of this data with the exception of:

mccalluc commented 5 years ago

for contributor you may not get the details of the person, but may only get the person identifier, which will need to be looked up in another (yet specified) user information API.

@shirey : for now, I'll assume this is the way it will work... but multiple successive roundtrips to the API to get basic page content will really hurt performance. If a particular request is intrinsically complicated, and we don't want to hold up the rest of the page, it could be moved to the client side, but I don't think this is an example of that.

(If this is a matter of REST orthodoxy, we need to get past that. There are lots of good reasons to diverge from a pure REST approach.)