Difference between revisions of "Blue Folder Lookup"
(Created page with "File:helpheader_small.png '''Location in standard build:''' '''''Accessible anywhere a Blue Folder icon is displayed''''' You may have already noticed blue folders disp...") |
|||
Line 1: | Line 1: | ||
− | [[File:helpheader_small.png]] | + | [[File:helpheader_small.png|right]] |
'''Location in standard build:''' '''''Accessible anywhere a Blue Folder icon is displayed''''' | '''Location in standard build:''' '''''Accessible anywhere a Blue Folder icon is displayed''''' |
Revision as of 16:53, 1 December 2015
Location in standard build: Accessible anywhere a Blue Folder icon is displayed
You may have already noticed blue folders displayed on reporting outputs. For example, running the "Memberships/Skills Report" shows all of the Organisations/People on your system who belong to/have a group or skill. The basic output of the report looks something like this:
This output is fine, as long as it contains the information you need, but suppose that you want to cross-reference this output with some other information. The "real world" thought process might go like this -
We ask all of our clients whether they consider themselves computer literate, and we use a skill group called "computers" to log this, putting them in the group if they are computer literate. We also log the disabilities our clients have, if they have any. I wonder what the data would show if I could cross-reference this with the "Computers" group? Does the fact that someone has a disability affect whether they see themselves as computer literate? If it does, does the disability in question matter? A lot of our clients have arthritis - is having arthritis likely to affect your confidence with a computer? Is there anything we can do about this?... and so on.
To answer these questions you could do the following -
- Run the "Memberships/Skills Report" to see who is in the "Computers" group.
- Export this to a spreadsheet.
- Look up the relevant clients and their disabilities.
- Add these to the spreadsheet.
Steps 1 and 2 are easy; steps 3 and 4 will take a long time. What you need is an easy way to say to the system, "show me the ouput of this report, and add on the disability data for the relevant clients" - and this is exactly what Blue Folder Lookups allow you to do.
At the bottom of the reporting output is a blue folder.
Clicking this blue folder will take you to the lookup page.
At the bottom of the page, the data is displayed. At the top, however, we have two extra sections: Export Results Through Mailmerge, and Export This Report With Extra Data From.
Contents
Export Results Through Mailmerge
This section will allow you to put together the output of your report with a mail merge, which you have previously set up. Mail merges will be covered later in this chapter.
Export This Report With Extra Data From
This section has two ways to output data: as a spreadsheet, using the "Export This Report" button, or on a map, using the "Switch to Map View" button.
Exporting a spreadsheet
The basic spreadsheet to be exported will be roughly the same as the original report output. However, by using the Extra Data section, you can add columns onto the spreadsheet with more data in about the relevant clients.
Extra data from a Data Extraction
See later in this guide for details of setting up Data Extractions.
Once you have a data extraction set up, you can use that data extraction on any reporting output, using this drop-down box. For example, a data extraction has been set up named "EA", which shows the age range and ethnic background of any pool of clients. If you select this data extraction, and click the "Export This Report" button;
The resulting spreadsheet looks like this:
Not particularly tidy, but very informative. What you have here, after only a few clicks, is a spreadsheet showing:
- All people that were active in a skill group over a certain date range
- The information about the age ranges of those particular people
- The information about the ethnic backgrounds of those particular people
You can use this spreadsheet to show:
- Whether the people in a particular group are biased towards a particular ethnic background and/or age range
This kind of information is very useful. For example, consider disability again.
If the members of the group "Computers" (meaning the person considers themselves to be computer literate) contains no-one with a disability, does that mean that people with disabilities in your funded area are not being supported to access computers? Can your organisation do anything to help, or signpost people to an organisation which can help?
If the members of the group "Befrienders" are all younger and male, will this have an impact on how many people take up your Befriending service? Is there a need for more female Befrienders, and/or more older Befrienders?
...and so on. If you are using a paper filing system, and/or each department has its own database, you would not be able to answer these questions without a huge amount of manual data collection, counting and tabulating. Using Charitylog means that you can do this easily, in less than a minute.
Extra data from Client-linked Records
You also have the option to add data from Client-linked records. Various options are available. Like data extractions, these will simply add more columns on to the output spreadsheet. You can select more than one set of client-linked records by shift-clicking a range (PC or Mac), or holding the "Ctrl" button (PC) or the "Command" button (Mac) and clicking the options you require.
Extra data from Extension Databases & Extras
Finally, you can add extra data from the Extension Databases you have on your system (providing they are Organisation/Person linked or Personal Tab-linked).
Spreadsheet output size
You can add as many options as you need - there is nothing to stop you using a data extract which gives 20 fields on every result, then adding all the Client-linked records, and all the Extension Database records. However, this will result in an extremely long spreadsheet which is difficult to work with. Consider breaking your requirements down into a series of spreadsheets and then work with these.
Length of spreadsheet output is one of the primary reasons that Charitylog has moved to the .xlsx (Office 2010) output format. The old .xls format only allowed 256 columns, whereas .xlsx allows somewhere over 16,000 (not that you would want or need that many for a Charitylog output).
Map View
The Blue Folder Lookup screen also allows an output to be displayed on a map. This has various uses, but all of the most obvious are to do with geographical location - for example;
- Display all new clients over the last three years, and see where your client base is
- Display all new clients over the last year, and see how new projects have affected your clients' uptake of your services
- Display clients accessing a particular service/Project - are there holes in the coverage that cannot be explained? Do you need to make more efforts at outreach in those communities?
- Check for incorrectly filled Super Output Areas - are there any outliers displayed that might be wrong?
The map view relies on postcodes to place the clients/people, so if there is no postcode entered on their record, the map view will discard them. This is one of the reasons we advise that a name and a postcode should always be a minimum for data capture.
Gathering the data in in the first place
Look again at the spreadsheet output for the data extraction "EA", which added age range and ethnic group information onto the output of the Memberships/Skills Groups report.
This demonstrates the power available in Charitylog, of being able to get out any data you have on the system, cross-referenced with other data. However, this spreadsheet also shows the most common problem with extracting this data - the fact that users fail to enter it in the first place. The column for Ethnic Group shows that while a few people in this group have their Ethnic Group recorded on Charitylog, the majority do not.
This is not a problem for the day-to-day running of the service; you might well imagine that a volunteer manager would not want to explicitly ask every volunteer for their age and which ethnic group they consider themselves to be in - if done wrongly, it could look confrontational and unnecessary. However, from the point of view of the chief executive, or the fundraiser, it becomes very important.
- If your Computer Literacy project is only succeeding in serving people under 40, even though you know from market research that there is a real need for computer tuition for people over 60, is this to do with the people that are delivering the service? Are they all under 25? Does this have a bearing on the clients that are willing to take the service up, bearing in mind that the volunteer tutors have to enter the client's home? Are people who live alone particularly unlikely to take up this service?...
If the age range information has not been input by users in the first place, there is no way to answer, or even ask, these questions.
This is why it's so important that an organisation's data capture (and therefore data protection) policy is well thought out, and communicated to staff. Implementing Charitylog often provides a chance for an organisation to do this for the first time - speak to your Implementation Consultant if you have any questions.
Rob Kay - manual author (talk) 16:53, 1 December 2015 (GMT)