Summary of my thoughts on how we can get this going can be found here:
https://docs.google.com/document/d/14R72-ev7Toh6iCN2de0FCOm5OrOWY33w5qV8LGLUgZM/edit?usp=sharing
Locate Database Code - https://github.com/openworm/movement_cloud.
Locate or acquire a copy of MySQL database archive of worm movement metadata - probably via Dr. Andre Brown, or some forgotten work archive in Lee Chee Wai’s possession.
This database or a subset should be probably curated somewhere moving forward.
Framework is Django, and was previously deployed on AWS.
Deployment steps should be laid out again, and documented. E.g. any self-signed certificates etc …
This information is probably best facilitated by Michael Currie.
The framework’s access to Zenodo (for the actual movement data) should be reviewed and tested.
Combination of Chee Wai, Michael, and Andre.
> Advanced:
Modernize the Django and front-end code.
Previous backend database access was ad-hoc using basic Django operations, and could be modernized to use a cleaner REST framework implementation.
Nicer interface alternatives to Data Tables, Crossfilter, and other major front-end features may be available in more modern interfaces implemented in React, and could be investigated.
Deployment.
Prior deployment dispensed with any need to move from a debug/development footing for Django because the data is open, public, and the interface was read-only.
Maybe it would be nice to modernize the deployment by putting the Django implementation in production mode, while using gunicorn as its WSGI layer, behind an NGinx web service. This allows us to start the web service as a daemon, with logging and other facilities cleanly built into the system.
Previously each time we restarted the service, we had to invoke python manage.py runserver in background, no hangup mode, with standard out and standard error directed to a log file we specify.
User-Standalone Deployment.
We could make the framework installable as a local service to users, so a centralized server would not be necessary and save the Foundation some subscription money.
Instead of the full database, we could provide a smaller but meaningful subset.
We will need to ensure that the Zenodo data can be accessed by members of the public via this setup.
Summary of my thoughts on how we can get this going can be found here:
https://docs.google.com/document/d/14R72-ev7Toh6iCN2de0FCOm5OrOWY33w5qV8LGLUgZM/edit?usp=sharing
> Advanced: