You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 9
Next »
Release 1.7.12 is in development at the moment. Below are the features planned for this release. This is an evolving document and will change as the release develops.
Beta 1 - Release August 1, 2019 - Location of WAR, VMWare and Source code http://www.i2b2.org/software/1712beta.html
Beta 2 - Release August 15, 2019
| Category | Feature | Description | Screenshot |
|---|
| Data | ACT Ontology | Beta 1 - In the Release_1-7/NewInstall/Metadata/db.properties file change the db.project from demo to act. Than ran the ant script against create_metadata_tables_release_1-7 and db_metadata_load_data | |
| Core | Easier Install | Beta 1 - - If using the prebuilt WAR file: Copy the .war file into a wildfly 14 or 16 instance in the /opt/wildfly-VERSION-Final/standalone/deployments/ folder.
- If making WAR file: Run in the edu.harvard.i2b2.server-common folder
ant clean dist war
Copy the i2b2.war from the dist folder to /opt/wildfly-VERSION-Final/standalone/deployments/ folder. - Run the data build for all the cell (PM, HIVE, ONT and CRC) . In the Hive there is a new table called HIVE_CELL_PARAM which contains all the previous XML and properties file.
- Modify the *-ds.xml in the deployment folder to point to the database
|
|
| Core | More authentication protocol support (okta, NTLM v2) | Beta 1 - Support for NTLM2 is supported. Instead of using authentication_method - NTML use NTML2 Beta 2 - Support for OKTA |
|
| Data | Totalnum scripts | Beta 1 - In the Release_1-7/NewInstall/Metadata/ ran the ant script ant -f data_build.xml create_metadata_tables_release_1-7 - This will create the stored procedures - POSTGRESQL : ant -f data_build.xml db_metadata_run_total_count_postgresql
- ORACLE : ant -f data_build.xml db_metadata_run_total_count_oracle
- SQL SERVER : ant -f data_build.xml db_metadata_run_total_count_sqlserver
|
|
| Webclient & Core | Enhanced Find Terms | Beta 2 - Find terms gives a sense of the hierarchy, and terms that are children of other search results are not returned. | |
| Webclient | Improved Maximized Left Pane | Beta 1 - In maximized mode, the left pane now makes all tabs accessible. | |
| Webclient | Larger Query Result Panel |
|
|
| Core | Bugfixes and refactoring |
|
|
| Core | RedCap | Beta 2 - Project Params (PM_PROJECT_PARAM) | Name | Value | Description |
|---|
| REDCP_TOKEN | (7B42348B7C51123432048B51EAA) | Required: Get the API Key from Redcap. Logon to Redcap on the right side under applications click API. Than select Generate token, and use this token for the value for the key. | | REDCAP_SURVEY_FORM | (profile) | Required: This is the name of the Data Collection Instruments to associate this project with, in this example it is set to the 'Profile'
| | REDCAP_ONTOLOGY_REFRESH | Y | Optional, Defaults to Y
Y - Every time a form is submitted the i2b2 metadata ontology get regenerated N - Do Not regenerate the metadata ontology. NOTE: When first setting up the i2b2/redcap this needs to be set to Y at least one or the ontology will not be created. | | REDCAP_ROOT_ONTOLOGY | \REDCAP\ | Optional, Defaults to \REDCAP\
What the root ontology is | | REDCAP_ONTOLOGY_FORMAT | tree | Optional, Defaults to tree
How the ontology will be created tree - All enumerated values, Yes/No will be children on the ontology popup - All enumerated values, Yes/No will displayed on a popup value when dragged to the query panel The only exception is items with checkbox, which will always be a popup | | RECAP_PROTECTED_ROLE | DATA_PROT | Optional, Defaults to DATA_PROT
If this redcap form has the identified value set to true, than this ontology will be protected and only users with the following i2b2 access role will be able to access it. |
On the redcap side, set the Data Entry Trigger, it is under Project Setup → in Enable optional modules and customizations, select Additional customizations → Data Entry Trigger, and enter: http://{i2b2 url}/i2b2/services/QueryToolService/redcapPush |
