...

• Which method of re-identification protection does your network use? (required configuration, default provided): In 1.22, we obviate the need for user lockout with new features: a greater obfuscation of results,  a more interactive Data Steward Application (DSA), greater obfuscation of results, and other changes, and email audit requests from the DSA to the data steward. Lockout remains on by default. Networks should not need both lockout (method employed in 1.21 and prior) and the new re-identification protections introduced in 1.22. We recommend using the new features and turning lockout off if your network governance allows. (Lockout will be off by default in SHRINE 1.23, and removed in SHRINE 1.24.)
• Network contact information ? (optional configuration): Determine what fields every node should provide via the SHRINE static data service. We created this general-purpose feature to provide contact information for the right person that remote researchers should contact for more information about query results. Networks should agree on key-value pairs to supply for this contact information and any other required information.
• Bot defense values ? (default values provided, optionally configurable): Determine what values to use for Bot Defense for your network, if other than default.

...

• Who should get emails generated by SHRINE's Data Steward Application? (required if not using lockout for re-identification protectionoptional but highly recommended): Find appropriate email addresses for the system administrators and data stewards.
• How will email from the DSA be sent? (required if not using lockout for re-identification protectionoptional but highly recommended): The default configuration assumes localhost is running postfix on port 25 .
• If your network has chosen fields for the SHRINE static data service, what are your local values? (optional, local configuration; see "Network contact information?" above)

Shut Down SHRINE

Before starting the upgrade process, make sure SHRINE's Tomcat is not running. Leaving it running during this process can cause problems. Simply run the following command:

...