@MauraBeaton: could you put the topic below on the agenda for next Steering Workgroup meeting?
@Patrick_Ryan and me have been working some more on the new ohdsi-studies organization in GitHub . We would like to propose the following:
-
Each OHDSI study should have its own repo in this new GitHub organization. Anyone can request a study repo, and the study lead will become the repo admin, therefore having the rights to do whatever she wants within the repo. We do not restrict what people put in the repo. If they want to post only the protocol and the json, that is fine. Some people may post the study R package.
-
We would require each repo to have a README file, and the start of this README file should conform to a standard template. An example study that adheres to this template is here.
-
The README files would be (automatically) scanned to generate a table that will replace the current OHDSI research studies page. The table can be filtered, for example to show only EHDEN studies or only prediction studies.
The advantages over the current way of working are:
- Avoiding the mess that is StudyProtocolSandbox. Each study has a clear commit log and issue tracker dedicated to that study.
- Each study will have a stable URL that can be referenced for example in papers.
- Having the meta-data in the README file means the study lead can easily update information on the study, hopefully leading to less out-of-date-information on the OHDSI studies.
Another idea is to have a prespecified subfolder in each study repo where the results Shiny app can live. This would replace the current ShinyDeploy repo as a means to deploy study Shiny apps. However, we still have to figure out the mechanics for that.