...
| 페이지 속성 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Ambition
...
EISCAT Scientific Association participates in hte EOSC Hub WP8 Competence Centre with the aim of developing a user portal for the future radar system EISCAT_3D, which is planned to start operation during 2021-2022.
User stories
| 정보 | ||
|---|---|---|
| ||
Requirements are based on a user story, which is is an informal, natural language description of one or more features of a software system. User stories are often written from the perspective of an end user or user of a system. Depending on the community, user stories may be written by various stakeholders including clients, users, managers or development team members. They facilitate sensemaking and communication, that is, they help software teams organize their understanding of the system and its context. Please do not confuse user story with system requirements. A user story is an informal description of a feature; a requirement is a formal description of need (See section later). User stories may follow one of several formats or templates. The most common would be: "As a <role>, I want <capability> so that <receive benefit>" "In order to <receive benefit> as a <role>, I want <goal/desire>" "As <persona>, I want <what?> so that <why?>" where a persona is a fictional stakeholder (e.g. user). A persona may include a name, picture; characteristics, behaviours, attitudes, and a goal which the product should help them achieve. Example: “As provider of the Climate gateway I want to empower researchers from academia to interact with datasets stored in the Climate Catalogue, and bring their own applications to analyse this data on remote cloud servers offered via EGI.” |
EISCAT_3D will generate raw data at a few observation up to three radar sites (each with almost 10000 antennas) and has to make those data browsable and analysable for researchers, as well as archiving the data for the long-term. It is planned to archive around 2 PB per year. This primary mission is achieved by procuring sufficiently big storage and network capacities at a few data/compute centres (for back-up or load distribution). The raw data is will be transferred to this/these locations , often after initial filtering and calibration at the data source(s). The data/compute centres are responsible for data archival, data curation, generation of derived data (level 1-2-3) and for sharing the data with scientists.
Data must be shared with scientists via a data portal and programming APIs. The ' EISCAT_3D Data Portal ' should offer the following main features:
- User AAI, user login
- Data browser
- Data download
- Online computing (analyse data without downloading them, using remote cloud resources and , reference applications or user's own software)
The CC is exploring the use of the following services within the framework of EOSC-hub servicesHub:
Application and data catalogue portal with compute integration: DIRAC
Metadata catalogue for high-level data: B2Find
Metadata catalogue for low-level data: DiracDIRAC
Compute resources: EISCAT, EGI HTC, EGI Cloud, institutional clouds (e.g. cPouta cloud at CSC)
Data storage and transfer (data→compute centres): File transfer TBD, e.g. B2STAGE
User SSO: EGI CheckIn and B2Access
...
Step | Description of action | Dependency on 3rd party services (EOSC-hub or other) |
|---|---|---|
UC1 | Authentication:
|
|
UC2 | Data access:
|
|
UC3 | Computation:
|
|
...
Requirement ID | EOSC-hub service | GAP (Yes/No) + description | Requirement description | Source Use Case |
|---|---|---|---|---|
RQ1 | EOSC-hub AAI | Yes: Dirac | Dirac interface to EGICheckin | UC1 |
| RQ2 | VM | Yes: VM | VM for portal | UC1 |
| RQ3 | Data staging | Yes: File system | File storage | UC3 |
RQ4 | Cloud Compute | Yes: HPC | Run software VM and/or container | UC3 |
| RQ5 | PID/DOI service | Yes: Registry | Registration of collection | UC2,3 |
| RQ6 | EOSC-hub Check-in | Yes:Check-in | EISCAT community include collaborations from includes institutes in Japan and China. Currently, check-in Checkin has been integrated into the EISCAT data portal that based on DIRAC4EGI technology. Other social logins are to be implemented, see GGUS ticket:https://ggus.eu/index.php?mode=ticket_info&ticket_id=139172&come_from=submit | UC1 |
...