Difference between revisions of "Classification Code Setup"
| Line 91: | Line 91: | ||
* Forcing code entry introduces another step to the process of recording contacts. Codes can be very useful, but using them when they are not really needed can add unnecessary hassle to an end user's day-to-day work. | * Forcing code entry introduces another step to the process of recording contacts. Codes can be very useful, but using them when they are not really needed can add unnecessary hassle to an end user's day-to-day work. | ||
| − | * Only use codes if you have a | + | * Only use codes if you have a reporting need for that level of detail. If you do not need great detail, you may be able to use Referral Reasons, Contact Types, Project Subcategories or an Extension Database on referral entries. |
Revision as of 14:16, 2 May 2017
Location in standard build: Administration > Security > Classification Codes
Charitylog features a built-in, customisable coding system for Contacts, giving you a way of classifying activity. It is a hierarchical structure, so selecting a certain option in level 1 then gives sub-options in level 2, and sometimes there is a third level, a fourth, and so on. This diagram shows an example, with a Residential Care code grouping. Each option picked has an associated code, which is automatically added to the referral. When the user has selected an option in each level, the final code output is created and added to the details of the referral.
Note: a coding system does not need to have multiple levels. If you want to just use a single list of codes (i.e. one level only) then that's fine.
The arrows show the available paths to take. The red arrow shows the path actually taken, down to the final code creation: B2E, which actually means "Personal Expenses Allowance, within the Payment and Charging section of Residential Care".
You can create your own code groupings just like this one - use the "Create New Code Grouping" button to make a new set of codes.
...and once you have created your new code grouping, click "Edit" to be taken to the main codes entry screen.
Once a main code is created, you can then create further sub-codes within it, with the "Go To Sub-Code" button....
...and you can add further sub-codes within that sub-code...
...and so on.
Note that you can give your own code system as many levels as you need, but consider how easy (or otherwise) it will be for day-to-day users to enter the codes. It's best to keep any coding system as streamlined as possible.
Questions attached to codes
At each level of the classification coding system, you have the option to add a question if a certain option is picked. When the users selects that option, a field will appear for entry of an answer to a question.
Click on the name of a sub-code:
Then click the "Save and Enter Questions" button.
You can now enter a question to associate with the code. In this case, a question has been added to a "Bus Timetables" code, which will ask the client for the date they started using the bus in preference to a car. Click "Save Details" when complete.
You will now be returned to the question display screen, with your new question shown.
When a user picks this code, a date entry box will appear below it for an answer to be entered.
When to use codes
- Using classification codes is good when you want a hierarchical structure. It is particularly useful if you have a large amount of possible codes that you want to use - breaking them down into levels like this means it is easy for end users to select from even a very large list of codes, without actually having to know the codes in the first place. They can simply pick the appropriate code in level 1, then pick the most appropriate code from level 2, and so on.
- Codes are also useful because you can log several codes against each contact, and therefore against each referral. In a project where you discuss a wide range of issues with a client at one visit, this can be a useful way to log all of these at once. This would not be allowed by Referral Reasons etc.
- Finally, code entry can be optional or forced - so forcing code entry will ensure that something is entered against each referral.
When not to use codes
However, consider:
- Forcing code entry introduces another step to the process of recording contacts. Codes can be very useful, but using them when they are not really needed can add unnecessary hassle to an end user's day-to-day work.
- Only use codes if you have a reporting need for that level of detail. If you do not need great detail, you may be able to use Referral Reasons, Contact Types, Project Subcategories or an Extension Database on referral entries.
Rob Kay - manual author (talk) 13:45, 6 January 2016 (GMT)
