When using Confluence as a remote target, we want a structure which avoids duplications, is easy to search visually, and creates pages within the size limits imposed by the platform.
After some thought, I have decided that a parent-child hierarchy would be the best option:
Parent page's title is the name of the channel e.g. #some-channel
Child pages' titles are the min and max timestamps of the messaged included e.g. 2023-12-01 08:34 – 2023-12-13 12:34
We can save the channel ID as Confluence metadata, then search for it using CQL to check if a parent page already exists, and get its ID.
One disadvantage is the size of the initial backup, which could lead to a (too) large page.
Another is the navigation in Confluence itself, which can be annoying especially for channels with low traffic.
When using Confluence as a remote target, we want a structure which avoids duplications, is easy to search visually, and creates pages within the size limits imposed by the platform.
After some thought, I have decided that a parent-child hierarchy would be the best option:
#some-channel2023-12-01 08:34 – 2023-12-13 12:34We can save the channel ID as Confluence metadata, then search for it using CQL to check if a parent page already exists, and get its ID.
One disadvantage is the size of the initial backup, which could lead to a (too) large page. Another is the navigation in Confluence itself, which can be annoying especially for channels with low traffic.