EUROfusion Data Availability Assumptions
EUROfusion data access scenarios and assumptions regarding authentication, public availability, and data mapping activities for Scenario A and Scenario B. The implications of open access, meta-data definitions, and user authentication on data releases and access models within the EUROfusion framework are discussed.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
DMP assumesthatall (EUROfusion) data willbe made availableto EUROfusionusers
Scenario A data access -userview We have in addition been assuming as a workinghypotheses that the Scenario A data willbe available withoutspecific authentication Either open on a public ip-address or at the very least on the GW Which option do we agree on? And does it have implications on data releases!? Will it in addition have an impact the configuration on n the new GW? Scenario A data is meta-data - in our specification it is low resolution waveforms For MAST/MAST-U (?) Meta data is public but they do not currently agree on our definition of meta data
ScenarioA Scenario B SOFT DEMO Production Production AUG Public Public? We should get a better view on intentions! COMPASS N/A ? JET N/A ? MAST/-u N/A ? TCV Public Public? public/2 year embargo public/2 year embargo WEST
Scenario B data access Limited access for higher dimensional datarelated to specific use cases. Implications on Data mapping activities EQ/MHD stab, TSVV11, TSVV1 ad TSVV10 Pre or postprocessing of things like core_profiles? Distributions for Access model: Incoming authenticated gateway users have access to existing data based on (local) authorisation Once authenticated (on GW) nothing additional should be needed for accessing EUROfusion data that has been made available throughDMP tools and data mappings.
ScenarioA Scenario B SOFT DEMO Production Production AUG Public Public? AAI? We should get a better view on intentions! COMPASS N/A ? AAI? JET N/A ? AAI? MAST/-u N/A ? AAI? TCV Public Public? AAI? public/2 year embargo public/2 year embargo WEST AAI?
