ClinEpi: Disable downloads for "merged" PERCH study

[danicahelb]

(this request comes after https://redmine.apidb.org/issues/51835)

The PERCH study will be released as 7 separate studies representing each study site, as well as a "merged" version that contains data from all study sites. This is because each site wants to manage data access requests for their own site separately

The "merged" PERCH study -- "PERCH Case Control" -- will need to have its downloads disabled.

Option 1 (preferred):

• Remove all links to download data (both for the subset and for the full dataset) (set build number 999 in presenters for removing the full files))

• Add custom verbiage: PERCH data from each country needs to be requested and downloaded separately. Please visit the PERCH Case Control dataset for each individual country to request access to data from that country.

Option 2 (not preferred):

• Gray out the download tab

[dmfalke]

I think we should be able to do option 1. We could either hard code something on the front end to show this for the merged study, or we could add yet another attribute to the dataset record with the desired verbiage. I'm less keen on hard coding, for what it's worth.

[danicahelb]

@dmfalke would the attribute to the dataset record be in the ClinEpiDB.xml file?

i'd also prefer to not hard code this

[aurreco-uga]

It is possible this will be needed in other studies that represent a set of member studies. so i agree this should be another property in presenters: "noDownloads" with some optional verbiage. (Though the custom verbiage proposed doesn't make sense currently until we release the member studies.)

This mega PERCH study seems to be the way to deal with the "project page" request from sheena years ago, for the SCORE studies.. which led t a working group https://veupathdb.atlassian.net/wiki/spaces/WG/pages/11698191/Project+Pages.

[danicahelb]

Project pages are a bit different...

The PERCH study is a single study that we’ve artificially broken up into smaller studies by country only because each of the study sites wanted to independently control access to their site’s data and also have different access restrictions.

Project pages, have been requested for studies like SCORE and VIDA, which would encompass separate studies with different methodologies and purposes that make up the project. The studies in a project were conducted by the same research team who sought to learn more about a particular topic (ie, schisto for SCORE and diarrhea for VIDA). Studies split into two datasets using same platform because they were logically two experiments

But perhaps the project page can still deal with situations like PERCH, we would just have to be very clear with the verbiage that PERCH study sites all used the same methodologies and collected the same data, while other projects such as India ICEMR did NOT use the same methodology and did NOT collect the same data

[dmfalke]

@dmfalke would the attribute to the dataset record be in the ClinEpiDB.xml file?

i'd also prefer to not hard code this

Sorry for the late response. Yes, this would be set in that file. We'd also have to update the WDK model to make it a record attribute, etc.

[dmfalke]

I'm planning to begin work on this, but I see that this is currently has the status "Backlog". @danicahelb should I wait on starting work on this? I think it will take a less than a week to complete.