Giter Club home page Giter Club logo

clinepiwebsite's Introduction

ClinEpiWebsite

Frontend pages (js, images, css, html) that add or modify EbrWebsiteCommmon and WDKClient, used in ClinEpiDB.org.

Local Development

First, configure your local development environment by adding a .env file in ClinEpiWebsite/Site. (We have provided a sample config in .env.sample.)

Next, install dependencies from npm:

yarn install

Finally, start the dev server:

yarn start

clinepiwebsite's People

Contributors

dmfalke avatar d-callan avatar ryanrdoherty avatar jtlong3rd avatar aurreco-uga avatar dependabot[bot] avatar github-actions[bot] avatar sheenatomko avatar danicahelb avatar brunkb01 avatar linxu123-git avatar mheiges avatar brlindsay avatar aaronwlsong avatar jbrestel avatar nkittur-uga avatar foxcapades avatar chowington avatar jernestmyers avatar asizemore avatar steve-fischer-200 avatar dmgaldi avatar sweverschulman avatar sak22 avatar rbelnap avatar

Stargazers

Bindu Gajria avatar  avatar

Watchers

 avatar  avatar James Cloos avatar  avatar Daniel Lawson avatar Daniel Beiting avatar  avatar John Iodice avatar Mikkel Christensen avatar jie zheng avatar Stuart Brown avatar Robert Wieck avatar Omar Harb avatar David Starns avatar  avatar  avatar DK avatar Brett avatar Matthieu Barba avatar  avatar Saikou Y Bah avatar  avatar Bindu Gajria avatar  avatar

clinepiwebsite's Issues

Website: Studies menu filter foiled by italic species names

If I want to find "SCORE S. mansoni" by typing into the filter in the Clinepi website's Studies menu, it won't work if I type SCORE S.

I have to type SCORE < because I happen to know there is an italic <i> tag in the study name.

Filtering should strip HTML first.

Pretty sure this is NOT a web-eda ticket - probably website related (don't know which repo). @jtlong3rd or @dmfalke can advise.

Cost is low though.

Change isPublic to be a filterable tag for studies and control release of studies

Right now we have 2 sets of qa sites, qa.clinepidb and qa.restricted.clinepidb. The only difference that I know of is that qa.clinepidb is restricted to show only studies where “isPublic” in the presenters is set to “true”. We don't really need the 2 different versions of the sites, but we do need a way to easily check which studies will be public with a release and which will remain on qa.

Brian suggested that we turn “isPublic” into a tag that we can use to filter on in the study summaries table as a way to check which studies will go out with a release. This would likely require service/client work to make sure all studies appear on the qa site, they are filterable based on the isPublic attribute, and that only those set to isPublic = true are accessible on the live site. However, if we make this change, it will allow us to get rid of qa.restricted.clinepidb.org and simplify things for the Systems and Outreach teams.

As part of this ticket, we could change the name of the annotation "isPublic" to "isReleased" to more clearly differentiate it from the data access level restrictions.

Line plot bug in y-axis range with continuous Y variable

To recreate:
Use the PRISM ICEMR Cohort and create a Line plot
X- axis: Age
Y-axis: Plasmodium asexual stages, by microscopy result
Function: Arithmetic mean (the same issue exists with median and geometric mean)

The plot should use the range of the means to set the Y-axis. However, it seems to be using the range of the raw Y variable data instead. This is problematic because it makes it look like a flat line with no data variation, whereas if you toggle on the log scale for the Y axis or change the default Y-axis range, you can see a strong relationship between age and parasite density.

https://qa.restricted.clinepidb.org/analysis/XhXiciQ
Screen Shot 2022-09-16 at 11 09 05 AM

Data Access Request form not loading correctly on ClinEpiDB live site

To recreate. Try to download a file from SCORE Burundi (https://clinepidb.org/ce/app/workspace/analyses/DS_55fd455f5e/new/download) which has Controlled access. It brings up the data access popup. When I click on the "Submit data access" button, it brings up a screen that says "Loading" but never loads. Refreshing the page brings up the form.

This needs to be fixed so that the data access form loads without needing to refresh the page.

Screen Shot 2022-03-21 at 11 29 51 AM

Screen Shot 2022-03-21 at 11 29 54 AM

Make tabs "sticky"

when the user scrolls down a page, for example the Study details tab, the tabs should always remain visible instead of scrolling out of view. We want the user to be able to "save their place" on the study details tab (for ex, a description of the study arms) so they can come back and refer to it as they are working on their analysis.

currently, the tabs scroll out of view so the user must navigate away from their position on the study details tab in order to navigate to the B&S tab

Sticky footer updates for b57

  • the footer is too tall, please shrink the height of the footer

  • it is not completely clear, in the footer, why all those icons are there. The relevance of the icons is to indicate that ClinEpiDB is part of a larger family of data resources. for a naive user, i am not sure they will understand. i wonder if the footer should make that more obvious.

DIY epi styling / verbiage changes

Discussed in 6/17/2022 EDA UX meeting

Terminology to differentiate official studies from DIY studies:

  • DIY datasets will use the terminology: “User studies”
  • ClinEpi studies will use the terminology: “Curated studies”

Changes needed:

On the “Study summaries” page:

  • Page header should be: Study summaries
  • Add a sub-header for User studies
  • Add a sub-header for Curated studies

On the “My studies” summary page:

  • Page header should be: My user studies

On the “My studies” page for a particular user dataset:

  • Page header should be: My user studies: _My user study name_ (“My user study name” should be in italics, because every time text is editable (like “Analysis name”) it appears in italics)
  • Change Use This Dataset in ClinEpiDB sub-header to Explore in ClinEpiDB (Explore in ClinEpiDB will be a link that takes you to an analysis page for this user study in the EDA)
  • Remove hyperlinked study name under Use This Dataset in ClinEpiDB

On the dropdown menu:
Change Workspace > My studies to Workspace > My User Studies

Bug in release number display for 2 vs 3 releases

We are currently not consistent in which release # and date we display for a study.

  1. For studies with only 1 version, we display the release # and date correctly.
  2. For studies with 2 versions, we display the second release # and date (e.g. Amazonia Brazil shows rel. 21 on 2022-Mar-03, which was the EDA release of the data and not rel.13 which was the original release)
  3. For studies with 3 versions, we display the original release # and date (e.g. GEMS1 Case Control shows rel. 5 on 2018-Dec-13 rather than rel. 14 or 21)

First we need to decide what should be displayed (most recent version, original version, or a list of all versions?), then we need to implement that.

This is minor and can wait

ClinEpi: add “Avg time to decision (days)” statistic to all studies table

see https://redmine.apidb.org/issues/43222

“Avg time to decision (days)” → amount of time between submission and decision to provide access or reject

decision was made to calculate the "avg time" statistic based on history logs (there is no need to take into account information from access requests made prior to the history log system being in place)

The data will come from the end_users table and the new history table.
Initially we thought of a new service endpoint but given that this information will be shown in existing pages:

  • All Studies results table
  • Study page
    Im hoping these will be new attributes/table in the study record xml (SQL)

More details:
avg_time_request_response_days:
1- is days enough granularity? YES (danica slack Jan 31 2021)
2- are we only considering transitions from request to another state? YES (danica slack Jan 31 2021)
----We may also want to consider time to 1st response as an additional stat

favicon.ico folder missing: monorepo?

then the problem seems to be that the repo ClinepiWebsite is missing /images/ClinepiDB/favicon.ico under Site/webapp/
also in MicrobiomeWebsite
Api and Ortho are fine

im thinking we removed those directories by mistake in ClinepiWebsite and MicrobiomeWebsite..
maybe we want to have all in EbrcWebsite but we never got to do it..?

let's wait for dave what was his intention.

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.