Currently, the SAE only gives identifies users with their ORCID (via session ID from Barista). Additionally, to match the expressivity from the graph editor, the SAE should also transmit the selectable user group information.
In manager, used as:
manager.use_groups(null);
or:
manager.use_groups([new_group_id]);
The manager is just use as a temporary hold for the information (as the manager is often holding the widget "state"), but is not necessary--it only needs to be there for the actual request.
In request call, used as:
reqs.use_groups(manager.use_groups());
User info, etc., is gotten with token from the session handling barista:
barista_loc + "/user_info_by_token/" + given_token
Note that there are open issues about the transportation of groups between clients and how they should be generally handled: https://github.com/geneontology/noctua/issues/372 ; this is meant to cover just transmitting selectable groups within the SAE.
Currently, the SAE only gives identifies users with their ORCID (via session ID from Barista). Additionally, to match the expressivity from the graph editor, the SAE should also transmit the selectable user group information.
In manager, used as:
or:
The manager is just use as a temporary hold for the information (as the manager is often holding the widget "state"), but is not necessary--it only needs to be there for the actual request.
In request call, used as:
User info, etc., is gotten with token from the session handling barista: barista_loc + "/user_info_by_token/" + given_token
Note that there are open issues about the transportation of groups between clients and how they should be generally handled: https://github.com/geneontology/noctua/issues/372 ; this is meant to cover just transmitting selectable groups within the SAE.