From installation to concrete use-cases
“This starts with information on installing the program, then includes details on the general functions, gives concrete examples, includes use-cases which are specific to individual states and, last but not least: training material,” explains Meier. “The principle is that our wiki offers knowledge management for the user, who can then find the information they need according to what they already understand.” The book navigation system is used to structure the contents in the wiki, which is offered in BlueSpice with the extension “Bookmaker”. This places the contents in a hierarchy of chapters and subchapters. Meier describes it in this way:
“At the start, there is a concrete definition of the task, then there is a link to a description of the software’s functionality. Those who want to know more about this can look at concrete examples, where necessary with photos of the LEFIS masks, and so be able to trace through how the project needs to be carried out in detail.” Here, great emphasis is placed on user-friendliness. One of the ways this is achieved is with a “create function”. Using this, the user can create a new page without having to understand the deeper wiki structure. The structure is defined by the templates and categories provided.
Figure: Function call in the “LEFIS” application
Topic hierarchy instead of long running texts
The whole system functions very clearly with expandable drop-down menus and clickable info buttons. “In the PDF handbook, you had to tortuously hunt through long texts, and sometimes search in hundreds of documents to find what you wanted to know. In the wiki, you only read the content you need and want. You can progress from brief descriptions down into the detail, for example concrete use-cases, when one needs such details.”
Put simply, for the task “import data from the land register management”, some users only need to see the heading of the task description, while others want to know which entries need to be made in the function dialogue. Depending on what they already understand, the task description may be enough for them, or they may need to dive deeper into the functional details and perhaps even take into account state-specific cases. If that is not enough, then the member of staff can see an example for each step of the work. The structures are defined. The contents are being developed.
“The application continues to develop and grow and so does our wiki.”
As a basic principle, all users are authors in the wiki: everyone has the permissions to add new examples. Additionally there are supervisors, specialist admins who have more permissions for describing the software and setting out state-specific rules, and three wiki admins who take care of the networking, copy-editing and the structure of contents. They are supported with training courses and workshops from Hallo Welt! GmbH. There is a four-person group “AG help” who the users can turn to in case of doubt. “Just as the application continues to develop and grow, so does our wiki,” says Meier. Every time the software is updated, the functional descriptions need to be adapted, and new practical examples need to be added all the time. “The work never really ends. This is really in the nature of things with such a complex application as LEFIS. But in the end, whatever questions a user has, they should be answered in the wiki.” (sa)