I posted some suggestions concerning the 'page metadata management' use case for Databases before - one of my favourite use cases of Databases as you will have guessed by now.
Just to give you an idea: a direct interaction with page metadata through Databases (eg. changing status, or adding a label) saves me more than 15 seconds per interaction.
Have you really never thought how time absorbing it is to just change a label, or a title, or a status? Databases provides you with the 2 seconds interaction.
But in fact it saves much more time than the 15 seconds per interaction:
- without the database I first need to search for and find the page - add at least 10 seconds
- without the database I do not have the overview of metadata, and chances are big I even would not manage and update the metadata at all, which ends up in heaps of lost time when confronted with false metadata - add an eternity.
- why not directly change page owners in the database?
- why not directly change page titles?
- why not directly type into excerpts in pages?
- list all incompleted tasks on that page
- show child pages or parent page (or breadcrumbs)
- generate all kind of behaviours now in macro's
...
Thanks for this feedback Filip - I'm glad Confluence databases make it easier for you to view, manage, and change page metadata. We are definitely looking into the ability to change other page metadata directly from the database. Meanwhile, I'll share this feedback with the Confluence pages team about the need to easily edit metadata!