Difference between revisions of "ExoDictionary:Migration Considerations"
From ExoDictionary
(Adding to list) |
(Need links to other definitions to not be pointing to the main namespace) |
||
| Line 12: | Line 12: | ||
*Custom template/branding for destination namespace on Spacepedia/Exoplatz | *Custom template/branding for destination namespace on Spacepedia/Exoplatz | ||
*Custom parameters for destination namespace on Spacepedia/Exoplatz | *Custom parameters for destination namespace on Spacepedia/Exoplatz | ||
| + | *Migrate definitions to a definition-specific namespace | ||
| + | *Change definition hyperlinks to stay within definition namespace | ||
===DURING=== | ===DURING=== | ||
Latest revision as of 16:20, 14 June 2019
Things to consider/work on for migrating Exodictionary to a Spacepedia/Exodictionary namespace:
BEFORE
- Find and/or develop bot for bulk actions
- Test bot
- Reduce definition entries imported from SP-7 that are not relevant to the exoproject wikis
- Bulk cleanup efforts
- Reducing tag and category collisions
- Migrate categories that are not to be merged to their new names
- Migrate Exodictionary namespace to a new namespace?
- Can a specific namespace not have automatic capitalization?
- Custom template/branding for destination namespace on Spacepedia/Exoplatz
- Custom parameters for destination namespace on Spacepedia/Exoplatz
- Migrate definitions to a definition-specific namespace
- Change definition hyperlinks to stay within definition namespace
DURING
- Export definitions in batches small enough to not cause timeouts
- Import definitions to destination Exodictionary namespace
- Export categories
- Import categories
- Export image pages
- Import image pages
- Download images
- Upload images
AFTER
- Check for and address any collisions
- Verify transfer of all non-removed content
- Verify usefulness of transferred site
- Deactivate legacy wiki
- Set up redirection of links to legacy wiki
