Short description	STARS4ALL is a community concerned with the light-pollution problem; involved in EOSChub as a EAP STARS4ALL (http://www.stars4all.eu) was originally a project funded by the European Union H2020 Programme (688135) to create awareness among citizens about the light pollution problem. For this purpose, it deploys a platform to give support to some light pollution initiatives. These initiatives include a photometer network (http://tess.stars4all.eu) to continuously monitorize the light pollution, using photometers to measure the sky brightness. In this context, it deploys a platform (http://tess.dashboards.stars4all.eu) to show the measurements in some dashboards. All data is published openly in our Zenodo’s community (https://zenodo.org/communities/stars4all). The project was completed in 2018 but STARTS4ALL continues the work through the foundation created for this purpose. Since then, the number of photometers has been continuously growing, until reaching 100 units. They expect to double this quantity this year, multiplying the number of units in the following years. Each minute, our system receive a measurement from each photometer, so there is a need to increase in the future the capacity of the network. STARS4ALL made a proposal for the first call of EOSChub EAP and the user stories and use-cases are derived from that and from discussions with the project PI 17-11-2019 Story and use-cases to be updated on the basis of the now accepted EAP proposal
Type of community	crowd sourcing infrastructure
Community contact	Esteban Gonzalez Guardia (e.g.guardia@gmail.com)
Interviewer	-
Date of interview	-
Meetings	-
Supporters	Shepherd; Daan Broeder

User stories

No.	User stories
US1	tbd
US2	tbd
...

Use cases

A use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language as an actor) and a system to achieve a goal.

Include in this section any diagrams that could facilitate the understanding of the use cases and their relationships.

General considerations

STARS4ALL is based in a set of initiatives, which a great variety of outputs. We want to model each initiative as a research object, or a composition of them. For practical effects, an initiative is a project.

Step	Description of action	Dependency on 3rd party services (EOSC-hub or other)
UC1	Creation of an initiative.	The user wants to register a new initiative by creating a description in B2SHARE. As a result, a persistent identifier or PID will be created.
UC2	Creation of a research object in B2SHARE	The user wants to register a new research object in B2SHARE. As a result, a persistent identifier or PID will be created identifying the RO and the initiative
UC3	Add objects to a research objects in B2SHARE.	The user wants to deposit a resource in B2SHARE (uploading a file to B2SHARE or giving a uri of the resource). This resource will be linked (filling in with the appropriate metadata) with the research object via the RO id and because of that with the initiative. In the case of Zenodo, the metadata of a research object will be completed with the metadata present in Zenodo.
UC3	Navigate among the resources of a research object, or the elements of an initiative.	The user will be able to consult all the outputs of an initiative /research object in B2SHARE, that has previously been registered in B2SHARE and indexed in B2FIND. All the resources’ links will be actionable in other words, the user will be able to navigate through them, as a HTML webpage.
UC4	Register a photometer	The user wants to register a new monitoring station in B2HANDLE, generating a persistent identifier (PID) in the system. This station will have information associated such as location, sensors information (the schema based on SOAF?), etc …). This PID will be used and linked when a user deposit the measurements of the sensor (in UC1).
UC5	data integration in GEOSS portal	When a user deposit a dataset (UC3) related with a sensor (UC5), all this information will be integrated in the GEOSS platform. As a consequence, the user will be able to consult all the information and measurements generated by this sensor.
UC6	Analyzing the observation data with a set of Jupiter Notebooks

Requirements

Technical Requirements

- Requirement number: Use numbers RQ1, RQ2, RQ3, ...
- Requirement title: Use a short but descriptive title. Use the same title in the Jira ticket 'Summary' field
- Link to requirement JIRA ticket: Open a ticket in <this JIRA queue https://jira.eosc-hub.eu/projects/EOSCWP10/issues/EOSCWP10-4?filter=allopenissues> (click on 'CREATE' button in the middle-top of JIRA)
- Source use case: Refer back to the use cases above (UC1, 2, ...)

Requirement number	Requirement title	Source Use Case
Example	EOSC-hub to provide an FTS data transfer service	UC1
RQ1	STARS4ALL Research object metadata schema
RQ2	photo sensor PID schema
RQ3	STARS4ALL RO md schema B2FIND mapping
RQ4	JN access to B2SHARE stored data
RQ5	JN access to Zenodo stored data

Capacity Requirements

EOSC-hub services	Amount of requested resources	Time period
VM	1x (1CPU, 8GB RAM, 20GB)	Q3
VM	1x (1CPU, 4GB RAM, 10GB)	Q3
VM	2x (1CPU, 4GB RAM, 50GB)	Q3
JN Hub	light version	Q1 2020