v1.8.2

v1.8.2

New features

• Deployment is fully dockerized including backup and migration #521, #527
• PostregSQL version was bumped from 10.1 to 16.4 #529

Fixed bugs

• Access object records real REMS ID when creating by REMS api call #526
• Metaclass conflict causing error during migration is fixed #522

v1.8.1

v1.8.1

Fixed bugs

• Users can change OIDC ID of external contacts #508

v1.8.0

v1.8.0

Remarks

New features

• Dataset Quick form is replaced by a Wizard form for enhanced user experience #433
• New notification feature was added. Users are reminded about upcoming events directly in the interface or/and via email #470, #475
• Entities can be imported directly from user interface. Import in JSON following ELIXIR-LU schema is supported. #438,
• Performance of access request creation endpoint is improved #443
• Scientific metadata are now displayed and editable for dataset #439
• REMS form name is displayed in list of exposures in dataset view and admin view #420
• Code formatter Black was added to CI #446, #383

Fixed bugs

• Project don't get ELU_ACCESSION id when dataset are published #456
• Modifications of Use Restrictions are not saved. #436
• Upon access approval in REMS, DAISY creates 4 access objects for given user #431
• Special subject field in data declaration shows wrong value #408
• Export to XLSX button is visible only to superadmin but this role have insufficient permissions #448
• Upon access approval in REMS, DAISY creates 4 access objects for given user #431
• Use restriction codes are not in standard format #462

v1.7.12

BREAKING CHANGE

All published datasets (exposed via API) are unpublished during migration. A new exposure endpoint needs to be created by administrator with the name and API key and datasets must be exposed manualy by a user belonging to datasteward group.

New features

• Support for multiple publishing endpoints #412.
  • Dataset metadata can be exposed to multiple pre-defined endpoints while using different external access request forms (e.g. REMS).
  • New "endpoint" model keeps API key specific to each endpoint (e.g. data catalog, dashboard app, ...).

Fixed bugs

• Cannot create access object #403

v1.7.11

Changelog

1.7.11

New Features

• minor permission system fix
  • users with EDIT permission can create Access object
  • if an Access object has status "active", it can be edited only by member of daisy-datasteward group

Fixed bugs:

• regular user cannot create access object (403)

v1.7.1

Changelog

1.7.1

BREAKING CHANGE

• update to 1.7.1 requires manual changes in settings.py file for Keycloak integration. See this section for more details.

New Features

• permission system (#397)
  • technical refactoring and test coverage
  • all user permissions are listed on user page
  • display inherited permissions on Dataset permission page
• only data stewards are able to change status of Access object
• bump the python-keycloak version to 2.6.0 and introduce the possibility to have different REALM to retrieve users and for login (#396)

Fixed bugs:

• user uploading document cannot download the document (276)

v1.7.0

Changelog

1.7.0

BREAKING CHANGE

• update to 1.7.0 requires changes Celery config file due to Celery migration to 5.X. See this section for more details.
• support of Python 3.6 was deprecated. Daisy now supports Python 3.9 #362

New Features

• Migration to Python 3.9 #363
• History of Access entity is recorded in audit log #369
• More attributes are displayed for Data Declaration, Document and Contact #354, #336, #355
• Allow attaching arbitrary (scientific) metadata to DAISY entities #294
• Access object can be created programmatically via API #349
• Users can be synchronized from Keycloak database #280, #301
• API supports export of Contract entities #310
• Option to set branding label and color #286
• Exporter has option to export also unpublished records #258
• Small improvements for managing users in django-admin #333, #332

Fixed bugs:

• Auditors cannot upload/delete the document #357
• Removed use restriction length limitation #347 , #340
• Increase the number of possible use restrictions in the daisy Data Declarations. #307
• Increase number of use restrictions in data declarations form #308
• Fixes to importer/exporter #338, #325, #313, #316, #289
• REMS API includes an error message #277
• Edit Document icon does not react on Project page #337
• Minor UI fixes #335, #304, #303, #305,#292
• Used ontologies are now referenced #366

v1.6.0

New Features:

• User model now contains API key #237
• Add support to link external identifier service #227 #206
• Resource Entitlement Management SystemREMS can be integrated to automatically log access in data logbook #226
• Publishing Dataset also publishes related Project and Partner entities #228
• Dataset export contains all related Data Declaration details #194
• End of Data processing events are logged in data logbook #45
• JSON schemas used by importer are stored locally and their version is tracked #254
• Entities can be published immediately after import using --publish-on-import flag #244
• Import of an existing entity can by skipped usin --skip-on-exist flag #282
• Ethics status on cohorts is kept on Cohort entity, not Project #139
• Participants of a contract can be updated #235
• Home organization is not anymore assumed to participate in a contract by default #215
• Enumeration labels were updated for "Use Restriction Rule" #230
• DPIA document can be added as an attachment rather than a fixed (URL) attribute #217
• Same Data Declaration title can be used under different datasets #207
• Bump Django from 2.2.20 to 2.2.24
• Bump django-celery-beat from 1.4.0 to 2.2.0
• Bump django-celery-results from 1.0.4 to 2.0.1
• Bump celery from 4.3.0 to 4.4.7

Fixed bugs:

• Broken project view #266
• Formatting is not preserved for project lay summary #234
• Export to xlsx fails for projects and datasets #233
• Accession number should be unique #142
• Empty use restriction form on data declaration edit form is validated #270

v1.5.0

New Features

• Major update of JSON import and export feature to follow Elixir JSON schemas #198, #199, #203, #216, #195
• Data declaration transfer entity was upgraded to more generic data Logbook #219
• Company roles were removed from contract entity and a comment field was added #218, #215
• Entities Project and Dataset were added to API endpoint #198
• Bump django-debug-toolbar from 1.11 to 1.11.1 #214
• Bump django from 2.2.10 to 2.2.20 #208 , #202, #180

Documentation:

• Update of deployment instructions #181, #179, #151

Bug Fixes:

• Missing placeholders on login page #134, #213
• 500 Internal Server Error when uploading attachment to contract #191
• Field "Has special subjects?" is not recorded correctly #148
• Sorting projects by start date returns "No results" #152
• Datasets and projects api endpoints are not public #205
• Error when building Solr schema #121
• Update solr schema files for docker #201
• Missing public decorator to new api views #209

1.4.0

New features

• superuser can export records into Excel file #163
• new dashboard layout #170
• new demo data #169
• added footer with logos of funding institutions #21
• visual improvements:
• arrows inside calendar #95
• larger modal boxes #161
• more compact editor forms #136
• icons used in dataset declaration's dynamic section #21

Documentation

• Update of README file layout (#129) and including link to demo deployment #158
• Updating link to documentation on About page #155

Bug fixes

• API now exposes only published entities #143