Skip to content

Polling System developed for the Institute for Ascertaining Scientific Consensus (IASC)

License

Notifications You must be signed in to change notification settings

DurhamARC/IASCPolls

Repository files navigation

IASCPolls

Unit Tests codecov.io License: MIT Code style: black DOI: 10.5281/zenodo.8155054

Polling System developed for the Institute for Ascertaining Scientific Consensus (IASC). This platform provides a tailored architecture for surveying consensus across the scientific community, and is hosted at https://iasc.awh.durham.ac.uk/

Durham University Project Team

Project Member Contact address Role Unit
Dr. Samantha Finnigan samantha.finnigan@dur.ac.uk Research Software Engineer (RSE) Advanced Research Computing
Joanne Sheppard joanne.r.sheppard@dur.ac.uk Research Software Engineer (RSE) Advanced Research Computing
Prof. Peter Vickers peter.vickers@dur.ac.uk IASC Principal Investigator Department of Philosophy

Background

Humanity needs a way to pool scientific community opinion quickly and efficiently on a given statement of interest. This should be on a very large scale, such that one can have confidence that the result reflects international scientific opinion. For this pilot project (2022-23), Peter Vickers has built a network of 30+ academic institutions around the world. Personal, one-to-one emails are to be sent locally to all relevant scientists at those institutions, asking for a yes/no answer to a given question. The scientist answers by hitting a button embedded in the email, and confirming the response in a second step. Each scientist on our list should have one vote only, and nobody else gets to vote. Voting should be anonymous, with any 'token' linking the scientist to their vote being destroyed after voting. Votes should be tagged to academic department, and institution, for subsequent data analysis. Originally the project was set up with Word, Excel, and Microsoft Forms, but several problems were encountered; tailored architecture is needed.

Getting Started

This project is developed in Python Django and React.

Run Locally

There are some prerequisites to be aware of: please see Dependencies for more information.

The django development server can be run using the command:

python manage.py runserver

Linting

The Black code style is used to lint this repository on-push. Set up a pre-commit hook to ensure that any code you push is passing this code style or Linting may fail for your commit. The .pre-commit-config.yaml file contains the configuration for this. You need to tell Git to run it with the following command:

pre-commit install

If you see command not found: pre-commit, you need to first install the pre-commit framework.

You can also run black manually by installing the python module and then python -m black ./src.

Contributing

Please feel free to comment on and create issues. When creating an issue, please use the correct issue template, e.g. for Bug Reports or Feature Requests.

main Branch

Protected and should only be pushed to via pull requests. Should be considered stable and a representation of production code.

devel Branch

Should be considered fragile, code should compile and run but features may be prone to errors.

feature Branches

Feature branches should be created from the main and devel branches to track commits per feature being worked on. External developers should fork the repository and add their commits to a Pull Request. This follows the "github-flow" model of branching.

release Branch

Pushing to the release branch triggers the CI/CD workflow to build the Docker images and upload them to the DurhamARC DockerHub repositories, then release to Azure and the backend servers. The release branch is protected and can only be pushed to by authorized members.

The release branch is managed by rebasing on top of the main branch and creating a tag. For example:

$ git checkout release
$ git rebase main
$ git tag -a v1.x -m "Release v1.x"
$ git push origin release v1.x
$ git checkout main

Built With

We are using the following frameworks and tools to develop this software:

A CI/CD pipeline is used to test and release this software, using GitHub Actions and Azure Pipelines.

License

This work is licensed under the MIT License, a permissive license which allows Commercial use, Modification, and Distribution, but does not admit liability or warranty for use of this code.

Acknowledgements

This project was supported by the Durham University Seedcorn project fund, Durham University Department of Philosophy, and the Centre for Humanities Engaging Science and Society (CHESS).

Citation

Please cite the codebase for this work if you use or reference it in academic publications:

APA

Mitchell Finnigan, S., Sheppard, J., & Vickers, P. (2023). IASCPolls: The Institute for Ascertaining Scientific Consensus Polling Platform (Version 1.0) [Computer software]. https://doi.org/10.5281/zenodo.8155054

BibTeX

@software{
    Mitchell_Finnigan_IASCPolls_The_Institute_2023,
    author = {Mitchell Finnigan, Samantha and Sheppard, Joanne and Vickers, Peter},
    doi = {10.5281/zenodo.8155054},
    license = {MIT},
    month = jul,
    title = {{IASCPolls: The Institute for Ascertaining Scientific Consensus Polling Platform}},
    url = {https://github.com/DurhamARC/IASCPolls},
    version = {1.0},
    year = {2023}
}

About

Polling System developed for the Institute for Ascertaining Scientific Consensus (IASC)

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors 3

  •  
  •  
  •