Author Topic: "Non-member" member type addition  (Read 5212 times)

dave4him

  • Global Moderator
  • Full Member
  • *****
  • Posts: 48
  • I love this job!
    • First Baptist Church Awana Clubs
"Non-member" member type addition
« on: February 11, 2012, 06:42:28 PM »
Note: This request applies to the Cloud database's Windows App as well as the Legacy database.

I think my Subject Line is an oxymoron ::) ;D

I am trying to figure a way to include Grand Prix racers from our 'Open' class in to the database so that they will be included in the Event grid, reports, etc. (Our Open class consists of graduated clubbers and any church member) Presently I would have to make them a "Leader" with a 'visitor' or 'prospect' status, which would work....but I don't want to add them as Leaders when they are not.  :-\ Could a simplified 'non-leader', 'participant' etc. status with a simplified member file be available? The 'graduated' clubbers are available to add to the Event already... :)
Any thoughts?
« Last Edit: March 24, 2022, 11:55:07 AM by Annette »
David Barnes
Awana Commander
First Baptist Church
Branford, FL
N.Fl. Awana Ministry Team

Rick Leffler

  • Guest
Re: "Non-member" member type addition
« Reply #1 on: February 12, 2012, 09:17:13 PM »
David T from Alaska submitted a request this year for new member types of "Parent" and "Guardian" so that more details could be entered for those. I thought that was a very interesting idea. This additional non-member type value would fit right in. 

Sometimes an idea that seems simple at first turns out to be more complicated once you consider the impact throughout the rest of the system.  Let's talk through this to see if there are any significant consequences. Please add your ideas and comments to this thread.

What might be some Pros and Cons to adding more Member Type values?

Pros:
- We could have robust tracking of Parents/Guardians.
- We could track non-member participants for Grand Prix or other events like Dave suggested in this thread.

Negative impact or Consequences:
- Would we still use the same "Leader" list module and add another tab for non-Leader member types?  Or, do we rename the Leader List to something more generic that would encompass all persons EXCEPT clubbers?
- What about all the reports where there is a Member Type combo?  Should we populate all of those combos with all of the possible Member Type values that would be seen on the Member form? (probably so)  And if we did, would the reports still make sense?
- What about the Member Type selection on the Check-in screen? Same question as the reports, do we have all values shown there?
- If we have at least two or three additional non-member types like "Parent", "Guardian", "Participant" do we also create a set of attendance (aka Session) records for them too like we do for Leaders and Clubbers?
- When an database user enters a new record in the Member form for an adult person who is a parent and is serving as a leader in the club. What would be the correct Member Type choice, Parent? Leader?  (I'm guessing Leader would be the best choice. Do you agree?)
- If we select a Member Type of "Participant", wouldn't that cause confusion... participant in what? The Awana Club? The Gran Prix? Church?  hmm.


As I think more about this I am reminded that I have had a number of requests from folks to be able to use AWdb to track more than just their Awana club. A couple of years ago we were able to start using the database to track VBS and I think that was helpful to those who needed that ability.  Some folks have said they would like to track small groups and Sunday School classes too.  Presently that isn't possible because a particular person (Clubber or Leader) can only be assigned to one "Club", and each club has only ONE set of attendance (aka Session) records. 

To broaden the capabilities of the Approved Workman Database so it can track any type of person (child or adult) and any number of relationships and areas of service or participation or associations to any number of groups (clubs, classes, small groups, committees etc),  we will need to re-architect the data model and interface.  It is likely all of the reports will need to be re-worked too.  I think it is the right thing to do, but it will be a major undertaking.  After all this pondering I'm feeling hesitant to taking the easy out quick fix of merely adding a couple of new Member Type values.  What are your thoughts?


dave4him

  • Global Moderator
  • Full Member
  • *****
  • Posts: 48
  • I love this job!
    • First Baptist Church Awana Clubs
Re: "Non-member" member type addition
« Reply #2 on: February 14, 2012, 02:27:56 PM »
I see your point Rick. To fully implement this additional member type does create more headaches than it is worth doing it seems. I experimented and found satisfactory results using this method: Created new member > assigned as Leader > Visitor status. Added Gender, Contact info > Created Fee (GP race car kit). Entered payment in Ledger.
RESULTS:
My "visitor" prints up in my Award Report and is listed in Event grid view. My inventory is adjusted automatically, funds are accounted for in Ledger. This covers my needs for adding a non-member to our Grand Prix Event. I started to use "prospect" instead of 'visitor' status but the Fees/Ledger are not available for a prospect.

Maybe if others requested similar enhancements in the future, you could revisit this thread.  ;) 
David Barnes
Awana Commander
First Baptist Church
Branford, FL
N.Fl. Awana Ministry Team