I agree that an option to have the Inbox and Tags visible at the top level of a database would be a nice option and mostly satisfy the users of DT2 that built systems based on that model. If you did that, I would like the option to selectively choose whether Inboxes OR Tags are shown… for instance, I would show the Inboxes but hide the Tags.
I recall that this has been discussed in OP. Set up a local smart group at root of the database, with scope set to the local database’s inbox, set “kind is any document”. The smart group becomes a pseudo inbox at the top level of the database. Limitation of this method: you can view, edit, or move/replicate any items in this pseudo inbox, but you can’t add anything to this inbox. However, that should be quite acceptable (?) coz we normally are moving things out of the inbox to other groups in database?
That’s a possible workaround. Thanks for the idea. By the way, what is “OP?”
OP. Original Poster.
Ha… I thought it means other poster… my bad.
+1 for hiding the inboxes of other databases. I understand why they are useful. But it my case I don’t need them and I don’t want to accidentally file items into those not used inboxes.
Another limitation: you cannot set smart groups to be unsorted. (I use unsorted, and rearrange items within a tag to have the most important on top. Can’t do that with the smart group workaround.)
Seeing as the results are from multiple locations, Unsorted doesn’t work. However, Development could also weigh in on this.
An alternative would be to allow smart groups to have their own sort method.