[WikiTraccs] [Feature] Select specific pages for migration in Page Inventory lists

[heinrich-ulbricht]

How to conveniently select source pages for migration?

Currently there are three selectors available to configure what to migrate:

• Space Selectors - to select all pages of a space
• CQL Query Selectors - to select based on a search query
• Content ID Selectors - to select pages by ID

The Content ID selector allows an arbitrary selection of page IDs, thus - in theory - covering all page selection use cases.

But in reality, the effort to choose pages based on ID can be quite high.

The following use cases need better support:

• migrate only a subtree of pages, that means a parent page and all child pages
• let different stakeholders choose the migration target for each page of a space
• split a space into multiple parts based on some criteria

So far I witnessed multiple clients using Excel sheets to do the above.

The proposed solution in WikiTraccs is as follows:

• allow the user to select a space to further classify pages in this space
• WikiTraccs will then
  • create a new SharePoint list with preconfigured columns that hold metadata from Confluence (title, ID, parent ID, ...) and columns used to configure the migration (migrate or not, wave, target site, "this and all children" ...)
  • read information about all pages in the selected space from Confluence
  • write page information into the SharePoint list
• the user can now mark pages for migration, configure migration targets for pages, or share the list with stakeholders to make this selection

Those lists will initially be created per Confluence space. It's like the space inventory, but for pages of a space - a Page Inventory.

This list could contain additional information about pages: macros used, last modification time, etc. pp.

After selecting pages for migration, the user starts the migration in WikiTraccs, pointing WikiTraccs to the Page Inventory that should be migrated. WikiTraccs then determines the pages to migrate and starts to migrate.

Possible drawbacks:

• spaces with a large number of pages (> 5K?) might slow things down when writing information to a Sharepoint list

This Page Inventory-based approach should cover the Excel-based approaches I witnessed so far, as well as the listed use cases.