Giter Club home page Giter Club logo

civic-client's People

Contributors

acoffman avatar agraubert avatar ahwagner avatar amberzw avatar dependabot[bot] avatar ebarnell avatar jmcmichael avatar kkrysiak avatar lsheta avatar malachig avatar mrjosh-zz avatar nspies13 avatar obigriffith avatar susannasiebert avatar tmooney avatar yang-yangfeng avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

civic-client's Issues

Include additional values on the evidence statement tables

When I select a particular variant (e.g. BRAF V600E) I find myself looking at the table of evidence statements and wondering what their evidence types are (i.e. predictive, prognostic, or diagnostic) and what the evidence directions (i.e. supports vs does not support) of these are.

Actually showing these values would take up way too much space. But they are simple categorical values just like the 'level' (A, B, C, D). I'm wondering if we could include them in a compact way (perhaps as colored icons/symbols. For example,

Evidence type:
T = therapeutic/predictive
D = diagnostic
P = prognostic

Evidence direction
'+' = Support
'-' = Does not support

Clinical significance
green = drug sensitivity (predictive) or good outcome (prognostic) or positive (diagnostic)
red = drug resistance (predictive) or poor outcome (prognostic) or negative (diagnostic)

Clinical significance is harder because it is not so much of a simple categorical variable. In that case maybe you need the full description... Or we need to come up with more tightly defined categories here. Or we rely on synthesizing this in the clinical summary.

This issue seems to be related to #36 (Adding more information to the drug column)

Fields in the Add Evidence page should be separated by required and not-required.

Requiring that each field is filled is a major burden for a curator. Many of these can be back-filled by us post-curation. Required fields should be: Gene Name (Not Entrez ID), Variant Name, Disease (Not DOID), Source (PMID is greatly appreciated but not required), Evidence Summary, Evidence Type, Evidence Level, Clinical Significance, Evidence Direction, Evidence Rating, Comments.

We also need to discuss these... Keeping the barrier to entry as low as possible is my personal priority #-1, but maybe @obigriffith @malachig may feel differently.

Reorder the Add Evidence Statment form items

The Add Evidence Statement form doesn't have a very logical flow at the moment from the standpoint of a curator (in my opinion).

I think a better flow would go as follows:
-Entrez Gene ID (Gene-based data)
-Variant Name (Variant-based data)
-Variant Origin
-Disease Ontology ID (Disease)
-Evidence Summary (Evidence info)
-PubMed ID
-Evidence Level (Evidence Descriptors)
-Evidence Type
-Evidence Direction
-Clinical Significance
-Evidence Rating

should ratings be calculated in aggregate or as a discrete value per record?

Currently, we only accept the original curator's trust rating.

It would be great if this could happen without having to click on "edit evidence statement" but still be tracked in the activity of an evidence statement. Otherwise you have to submit a comment about your evidence statement change which may deter users that just want to vote.

Reorder evidence summary items

I've been thinking more about this. I already suggested some reorders that took effect and were an improvement. But, I am wondering if the following would be even better.
Left column: Evidence Level, Evidence Direction, Evidence Type, Clinical Significance.
Then, as you read down the items you sort of get a sentence/story. Like: "Clinical" evidence "Supports" a "Predictive" association with "Sensitivity".

The downside is that Drug and Clinical Significance wouldn't appear together. That has a certain logic to it as well. We could at least line them up left to right.

So, for the right column we could have: Citation, Rating, Disease, Drug.

That has the advantage of putting Citation at the top to bring attention to the source more, followed by rating which is really a rating of that publication. Drug is also commonly N/A for non-predictive evidence so I like having it at the bottom.

Thoughts?

Search for Variants in Quick Event Search

Requiring the gene before the variant in quick event search is a bit frustrating, and may lead people to believe a variant is missing. Typing 'V600E' should bring up BRAF V600E. And G12D should drop down all the RAS's with G12 entries.

Add a page for the FAQ

I've been stabbing around in the dark for a while and can't figure how to make a new tab/page on the home page. The FAQ file is here: /civic-client/src/app/pages/faq.tpl.html

Set an intuitive order for tables of evidence statements

It is not obvious how these are sorted now. For example, if we select BRAF V600E, there are currently 31 evidence statements. Not sure what order these are in now. But it would be awesome if they were ordered by 'Level' (A, B, C, D) and then within statements of the same level by 'Rating' (highest rating first). Thoughts?

Adding more information to the Drug column

In order to display type, direction and significance in the evidence table, it may work to color-code the drug column.

Sensitvity could cause the drug text to be green, resistance red.

Statements without drugs can print evidence type, with Diagnostic in Blue and Prognostic in Purple.

Then the Supports/Refutes could be represented as an arrow?? I don't know if I like this.

Licensing

We need to add links and explanations of the CC license we've selected on the downloads page and in the page footer.

Change "Login" text to a link

In all the talk pages under comments it says "Login to post comments." It would be great if the Login was actually a link to the login screen.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.