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

Export screen - various date order and reliablity/severity order #425

Open
patricechataigner opened this issue May 31, 2017 · 2 comments
Open
Milestone

Comments

@patricechataigner
Copy link
Collaborator

Would be good to see the number of entries associated with each pillar/sub pillar and the total number of entries somewhere, which change when filters are selected of course...

Also, just checkign the mock up, important to have a button for selecting the date order ( from most recent to ancient) and the possibility to change the symbols for reliability or severity ( probably not an emergency) and the order of appearing for severity and reliablitiy ( more important than the symbol stuff)

Just adding the mock up for reference
170426 Export mock up.docx

@eoglethorpe eoglethorpe modified the milestone: OCHA Jun 5, 2017
@bibekdahal
Copy link
Collaborator

Showing number of entries means we load all entries and filter them in the export screen. Like in the entries page, it will take some time to load all those entries.

For the rest of the features, do we need them for both types of projects (that is, with and without analysis framework)?

For the date ordering, should we use Information date, Entry imported date or Lead published date?

We haven't actually shown scale or date for the analysis framework based export. That's because user can have any number of those elements in the analysis framework. It would be good to know how you would like us to handle this?

@patricechataigner
Copy link
Collaborator Author

patricechataigner commented Jun 8, 2017 via email

bibekdahal added a commit that referenced this issue Jun 14, 2017
bibekdahal added a commit that referenced this issue Jun 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants