a liberty enhanced categorisation system

Created by: xing, Last modification: 09 Oct 2008 (05:40 UTC) by laetzer

What are Pigeonholes?

»Pigeonholes« is a service to categorize content. It replaces the legacy package. Pigeonholes makes it easy to organize, search and group content in hierarchically nested categories.

What it does

Pigeonholes allows you to create a set of containers (each of which is a pigeonhole). You can move them relative to each other in a nested system. To illustrate this (Pigeonholes are in red and content in blue):
  • pigeonhole 1
    • wiki page 1
    • wiki page 2
    • wiki page 3
    • blog post 1
    • pigeonhole 1.1
      • image 1
      • image 2
      • wiki page 1
      • pigeonhole 1.1.1
        • image 1
        • image 2
    • pigeonhole 1.2
      • blog post 1
      • blog post 2
      • image 1

The red content sits in their respective categories. There are options on how to display the related items in the same category and you can assign multiple content items easily by using the assign content page. This allows you to select a number of content items and add them to individual categories by simply checking the appropriate checkboxes. It's a very easy and quick way to keep your data categorised and up to date.


Pigeonholes is a service and therefore incorporates itself seamlessly into any content package that supports services. These include articles, wiki, blog posts …

When it comes to editing a wiki page or a blog post, you can assign the content to one or more Pigeonholes by selecting them using a list such as this one:

[ ] pigeonhole 1
[ ] pigeonhole 1 >> pigeonhole 1.1
[ ] pigeonhole 1 >> pigeonhole 1.1 >> pigeonhole 1.1.1
[ ] pigeonhole 1 >> pigeonhole 1.2


It is possible to assign a group or a permission to a given category, so that users of only that group, or users who have given permission, may view the content within it (not possible in Bitweaver version below 2). Pigeonhole permissions are inherited from their parents. For instance, in the above example, if pigeonhole 1.1 were assigned to the group Registered only registered users can view that content. The same applies for pigeonhole 1.1.1 but not for pigeonhole 1.2.


LibertyStructure has been tightened to only use a couple of database queries per structure. Wiki books (structures) as well as Pigeonholes perform great, while using a considerably low number of database queries.


last step: pages inherit permissions

by mlpvolt, 03 Apr 2006 (22:03 UTC)
As a next (possibly last) in categories to groups development it has seemed to me that allowing new pages to inherit permissions (and maybe categories) from the pages they are initially linked from is a very useful addition.

That way typical users could work in private to group pages without having to think about perms. As an admin this is a frequent request - first, everyone wants "my own private wiki," using wiki as groupware typically requires content classes with differentiated perms, and if content is not static, admins have to keep up with demand to create and assign perms to new pages. (groan).

I call it the last step because the "complete" permissions system is one that is fully flexible both vertically (nested hierarcy) and horizontally (equal but private). Enables the wiki as "a house with many floors and many rooms".

The other missing feature is the ability to "add user to my group".

example: admin creates a group "finance committee" and a category "finance committee" and a page "finance committee home" and a user with perms for the group. Then the user may add committee members, create new objects containing their content and membership can grow organically with no further admin assistance.


by Erin, 22 Jan 2007 (06:23 UTC)
Without the ability to assign a page to more than one pigeonhole, this would be a downgrade from categories, functionally. If pigeonholes can do this, you should say so.
  Page 1 of 1  1