Releases: ImperialCollegeLondon/Faraday-liionsden
Releases · ImperialCollegeLondon/Faraday-liionsden
v0.4.1
What's Changed
- Update pre-commit hooks by @github-actions in #257
- update dev requirements and pre-commit by @dandavies99 in #259
- Change head name by @RuiheLi in #264
- Bump django from 4.1.3 to 4.1.7 by @dependabot in #261
- Restrict dropdown choices by @dandavies99 in #258
- Dev docs by @dandavies99 in #262
- Bump cryptography from 38.0.3 to 39.0.1 by @dependabot in #265
- Bump certifi from 2022.6.15 to 2022.12.7 by @dependabot in #266
- Update pre-commit hooks by @github-actions in #267
- Bump django from 4.1.7 to 4.1.9 by @dependabot in #268
- Security Alerts Update by @AdrianDAlessandro in #269
New Contributors
- @RuiheLi made their first contribution in #264
- @dependabot made their first contribution in #261
Full Changelog: v0.4...v0.4.1
v0.4
What's Changed
Feature changes
- Refine which fields are mandatory and default values of those by @dandavies99 in #247
- Improve behaviour of formsets when invalid or missing fields are submitted by @dandavies99 in #250
- Tidy the parsing workflow, make use of column mappings and add a diagram showing the overall parsing workflow by @dandavies99 in #253
- Allow .txt/.csv Maccor files to be parsed by @dandavies99 in #254
Bug fixes
- Prevent saving invalid files by not re-parsing the data file when editing ExperimentDataFile objects by @AdrianDAlessandro in #245
- Move save() out of clean method for ExperimentDataFile by @AdrianDAlessandro in #248
Development changes
- Add config for debugging the django app locally in VS code config by @dandavies99 in #252
-
- Update dummy data to match new database schema for local development by @dandavies99 in #244
Full Changelog: v0.3.0-alpha...v0.4
v0.3.0-alpha
What's Changed
- Improvements to experiment data file
- Link devices directly to experiment so we know which device the data pertains to by @dandavies99 in #227
- Add "time performed" field. This may be generally useful but also so one Experiment can track the performance of one device over time with multiple data files from experiments at different times by @dandavies99 in #228
- Remove polymer field from component as the vast majority of materials in this database are not polymers by @dandavies99 in #232
- Fix the admin site so that files can be downloaded by generating the appropriate SAS token for those links by @dandavies99 in #237
Full Changelog: v0.2.1-alpha...v0.3.0-alpha
v0.2.1-alpha
What's Changed
- Privacy notice has been added in production to comply with college GDPR by @dandavies99 in #234
- Added a link to latest release notes (such as these!) by @dandavies99 in #235
Minor technical changes
- Separate parsers by @dandavies99 in #231
Full Changelog: v0.2.0-alpha...v0.2.1-alpha
v0.2.0-alpha
What's Changed
Major changes
- Modify the infrastructure setup to make use of the terraform web app configuration guide, including use of Azurite as in the django azure demo repository by @dandavies99 in #203
- Add two new optional fields to the ExperimentDataFile by @dandavies99 in #215
- Make the name field mandatory and unique for most of the key models by @AdrianDAlessandro in #224
- Add more fields to Experiment model by @AdrianDAlessandro in #213
Plotting
- Add simple plotting capability by @dandavies99 in #197
Improvements to Parsers
- Handle empty data files correctly for Biologic by @CWestICL in #192
- Improve header size detection to deal with invalid files @dandavies99 in #205
- Improve form behaviour when an unsupported file type upload is attempted @dandavies99 in #208
- Allow experiment page to be displayed when it has unparsed data files by @dandavies99 in #209
Minor changes
- use replace method for encoding errors by @dandavies99 in #163
- migrate to flexible azure server by @dandavies99 in #164
- fix typo DATABASES by @dandavies99 in #166
- PDF file storage in azure by @dandavies99 in #168
- add development warning to homepage by @dandavies99 in #176
- add azure and urllib logging by @dandavies99 in #198
- Update gitignore for terraform state files by @dandavies99 in #206
- Add pip-tools to development requirements by @AdrianDAlessandro in #207
- Added .gitattribute file to fix local Docker container build on windows by @CWestICL in #212
- update cryptography and pillow by @dandavies99 in #214
- Fix data view by @dandavies99 in #216
- Compound form auto mass by @CWestICL in #220
New Contributors
- @CWestICL made their first contribution in #192
- @AdrianDAlessandro made their first contribution in #207
Full Changelog: v0.1.0-alpha...v0.2.0-alpha
First release
This is the first release of the Liionsden platform. The key feature milestones are as follows:
Frontend web interface
- There is a web interface to add various entities to the database, including their metadata:
- device (i.e. cell, module, pack...) specifications including constituent components made up of compounds
- batches of devices of a particular device specification
- experiments in which devices are measured
- equipment that is used in experiments to measure devices
- It is possible to search through the above data, filtering on specific properties of the entities in the database.
- It is possible to upload data files in Biologic or Maccor file formats. These are automatically parsed and the data is saved.
- The frontend web interface makes use of bootstrap.
Backend features
- An Azure storage backend is used for saving and retrieving media files, including the implementation of SAS tokens to retrieve files from a private container.
- An object-level permission system is implemented, ensuring that contributors are able to view/edit/delete only those entities in the database that they should be able to perform those actions on.
- Users are granted specific permissions based on their role.
Next steps
Features that have not been implemented yet, which should probably be worked on next:
- User registration process, including e-mail verification and password reset process.
- Wider implementation of parsers: (i) testing current two parsers on different types of raw data file to ensure they are robust, (ii) writing of further parsers to take raw data files from different instruments.