We are moving from an intranet to confluence. In our intranet, we had the concept of a "content manager" who was assigned a number of pages. Each year they could view a list of their pages and they'd sign off on each page as being 'current'.
I was thinking about how to achieve this with confluence and it seemed possible with tags. I could add a tag "review" for any content that gets reviewed. I could add "reviewer-username" to attach a manager to a piece of content. I could then have these people add "reviewed-YYYY" for the year they reviewed the content.
This would allow me to use the content by label macro to see all content that is reviewable but hasn't been reviwed in a certain year for example.
This seems like heavy usage of the labels - does anyone have a better approach for how to have content managers using out of the box tools?
Archiving Plugin is a Confluence add-on developed for exactly these use cases.
The nicety is that it makes the whole thing automatic. You configure the rules, and then the list of pages to be reviewed will come to the content managers, so it's fire and forget. Page expiration can be set to exact dates, or "this page expires in N days from its last update", "this page expires in N days from its last view", etc.
Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time! We're looking for people to participate in a remote 1-hr workshop...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs