Update instance archetype nomenclature
Currently, the title of each default archetype is based on a client use case. This was a legacy decision, is not informative for all users and should be modified to be more generic moving forward. We'll be introducing functionality in the near future where users can copy and/or create new instance archetypes - there are multiple reasons for these names to better describe the default workflows they represent.
The code changes would be as follows;
- Find every place in the code where the current archetype names are used, using a simple search, and change all of these. This should include any migration code. Name changes for archetypes.
aperture
-> 'journal';colab
-> 'prc';elife
-> 'preprint1';ncrc
'preprint2'. - Create a migration to update instanceName in the JSON in the configs table.
- Update CHANGES.md to instruct customers to change these names in their .env files prior to upgrading.