You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
API: Modified in v0.0.4-dev the candidate instrument data format returned by a GET request or provided as the body of a PUT/PATCH request. The values of all fields are now defined by the Data key instead of $InstrumentName (PR [api] Modify YAML schema so that Swagger Codegen PHP Client works #7857)
Notes For Developers
Require jsodc comments to have correct @return and @param values in javascript (PR Jsdoc update #8266)
Source the SQL/Release_patches/24.1_To_25.0_upgrade.sql SQL file into your database.
Run the following scripts:
php tools/configuration_check.php This script is used to validate the configuration of LORIS. It checks configuration settings and server paths to make sure that the application and underlying architecture are set up to allow LORIS to run properly.
php tools/single_use/migrate_instrument_permissions.php This script migrates instrument permissions from the config.xml to the new database tables that now store them.
php tools/single_use/update_violations_resolved_hashes.sql.php This script is intended for a one-time use only to update the hasing of the violations_resolved table. Not doing so will result in duplication of data in the violations_resolved tale when users update a resolution status for a violation.
Run make all from the LORIS root directory.
OPTIONAL: Run any cleanup patches in SQL/Archive/25.0/Cleanup/
OPTIONAL: Remove the <instrumentPermissions> tag from your config.xml which is no longer used after running the migration script.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What's Changed
New Contributors
flag
table appears to be unused #8278Full Changelog: v24.1.4...v25.0.0
Notes For Existing Projects
Data
key instead of$InstrumentName
(PR [api] Modify YAML schema so that Swagger Codegen PHP Client works #7857)Notes For Developers
@return
and@param
values in javascript (PR Jsdoc update #8266)Upgrade Process
24.1.x to 25
Get the 25.0.0 source code
Source the
SQL/Release_patches/24.1_To_25.0_upgrade.sql
SQL file into your database.Run the following scripts:
php tools/configuration_check.php
This script is used to validate the configuration of LORIS. It checks configuration settings and server paths to make sure that the application and underlying architecture are set up to allow LORIS to run properly.
php tools/single_use/migrate_instrument_permissions.php
This script migrates instrument permissions from the config.xml to the new database tables that now store them.
php tools/single_use/update_violations_resolved_hashes.sql.php
This script is intended for a one-time use only to update the hasing of the violations_resolved table. Not doing so will result in duplication of data in the
violations_resolved
tale when users update a resolution status for a violation.Run
make all
from the LORIS root directory.OPTIONAL: Run any cleanup patches in
SQL/Archive/25.0/Cleanup/
OPTIONAL: Remove the
<instrumentPermissions>
tag from your config.xml which is no longer used after running the migration script.This discussion was created from the release LORIS Release v25.0.0.
Beta Was this translation helpful? Give feedback.
All reactions