Use cases and user personas for WG

[jyucsiro]

This issue aims to capture user stories for the DPN-O WG to work through in order to develop sensible extensions/refinements required based on existing web services.

[jyucsiro]

I'd suggest we use the following template for user personas/profiles:
As ,
I want <what?>
so that <why?>.

[jyucsiro]

[benjaminleighton]

Name: Annotate Diverse Data
Persona: Data science / Community Curator

I want: My own instance of a DBL to which I can add records of diverse, existing, datasets
I want: to gather these records of datasets and services from sources I have no control over.
I want: to annotate these records using an O&M like scheme to suit my and my communities purpose.
So that: I and others can discover them by spatial temporal and semantic queries.
So that: I do not need to make request of the data and service owners provide annotations.
So that: I can provide my own annotations that might conflict/coexist with some other person or communities meta data about the same services or datasets.

Name: Progressively Describe Subsets
Persona: Data Owner

I want: To add records about my data quickly to a DBL with a minimum of meta data.
I want: To initially treat this data as a single dataset with basic annotations
I want: To progressively refine the meta data for this data by providing meta data for data within this dataset. I may consider these subsets to be new related datasets.
So that: I can incrementally provide finer discoverability to my self and others.
So that: I can assess which subsets of my data are most valuable and provide annotation progressively.

[ashleysommer]

From the Soils Project:

Persona: Provider of an aggregated view of Data Providers of Time-series Datasets
I want: To allow third party software to connect to my DBL to discover Data Providers
I want: the ability to expose data providers which provide Time Series Data services
I want: to store metadata about time-series datasets in the DBL cache
I want: to discover time-series datasets and metadata from known SensorCloud instances
so that: the third party software needs to connect only to our DBL to discover all of the available relevant time-series data providers
so that: the third party software can use the DBL to filter or search time-series datasets based on metadata stored in the dbl harvest cache

(Extensions to the DPN/services ontology and DPN/dataset ontology are already implemented and in use to support the above)

[benjaminleighton]

Name: Filtered Datasets
Persona: Data Owner / Data Scientist / Community Curator

I want: To describe of a Dataset which is accessible through a service or available within another dataset but cannot be simply identified or linked
So that: I and others can discover them by spatial temporal and semantic queries.
So that: I can describe subsets of opaque services or datasets without having to reengineer them

[gajowi]

Name: Dynamic Service
Persona, Data Owner / Service Provider

I want to express the potentiality for providing services to access a data collection
so that: consumers can request that a service be instantiated to serve the data
and so that: services do not need to be kept up occupying resources