Sunday, October 20, 2013

LodgeMaster registration filtering

Filtering members in LodgeMaster to repair Scout registrations

After setting registration status following a successful import of one or more of the 3 files from ScoutNet (Registered, Not Matched, and Not Registered) after an audit run, each current years dues paid member will have a status code/value set.  Here's one way to find those still needing to be checked against ScoutNet (though some who "pay dues" may in fact not be registered with the Council when audited).

Click on the Advanced Filter button, and add the condition for the "Reg. Audit Result" field as shown.



Splitting  into Chapters and Status

With the members split into registered and the rest, add the column for Result if not visible in the current view.


Chapter

Filter Chapter by clicking on the funnel at the column heading.


Result

Show not audited, not matched, and/or not registered by filtering on that column as shown.



The count for each of the unchecked members is shown at the bottom left of the screen.

Sunday, September 15, 2013

Bath update


Bath update

Before and during remodel



June 22

July 4

July 13th, after summer camp

July 16th

After, mainly; August 20

Friday, May 10, 2013

OALM Election Checks

Checking Election Data Consistency in OALM 3.

Version 2 did not let us look at this view easily; in version 3, once Ordeal Candidates are registered, look at the Event Manager view, filtering as follows.



1

2

3

4

5

6

Monday, March 11, 2013

OALM 3 filtering

To complement and expand prior posts on the LodgeMaster 3 filtering steps, here's another view, with more pictures.

Figure 1 shows the header for "Full Name" and the triangle clicked to indicate sorting on that column value.  The dues year is 2013, as the default starting point on these menus is the current year.



1

Figure 2 shows the results of clicking on another column header, Chapter, so the triangle there is highlighted.  There isn't a secondary sort column - I would expect the prior results (by full name) would be used after Chapter. I have not found a way to add a second sorted by.


2

Figure 3 shows the "funnel" action, distinct from the triangle, which brings up a checklist. This works fine for few distinct values; less so for wide ranges such as name. The sort order remains, for those rows that are left.


3

Figure 4 shows the filter editor, after clicking on "Advanced Filtering", where the columns selected by the prior "funnel" checklist have been converted to a logical clause ("Is any of").


4 Five adds another cause, with the choice of operators highlighted.  These will change depending on the field being character, numeric, date, etc.
I would use these options where I could, rather than the checklists, since keeping all the logic in one place avoids incorrect documentation - the funnel values may not be listed in some cases.


5 Six shows the necessity for selecting prior dues years, and perhaps future, to get a wider range of records. I can't select a range without clicking each one, although there is a button at the top for "all" or "none".  Writing a "between" clause makes more sense to me.


6 Seven adds a between clause for last  name.

7 Eight shows more of the conditions than figure 5 above shows. The icons help to visualize the logic. What's not easy for me to create using these menus is anything with precedence or grouping.

8

Thursday, March 7, 2013

Function or Control? You decide

New laptop. New keyboard. Cleaner, but things are not where I left them.

Who moved my control key? Again.



Friday, March 1, 2013

OALM chapter members

1

  •  members for The Capitol Chapter
  • which years
  • their contact info
  • respective level
  • have several members that have not paid their dues and are trying

See also




2






3



Wednesday, February 27, 2013

OALM 3 - Dues Paid Check

In the updated version of the Order of the Arrow "LodgeMaster" membership database, there are new ways of looking for information. One we struggled with in prior versions was checking on dues paid status for individuals, whether in a unit, or in a Lodge position.  Below are the results of a query where I altered the "dues years to include" to cover the range 2010 through 2012. Not shown is the advanced filtering condition where position is not empty.

You'll notice there are dues paid records for 2013, though one might expect these to be outside the range specified.  The reason these appear is that these members also paid in a prior year, so they match the rules given.



To view only those records in the range requested, you will need to add an "exclude" year condition so that the current year does not match.