v28

Hopefully fixing Elixir scope.

v27

• Fix Elixir login

v26

• Updates to requirements (versions)
• New tests (mainly import)
• Code style changes (pylint, flake etc)
• Bug fixes

Note: Elixir login does not work, use v27 instead

v25

• Google login and analytics removed
• Peewee updated to latest version
• Changed error handling, giving more useful http responses
• Bugfixes

v24

Bugfixes

• Handle exceptions for non-existing genes.
• Make sure account is added to database when giving consent.
• Update temporary links to support version numbers.

v23

General

• Database migrated from mysql and mongodb to postgresql
  • New database schemas
• Import scripts for datasets and references to the new database
• Support for registered access for Dataset VCF files
• Simplified setup for development enviroment
• Beacon migrated to "external" elixir beacon
• Beacon UI changes
• Target python version is now 3.6
• A lof of bug fixes

Browser

• Browser migrated to postgresql
• Browser UI changes, e.g. dynamic updates to number of shown variants
• Tests for most of the browser backend
• Support for showing the same variant in other datasets on the browser variant page
• Download will now download the visible variants, not all variants for the gene/region/etc
• A lof of bug fixes

v22

Intended to be the last update before postgres.

• Error management added for a few cases, preventing multiple exceptions
  • e.g. dataset lookup
• Fix of a spelling error
• Update to backup script

v21

• Fix for the population frequencies display box in the variant display. Now the frontend won't crash in case the key doesn't exist in the db entry.
• Add dbsnp rsid values for variants when there's no rsid in the db entry.
• Update the law text to mention GDPR instead of PUL.

v20

• correct IP in logs
• link to protein atlas in browser

v19

• Integrated browser

  Browser moved from beeing an external service to be inside the portal.

• Better reload of cache upon updated version

  Hopefully the webbrowser will use the new resources now when making a new deployment to the infrastructure.

• Show future versions to people that know the URL.

  This is esp. for reviewers and editors that need to be able to view the site before the data/analysis is published.