Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need the latest/correct document for setup #6

Closed
rachbhatnagar opened this issue May 30, 2022 · 4 comments
Closed

Need the latest/correct document for setup #6

rachbhatnagar opened this issue May 30, 2022 · 4 comments

Comments

@rachbhatnagar
Copy link

Hi @erikvw,

Need your help to get the correct requirement file. In the repo, the requirements/stable.txt is not present. Should I have to take requirements.old/stable.txt or any other file?

Also, this command I got from the edc/docs/README.rst. Is this the correct document for setup?

Let me know.

I really appreciate any help you can provide.

Best Regards,
Rachit

@erikvw
Copy link
Member

erikvw commented May 31, 2022

Hi @rachbhatnagar. We changed the build for most, and soon all edc modules, to drop the use of a requirements file. Requirements are pinned in the setup.cfg. We are also releasing off the main branch now.

@rachbhatnagar
Copy link
Author

rachbhatnagar commented May 31, 2022 via email

@rachbhatnagar rachbhatnagar changed the title requirements/stable.txt not found Need the latest/correct document for setup Jun 1, 2022
@erikvw
Copy link
Member

erikvw commented Jun 4, 2022

Hi @rachbhatnagar ... note that these modules "support" a clinical trial system. The modules by themselves don't really do anything. You need to build your CRF models and write the validation checks. Check the readme for some of the projects that use the edc modules. The more recent the project the better.

We test on ubuntu-latest, mysql latest, so these are fine.

@vagarwal77
Copy link

@erikvw I am also interested to setup edc for multiple studies.
What i would like to do is -

  1. setup and deploy edc modules as a service
  2. Build study A, study B, study C of different Oncology on the same deployment without any code changes.
    Current commercialized EDC like Medidata use XML ODM for study configuration setup, Veeva use json config to build study. I am looking for a similar solution. Based upon your above comments, looks like, every time we need a new study, we need to build new Django models and need to deploy separately, which is kind of against todays SaaS model.

I may understood readme or your comments incorrectly so, please suggest or i am in EST time zone and would love to hop on a call with you.

@erikvw erikvw closed this as completed Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants