For official reporting to church headquarters, that's correct. But I think people are wanting some other categories for local reporting. If none of the other "unofficial" categories never make it into the local summary, then all the different visit types are pointless, no?The Earl wrote:It does not matter what we call the two categories, what is important is that we have to aggregate all other types into 'visited / not visited' for reporting.
HT/VT Reporting Website Overview
-
russellhltn
- Community Administrator
- Posts: 36835
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
-
brado426
- Member
- Posts: 313
- Joined: Sun Feb 11, 2007 9:50 pm
- Location: Foothill Ranch, CA
I put together this "Contact Type Editor" administrative screen shown below:

We have our standard contact types in the top grid that cannot be added to or deleted, however, the text can be changed. We have the custom contact types in the lower grid. For the custom contact types, new contact types can be added, the text can be changed, and the contact type can be deleted (not really deleted, but deleted as far as the user is concerned.) For each custom contact type, you can specify if it should be counted as "Visited" or "Not Visited." For Visiting Teaching, this will say, "Contacted and "Not Contacted." I'm also thinking that for Visiting Teaching, "Phone and Letter" will need to be "Standard Contact Types."
I'd like to keep it so the teacher can report by selecting only one dropdown box. The easier it is for the user to report, the more likely they will report on their own. I think some changes are in order for the "Reporting Page" to accomodate this, but I haven't thought that far ahead yet.
Comments?
Brad O.

We have our standard contact types in the top grid that cannot be added to or deleted, however, the text can be changed. We have the custom contact types in the lower grid. For the custom contact types, new contact types can be added, the text can be changed, and the contact type can be deleted (not really deleted, but deleted as far as the user is concerned.) For each custom contact type, you can specify if it should be counted as "Visited" or "Not Visited." For Visiting Teaching, this will say, "Contacted and "Not Contacted." I'm also thinking that for Visiting Teaching, "Phone and Letter" will need to be "Standard Contact Types."
I'd like to keep it so the teacher can report by selecting only one dropdown box. The easier it is for the user to report, the more likely they will report on their own. I think some changes are in order for the "Reporting Page" to accomodate this, but I haven't thought that far ahead yet.
Comments?
Brad O.
-
brado426
- Member
- Posts: 313
- Joined: Sun Feb 11, 2007 9:50 pm
- Location: Foothill Ranch, CA
I put together this "Contact Type Editor" administrative screen shown below:

We have our standard contact types in the top grid that cannot be added to or deleted, however, the text can be changed. We have the custom contact types in the lower grid. For the custom contact types, new contact types can be added, the text can be changed, and the contact type can be deleted (not really deleted, but deleted as far as the user is concerned.) For each custom contact type, you can specify if it should be counted as "Visited" or "Not Visited." For Visiting Teaching, this will say, "Contacted and "Not Contacted." I'm also thinking that for Visiting Teaching, "Phone and Letter" will need to be "Standard Contact Types."
I'd like to keep it so the teacher can report by selecting only one dropdown box. The easier it is for the user to report, the more likely they will report on their own. I think some changes are in order for the "Reporting Page" to accomodate this, but I haven't thought that far ahead yet.
Comments?
Brad O.

