We are happy to announce that v6.1 is ready for download! As always, it has new features, improvements and bug fixes selected based on feedback from many of our current adopters.
New features highlights:
Version | Download |
---|---|
Enterprise | Email contact@openspecimen.org |
Community | Post any installation related questions on forums.openspecimen.org |
Software/Hardware requirements
Review this page before attempting to upgrade for any changes: Software/Hardware Requirements.
From v6.1, you can create a new user type called 'Contact' to restrict OpenSpecimen access. These users will not receive login credentials and system email notifications. But, they will be listed under some user drop-downs e.g. PI, coordinator, nurses etc.
This feature has been introduced to remove unwanted users without deleting the user associated data.
For more details refer: User management
Based on feedback, below enhancements are implemented in 'Dropdown Manager'. The user will be able to -
For more details refer: Dropdown Manager
OpenSpecimen now support semicolon separated files for bulk import of data in addition to comma separated files. This is useful for files being imported from external devices which might be outputting data in different formats.
Admins can export container types in bulk which can be used to import into another OpenSpecimen server. This is useful when container types are set up on test server and have to be moved to production server.
The exported file can be used as is to import using bulk operations into another OpenSpecimen instance.
Below are reports which are available as saved queries when you install v6.1:
Super admins can now configure one or more identity providers(LDAP or SAML based) to authenticate users in OpenSpecimen via UI.
For more details, refer to Configuring Identity Providers.
OpenSpecimen can now handle the repeating instruments(forms) of REDCap. Repeating instruments are forms for which users can add multiple records.
Admins can now exclude part of the instrument from syncing with OpenSpecimen. For more details, refer to the section participant mapping in 'Participant mapping, matching and merging'