Talk:Aggregation

1. Aggregation

• Speed measurement - pages per hour
• Process description for training purposes

Categories and Naming

When combining organisation and the wiki system to achieve casual (and evolving) integrated organisational systems, one of the problems encountered lies in where to place new articles or paper notes which have been entered within the structure, which is represented by the workspace we call "Business Model".

Process

In other words, how do I know what to call my article and which categories do I place it in? We need to solve this issue to make it simple to enter content and to ensure knowledge processing in a productive way, which allows quick entry to an accessible location (cache) by someone in a "doing" role (e.g. Administrator) from where it then gets "solved" and placed in the system by someone in a "thinking" role (e.g. Manager). This process is important for the evolution of our business model.

The most generic approach to this problem would be that whoever is entering (or creating) content just names it under the name of the organisation, e.g. "Tech Support/Form for recording travel costs" and files it under the category for that organisation, e.g. "Tech Support|Form for recording travel costs". This describes the job of the doing role.

Now we have a generic category which contains articles that we only know enough about to know they are to do with that organisation somehow. Using "list-cat" we can list the articles in that category on the "talk" page of the business model workspace for that organisation, e.g. "Talk:Tech Support". On this talk page is a "todo" list where our freshly entered, uncategorised content is listed.

For our example, one of the processes entrusted to the manager of the organisation is "Content management". As part of this, the person in the manager role goes to the talk page of the business model, where all the articles, like the one described above, are listed. The manager can now regularly go through those articles and place them in the system to "solve" them.

Workflow

The content may been in the in the administrator's in-tray as a physical document, or in the form of an email in the email in-box, then the content was dealt with using the business model workspace, or placed in an "outbox" for further processing. The person in the role of administrator then, sees the category which contains the unplaced documents, in our case "Category:Tech Support" as an outbox.

To the person in the role of the manager, however, it is an inbox.

Business Model Evolution