| | 22 | |
| | 23 | == Needs of the PhenoFlow module (lifelines, bbmri, gids2.0) == |
| | 24 | |
| | 25 | PhenoFlow is the user interface for searching, browsing and extracting phenotype data from the Pheno model. |
| | 26 | |
| | 27 | The systems (that will be) using this module are |
| | 28 | * LifeLines (datawarehouse) |
| | 29 | * BBMRI-NL (biobank catalog) and |
| | 30 | * gids (2.0). |
| | 31 | * COL7A1 Phenotype/Patient browser (here one gene == one investigation) |
| | 32 | * XGAP data browser |
| | 33 | |
| | 34 | Requirements: |
| | 35 | * Users need to be able to login |
| | 36 | * All registered users have edit permissions to create new investigations |
| | 37 | * All existing investigations can only be listed (names) but no other values |
| | 38 | * All investigations are owned by one or more persons |
| | 39 | * If not yet owned, users can request to become manager of an investigation. |
| | 40 | * Otherwise users can request read access to the investigation |
| | 41 | * Users can create groups of themselves (except for lifelines) |
| | 42 | * Users can share an investigation and all its components to [public, groups, whitelists of users) for viewing |
| | 43 | * The sharing rules can be read or write (so that means they can transfer management of an investigation) |
| | 44 | * All InvestigationElement inherit the sharing rules set on an investigation (hence, if the investigation is public so are all its elements) |
| | 45 | * Individual investigation elements, and the dataelements that refer to them can have different permissions (lifelines) |
| | 46 | |
| | 47 | Issues: |
| | 48 | * What about data that is not an Investigation/InvestigationElement? |
| | 49 | |
| | 50 | See www.myexperiment.org for some inspiration on how this 'sharing' model can work. |
