Step 4:  Get Your Database Ready

Get the Database Installed (if hosting locally)

Your IT Contact will need to install and test the Pirouette database, so that the software is functional and ready for use.

(If you are using Roxy Software’s hosting service, we’ll set up the server, complete the installation, and send you a web link to your Pirouette install.)

Database Configuration

Once the database is installed, the next step is database configuration by the Pirouette Administrator.  This is the process of customizing the database for your particular organization so that it’s ready for use.

Configuring the program structure:

This important step determines how client data will be categorized in the database, and the type of reporting (and analysis) you’ll be able to do with the data.  Ideally, your program/service structure should be configured in a way that is meaningful to the users entering data, but you should also consider your organization’s reporting requirements and the way in which the data will ultimately need to be compiled.

Creating and configuring user accounts:

For staff to access Pirouette, an employee record must be created in the database that contains the user’s name, login username, and
password.  This record is referred to as the Pirouette user account.  It’s advisable to have the administrator create all passwords, in order to maintain consistency in password strength and conformity to the organization’s password policy.

Configuring pulldown lists:

Upon initial installation, Pirouette is preconfigured with pulldown lists.  The information contained within these lists serves as a great starting point, and might even be completely adequate for your organization’s needs.  However, you should review the lists and revise them as necessary to suit your particular organization.

As the overall intention of gathering information is to aggregate the data, an additional pulldown item should only be added if it contributes to
the overall quality and meaningfulness of the data being collected.  For example, adding a large number of very specific ailments to the physical health issues list will not only make the pulldown list long and unwieldy, but the specificity of the data will make it less meaningful.

For detailed steps on how to perform these and other configuration functions, see the Pirouette Administrators Manual.