Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we revise the "Data" tab? #102

Closed
DenoBeno opened this issue Sep 16, 2019 · 3 comments
Closed

Should we revise the "Data" tab? #102

DenoBeno opened this issue Sep 16, 2019 · 3 comments
Assignees
Labels
BB: Data Dashboard Data Dashboard Building Block duplicate duplicate issue enhancement New feature or request on-hold Issue is on-hold and will be adressed later or closed question Further information is requested

Comments

@DenoBeno
Copy link

related to clarity-h2020/emikat#16

I have recently implemented the "table views" for the vulnerability and for the adaptation options. These views just show the available "data" and allow users to include this data in the report.

What "include in the report" means is an interesting question. In some cases it simply means that the report should contain more information about this data set. In other, it may influence the calculations.

Questions:

  1. Should these "tables" appear under "data" tab? If not, what should?
  2. Should we revise all data tabs in this way?
@DenoBeno DenoBeno transferred this issue from clarity-h2020/emikat Sep 17, 2019
@p-a-s-c-a-l p-a-s-c-a-l removed their assignment Sep 17, 2019
@DenoBeno
Copy link
Author

Current work on "URL variables" (see clarity-h2020/data-package#47) may allow us to drastically lower the number of resources listed per data package, thus making the "data" tabs under "hazard", "local effects" and "element at risk exposure" steps more manageable and eliminating the need to redesign them.

Furthermore, the see #101 will eventually allow users to also limit the number of resources shown in table and map tabs...

I'm still not sure what to do with "data" tabs under "vulnerability" and "adaptation options". Putting this on hold.

@DenoBeno DenoBeno added enhancement New feature or request on-hold Issue is on-hold and will be adressed later or closed question Further information is requested labels Sep 21, 2019
@p-a-s-c-a-l p-a-s-c-a-l added the BB: Data Dashboard Data Dashboard Building Block label Oct 30, 2019
@p-a-s-c-a-l p-a-s-c-a-l added this to the D1.4 CLARITY CSIS v2 milestone Nov 11, 2019
@p-a-s-c-a-l
Copy link
Member

Can this be closed?

@p-a-s-c-a-l p-a-s-c-a-l added the duplicate duplicate issue label Feb 28, 2020
@p-a-s-c-a-l
Copy link
Member

Duplicate of #146

@p-a-s-c-a-l p-a-s-c-a-l marked this as a duplicate of #146 Feb 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BB: Data Dashboard Data Dashboard Building Block duplicate duplicate issue enhancement New feature or request on-hold Issue is on-hold and will be adressed later or closed question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants