This issue is for discussing user-facing aspects of the EIDF integration.
Our initial proposal for the user experience is as follows (automated steps in italics):
User runs battery experiment and creates data in a monitored path
Galvanalyser crawls monitored path and extracts dataset information
User logs in to Galvanalyser (local instance) and edits dataset metadata
User clicks 'Upload to EIDF' button when satisfied with metadata accuracy
Galvanalyser uploads data to EIDF
Thereafter data will be available via the EIDF for analysis within their cluster, handling long-term storage (useful for publication linking, etc), and other services. Data can still be accessed and analysed via the local Galvanalyser instance, too.
This issue is for discussing user-facing aspects of the EIDF integration.
Our initial proposal for the user experience is as follows (automated steps in italics):
Thereafter data will be available via the EIDF for analysis within their cluster, handling long-term storage (useful for publication linking, etc), and other services. Data can still be accessed and analysed via the local Galvanalyser instance, too.