Also, we do need to revisit the display of the conservation status cards in the new database. I have previously discussed this with Florian, multiple times, and I’m still not happy with how it’s been done. The way the listings table was done in the old database has caused many issues for us. It is a problem in the old database that I didn’t want carried over to the new database, but it has been. The conservation status listings, history and current statuses need to be displayed different so that they are clear, easy to understand and won’t be misinterpreted.
Acknowledging the fact that many stakeholders have entirely conflicting requirements of what should and shouldn't be shown, we can only offer to show the superset of all information all users ever need to see. That means, there will always be some information on any given screen that is somewhat redundant to some users. This will suck less once we get used to the look and feel.
florianm
commented
4 years ago 
Feedback from Amy:
Getting rid of duplicates
Displaying cons listings
Acknowledging the fact that many stakeholders have entirely conflicting requirements of what should and shouldn't be shown, we can only offer to show the superset of all information all users ever need to see. That means, there will always be some information on any given screen that is somewhat redundant to some users. This will suck less once we get used to the look and feel.
@florianm to visit Amy for UX feedback.