...
In existing portals the Synapse back-end can compute this information because it possesses all the required information: The list of files in the download cart, the access requirements applied to those files, and the access approval state for the user for each access requirement. But
Index of available file data;
Download cart (a subset of the indexed files);
Access requirements, applied to folders and/or files;
Access approvals, each related to an access requirement and a user
However, in the AMP-ALS portal the Synapse back end won’t be the source of information about users' access approval so it will lack this information, which instead has to be retrieved . Instead it has to retrieve this information from remote data repository(ies).
...
Note that when the Portal logins in, it receives an access token (AT) to the Service (not for either linked data repository). This is labelled, , “AT-Service”. (The prerequisite account linking is not shown in this diagram.) When the Portal requires a resource which is held by Synapse, it sends a request to the Service, which recognizes the request as being relevant to Synapse, obtains a Synapse access token (“AT-SYN”), issues the request, and returns the result. In short the Service acts a proxy to the Synapse REST APIs. The Service could similarly interact with RDCA-DAP to retrieve resources held there, and perhaps issue data access requests.
...