...

Before You Start

Upgrade a Network

SHRINE 1.22 has a few new features, some of which require consistent configuration across a network.

Know Your Network-Wide Configurations for New Features

• Which method of re-identification protection? (required configuration, default provided): Decide what configuration to use for obfuscation. In 1.22, we provide support to replace obviate the need for user lockout with a more involved data stewardnew features: a more interactive Data Steward Application (DSA), greater obfuscation of results, and other changes. 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 turning lockout offoff if your network governance allows.
• Network contact information? (optional configuration): Determine what fields every node should provide via the SHRINE static data service. We created this feature to provide contact information for the right person that remote researchers should contact for more information about query results. Networks should agree together on what key-value pairs to supply for this contact information and any other required information.
• Decide Bot defense values? (default values provided, optionally configurable): Determine what values to use for Bot Defense for the your network, if other than default.

Upgrade a SHRINE Node

Know Your Local Configurations for New Features

• Who should get emails generated by SHRINE's Data Steward Application? (required if not using lockout for re-identification protection): Find appropriate email addresses for the system administrators and data stewards.
• Start figuring out the values for the SHRINE static data service. It may take some time to discover.
• Determine how How will email from the DSA will be sent. ? (required if not using lockout for re-identification protection): The default configuration assumes postfix on port 25.
• Learn what If your network requires for obfuscation.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:

...