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

Remove stoplights from structural data #68

Closed
jchodera opened this issue Apr 18, 2020 · 7 comments · Fixed by #70
Closed

Remove stoplights from structural data #68

jchodera opened this issue Apr 18, 2020 · 7 comments · Fixed by #70
Labels
help wanted Seeking community input for ways to fix this

Comments

@jchodera
Copy link
Contributor

We need to remove the stoplights from structural data. They are entirely misleading as to the quality of the structures and their utility for different purposes.

Publication status has no impact on structure quality. If we want to communicate publication status as presence of preprint or published version, we should simply come up with an icon that is displayed for preprint and published that shows up if these are available and absent if they are not.

This is going to cause active harm to the community if we keep these.

The appropriate annotation data should instead be pulled from the Coronavirus Structural Task Force, but we shouldn't wait for the implementation of that to strip out the stoplight nonsense.

@Lnaden
Copy link
Collaborator

Lnaden commented Apr 20, 2020

I'm going to add some additional information about this issue here:

This is in response to the feature added in #61 . I added this comment to that PR after it was closed, but I'll post again here so people don't have to jump back and forth:

The RYG system is to indicate whether or not a datum has undergone an official, regulated, peer review process at a glance. We're trying to remain as neutral as we can on the mater and are simply accepting data, leaving mechanisms such as issues and project boards for the community and teams to have discussions on the data. If need be, we transfer the discussions to another public facing system if discussing through issues isn't suitable. As the reviews come in and consensus is reached from the community based on both usefulness and quality, we can take advantage of the rating system or some equivalent to indicate what the top data are.

We are going to be keeping an ear open for community feedback on the subject though, and if people do not like this system, we can work on a replacement.

I'm also going to tag a few people here who have also expressed opinions about this in meetings:
@eriklindahl, Rommie Amaro (I can't find a GitHub presence, will email.), @mojtabah (point of contact in Head-Gordon lab)

@Lnaden Lnaden added the help wanted Seeking community input for ways to fix this label Apr 20, 2020
@jchodera
Copy link
Contributor Author

@Lnaden: Is there a reason adding icons with links to preprint and/or journal articles does not accomplish the same task while not misleading the reader about the quality of structural data?

@jchodera
Copy link
Contributor Author

For example here is a very simple visual iconography you can use that accomplishes the task of clearly indicating preprint/publication status without being actively harmfully misleading about structure quality (from here):
image

@Lnaden
Copy link
Collaborator

Lnaden commented Apr 20, 2020

Sure, we could do that instead. I can use a few of the Open Access icons instead. Would that be acceptable to the current scheme?

@jchodera
Copy link
Contributor Author

Anything would be better than stoplights right now.
The graphic above is CC-BY, so could also be (re)used if desired (if you have attribution somewhere).

@Lnaden
Copy link
Collaborator

Lnaden commented Apr 22, 2020

the new system is in and has 0 ambiguity in my opinion

@jchodera
Copy link
Contributor Author

Huge improvement---thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Seeking community input for ways to fix this
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants