search

VEuPathDB / EdaNewIssues

0 stars 0 forks source link

Project-based site configuration with entity-centric preferences #598

Open asizemore opened 1 year ago

asizemore commented 1 year ago

Dropping a thought i had here before it gets lost.

Mbio and clinepi have different expectations on what their users will want from the site, which leads to different preferences on what lives where. For example, we've had debates about the entity diagram - it's crucial for clinepi but not for mbio. We wouldn't want to hardcode these sort of preferences by project in web-eda, but maybe we could have an "entity-centric" flag that turns on many of the helpful views of entities such as the entity diagram.

We'd need a longer list of differences that we'd want to have between the two sites before we implement this, but just an option for having different flavors of our beloved eda.

dmfalke commented 1 year ago

The way we've approached this, thus far, is with props for the root-level component. It is up to the "housing" application to determine how to set these values (environment variables in local dev server, and conifer variables in managed websites).

Are you thinking we might want to have study-specific flags, as well?

asizemore commented 1 year ago

A new env var is what i was envisioning. As we figure out how mbio and clinepi should differ (and soon genomics!) we could just use this flag to turn different parts of the site on and off.

Nothing groundbreaking here, just trying to start laying groundwork for a path forward for allowing the mbio and clinepi edas to differ just a bit :)

Oh, and this is also a place for us to list things that would be different between the two! The entity diagram is one, but i just remembered the showMissingness option is another.