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

Allow 'features' from user generated lists to be displayed in a similar way to threatened status displayed from conservation lists. #305

Open
rp-ala opened this issue Mar 10, 2016 · 3 comments
Labels
Project - IEK Garragal project

Comments

@rp-ala
Copy link

rp-ala commented Mar 10, 2016

Ability to identify e.g. 'species of concern' from an Indigenous cultural perspective, from a user specified 'features' list.

@rp-ala rp-ala added the IEK label Mar 10, 2016
@m-r-c
Copy link
Contributor

m-r-c commented Mar 21, 2016

Does this mean to display the data as text, or to render coloured icons of some sort like the conservation status icons? Text can already be displayed via the 'feature list' controls. Icons would be trickier, as the admin would probably need to provide a mapping from their specific list entries.

@rp-ala
Copy link
Author

rp-ala commented Mar 21, 2016

Ultimately, the ability for the admin to map icons for key features would be good for ease of use and to reduce reliance on text-based interfaces. At present, let's run with the text implementation, and look at the priority for icons amongst other needs at a later stage.

@m-r-c
Copy link
Contributor

m-r-c commented Apr 29, 2016

To investigate: it is possible to create a list containing an attribute with a url to an image, then use that to render the image on the profile page. This could be used instead of or as well as the colour-coded statuses.

@pbrenton pbrenton added Project - IEK Garragal project and removed IEK labels Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Project - IEK Garragal project
Projects
None yet
Development

No branches or pull requests

3 participants