The Openbravo ERP glossary project: helping Openbravo users develop their understanding of ERP

When you are implementing an ERP system for the first time, you can be faced by a double learning curve. Not only do you have to learn the new software, but you have to become familiar with the theories and concepts of ERP that underpin it. ERP is a specialist area and it can feel like a whole new language.

That's why we've started compiling a glossary of terms on the wiki. The glossary covers specific Openbravo terms, but also both general ERP terms, and I'd like to request help from the community in taking it further.

It's a project that's easy to join in - it doesn't require a big time commitment and you can dip in and out of it at your leisure. If you are already an expert, you can help by defining some of the terms on the list. If you're a novice, you can help by adding any terms you don't understand to the list of candidates for inclusion.

The glossary stands on its own as a useful document, but as it grows we will be able to link to it from elsewhere in the wiki and also use it in online help. As a technical author it's also a useful reference for me as I work through the system documenting it.

To get involved, you just need to be a registered user on the Openbravo wiki. Contributions are very gratefully received.

My name is Rachel Johnston and this is my first blog post as Openbravo's technical author. In the months that follow, I'll be posting here to keep you up to date with documentation at Openbravo.

I started working at Openbravo at the end of August 2008, and as the company's first full-time author, I'm starting off by trying to address some of the immediate needs that users have identified. In particular, I'm aiming to deliver a complete configuration guide for Openbravo ERP by the end of 2008. As part of that process I'm also working on a quick start guide which covers the essentials - a small, easy-to-follow document that will make it easier for new customers and evaluators to get Openbravo ERP working "out of the box".

In the longer term I'll be completely revising, restructuring and rewriting the documentation set - including comprehensive online help. The aim is to change the user documentation from a product based approach, (describing what you can see on the interface) to a task based approach (explaining how to use the product to get things done). For more technical users, there are also plans to develop better resources for contributors and developers.

Although there is now a professional author in-house, contributions from the community are still very welcome. The wiki is still at the heart of Openbravo documentation, but the coming improvements will make better use of the material that's there, fill in the gaps and enable you to use the wiki in a more productive way.

If you have any requests, feedback or corrections, there is a Documentation thread on the sourceforge forum. Alternatively, post them here or e-mail me in person at rachel dot johnston at openbravo dot com