ruegenbfr
commented
3 years ago Proposed solutions:
- use window.postMessage System:
- NRW Page opens Browser tab/window (with fcl-client) and provides data by using postMessage system
- If the supplied data is not the model data itself but a resource link/id, the fcl-client gets the model data from the external (NRW) resource.
- use url parameter on fcl-client start:
- NRW Page opens fcl-client with an additional (resource link / id) parameter in the url
- the fcl-client gets the model data from the external (NRW) resource.
- use fcl-server api:
- NRW Page calls fcl-server API to 'leave' data for a specific post box (which belongs to a user account), using a user account postbox id
- fcl-client loads model data either from the fcl-server or from the external (NRW) resource, depending of the nature of the postbox data
See details here: https://app.zenhub.com/files/61294409/fb612749-907a-4dad-8e59-5a6b2315d0ea/download
Next step:
Discuss solutions with NRW
As a user of the NRW ATAST tool I would like to be able to view the ATAST data easily in FCL Web (same user, same computer).
Workflow in the NRW tool: When clicking the FCL Web button, the data is prepared as a JSON file and stored in local storage and FCL Web website is called
Workflow in FCL Web: When user visits FCL Web and is coming from NRW ATAST tool website, the user should be able to login to FCL Web (manual login). After successful login, the Tracing view should be opened and the data should be loaded automatically (from local browser storage).
DevNote: Can local browser storage be used from two apps? Security issues? Local storage for all user acounts. Delete local storage afterwards.
CAVE: This is the workflow for users already registered in FCL Web. If users are not registered/forgot the password, they have to register/recover password first and then again export the data from the ATAST system in order to start the workflow.
Alternative: KNIME script (Selenium) --> ask Alex/Birgit.
Think of Tests
Additional context