We have our standard contact types in the top grid that cannot be added to or deleted, however, the text can be changed. We have the custom contact types in the lower grid. For the custom contact types, new contact types can be added, the text can be changed, and the contact type can be deleted (not really deleted, but deleted as far as the user is concerned.) For each custom contact type, you can specify if it should be counted as "Visited" or "Not Visited." For Visiting Teaching, this will say, "Contacted and "Not Contacted." I'm also thinking that for Visiting Teaching, "Phone and Letter" will need to be "Standard Contact Types."
I'd like to keep it so the teacher can report by selecting only one dropdown box. The easier it is for the user to report, the more likely they will report on their own. I think some changes are in order for the "Reporting Page" to accomodate this, but I haven't thought that far ahead yet.
Comments?
Brad O.
-
nbflint
- Member
- Posts: 204
- Joined: Mon Mar 12, 2007 9:07 pm
-
The_Earl
- Member
- Posts: 285
- Joined: Wed Mar 21, 2007 9:12 am
-
russellhltn
- Community Administrator
- Posts: 36835
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
I would have Contact Text first, but yes the same for both.nimebe wrote:You should Switch the column order for Standard contact types so it matches the custom contact types; i.e. contact type column first
In fact, I'd go one step further - merge them into one table but omit the "delete" and "chart separately" from the two standardized types. I think the two table setup is likely to confuse a non-technical person.
Uh, what does "chart separately" do? Sorry if it's been covered before, but it's not immediately obvious to me.
-
brado426
- Member
- Posts: 313
- Joined: Sun Feb 11, 2007 9:50 pm
- Location: Foothill Ranch, CA
The Earl wrote:That is perfect.
Again, I don't think you need the ability to change the standard types in the UI, but having the ability is only a liability if the admin does something silly.
I don't like it either, but there are cases that it would be a necessity such as for foreign languages.
I would have Contact Text first, but yes the same for both.
Yeah, you guys are right.... I'll change that.
In fact, I'd go one step further - merge them into one table but omit the "delete" and "chart separately" from the two standardized types. I think the two table setup is likely to confuse a non-technical person.
Well, I put them in two tables to make it absolutely clear which Contact Types were the standard ones and which contact types are the custom ones. If we put it in one table, I think it would be harder to differentiate between the two.
Uh, what does "chart separately" do? Sorry if it's been covered before, but it's not immediately obvious to me.
Yes, this needs to be made clearer. This option determines whether the custom type shows up as part of the "Counts As" type (in this case, Visited or Not Visited) in the statistics view and pie chart. If this box is checked, it will show up as a different section of the pie chart. For example, someone may want to give the option of "Attempted" but they just want it to be graphed as "Not Visited" along with the rest of the not visited. I think the best way to clear this up is to add some instructions.
Brad O.
-
russellhltn
- Community Administrator
- Posts: 36835
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
brado426 wrote:Well, I put them in two tables to make it absolutely clear which Contact Types were the standard ones and which contact types are the custom ones. If we put it in one table, I think it would be harder to differentiate between the two.
My first reaction is "does it matter"? But then, I think I see what you're saying. You don't want to give the impression that the whole thing gets reported back to CHQ. Perhaps a bit of explanatory small font text could make the difference clearer. Standard - Visit types reported to Church Headquarters. Custom (perhaps "optional"?) Additional visit types for local reporting only. (Optional)
My suggestion is "Tallied separately (from subcategory)", but I don't know as it's any clearer.brado426 wrote:
For example, someone may want to give the option of "Attempted" but they just want it to be graphed as "Not Visited" along with the rest of the not visited. I think the best way to clear this up is to add some instructions.
Edit: Is there a way of doing the chart so that the visit/not visited and the subcategories are both clear? I'm thinking of a "removed slice" to distinguish between visit/not visited while the individual subcategories are shades of the two main slices. (I'm guessing "not reported" would be considered "Not visited".) That would help make the distinction between "local" and "official" stats.
-
brado426
- Member
- Posts: 313
- Joined: Sun Feb 11, 2007 9:50 pm
- Location: Foothill Ranch, CA
RussellHltn wrote:
Is there a way of doing the chart so that the visit/not visited and the subcategories are both clear? I'm thinking of a "removed slice" to distinguish between visit/not visited while the individual subcategories are shades of the two main slices. (I'm guessing "not reported" would be considered "Not visited".) That would help make the distinction between "local" and "official" stats.
That is something to think about. "Not Reported" actually shows up as a separate section of the pie chart. I thought it would be best to separate the "Not Visited" and "Not Reported" and allow the Presidency to manually mark anything that was still "Not Reported" at the end of the month.

I think I prefer it this way.... does anyone disagree? If we counted "Not Reported" as "Not Visited" I think we would be potentially making incorrect assumptions for the Presidency.
Brad O.
-
mkmurray
- Senior Member
- Posts: 3266
- Joined: Tue Jan 23, 2007 9:56 pm
- Location: Utah
I agree with you for local purposes, but when it comes time to report to CHQ, an assumption must be made and it's probably more accurate to assume the families weren't visited than to assume they were.brado426 wrote:I thought it would be best to separate the "Not Visited" and "Not Reported" and allow the Presidency to manually mark anything that was still "Not Reported" at the end of the month.
I think I prefer it this way.... does anyone disagree? If we counted "Not Reported" as "Not Visited" I think we would be potentially making incorrect assumptions for the Presidency.