provide user stories for discovery metadata

[tomkralidis]

As part of the next version of WCMP, we need to identify user stories that capture goals and acceptance criteria. The user stories will capture what a user does/needs as part of their work, and will help clarify user needs as we continue to assess metadata standards.

[josusky]

@gaubert I have the impression, that this team wrote some user stories previously, before the reorganization. But I cannot find any such document here on GitHub. Am I mistaking it for the work of some other team? Or it was just saved somewhere in the old WMO wiki?

Anyway, for a quick start I offer these brief story descriptions (@tomkralidis is this what you had in mind, or was it something more elaborate?):

1. As an NWP center operator I want to quickly and easily publish information about the data that my centre provides and update it as needed in a (semi)automated way using the information that I already have in my vast databases so that I can concentrate on my core business.
2. As the leader of a forecasting team of a national meteorological institution, I would like to be able to find more sources of data that might be relevant/useful for the work of my team, notably NWP and satellite imagery so that we could further improve our predictions. That should work for unprocessed outputs of a prediction model or a satellite as well as for services that offer more sophisticated access to the data, e.g. tailing.
3. As an entrepreneur (start-up) that provides (wants to provide) tailored weather information I want to be able to find services (free or commercial) that provide meteorological data in a cloud or even better, provide customizable processing of such data - to be able to build my own service on top of it. And I want to be able to find out if a new such service appears or if an existing one changes its abilities so that my company can keep on advancing.
4. As a software developer (working for a national met center or a private company), I would like to find a relevant technical description of the service (API) that my boss wants me to integrate with, so that the declared interoperability becomes reality.

[tomkralidis]

Thanks for getting this started @josusky. This is exactly what we are looking for. Adding:

1. As a user I would like to search for real-time observations for a given time and geographical area of interest so that I can have up to date information on weather for my city
2. As a web developer I would like to access to a search API that provides easy to read documentation, examples, and a simple, intuitive RESTful API with JSON so that I can integrate into my web application quickly
3. As a GIS professional, I would like to search for weather/climate/water data from my GIS Desktop support tool so that I can integrate forecast data into my workflow

[kaiwirt]

A while ago we made a video on this. Which covers exactly the three groups you mention. The everyday user, the developer and the weather specialist. Here is the advertisement block :-)

https://gisc.dwd.de/wis2.0/WIS_2.0_final.mp4

[tomkralidis]

Thanks @kaiwirt ! Below, as user stories.

1. as an everyday user, I would like to find easy to understand and precise weather data so that I can plan to have people over for an outdoor BBQ on a nice day
2. as a smart home owner, I would like access to frequently updated data so that I can keep my smart home monitoring up to date
3. as a weather specialist, I would like to access weather data in native data formats and subscribe to product updates, so that I can provide tailor made weather services to my users

[josusky]

Hi @kaiwirt , I like your video. It explains multiple requirements that the national weather services have to fulfill. However, I dare to say, that the BBQ story is not a valid user story for WIS. At least not directly. The reason being, that this requirement is very well fulfilled for quite some time already - by the tons of weather-related web pages, many of them being the "main" web pages of the national weather services. WIS is, from the BBQ user perspective, a back-end, not the front-end. Our user is the developer of the public web page.

[amilan17]

1. As a data/metadata provider, I want statistics on the different types of data/metadata (e.g. the 'core', 'recommended' and 'other'), so that I can identify successes and gaps.
2. As WMO auditor, I want statistics organized by data/metadata provider, so that I can identify compliance.

[amilan17]

@tomkralidis I think we can close this

[tomkralidis]

User stories are included in WCMP2 at https://wmo-im.github.io/wcmp2/standard/wcmp2-DRAFT.html#_user_stories