Current revision |
Your text |
Line 4: |
Line 4: |
| documented. | | documented. |
| | | |
- | == CallOutPriority == | + | == Status == |
| | | |
- | <code>CallOutPriority=</code> changes the order of people
| + | You'll noticed that the |
- | with a group.
| + | |
- | It can for instance be used to order the Emergency Callers
| + | |
- | in the sequence they prefer.
| + | |
| | | |
- | The value is an integer.
| + | <Joined Type="Member" Start="1997-03-04" /> |
- | Lower values are presented first.
| + | |
| | | |
- | If you don't want to specify a value, don't include <code>CallOutPriority=</code> at all.
| + | has changed to |
- | The default value of 999 will then be assumed.
| + | |
| | | |
- | == OpStatus == | + | <Status Type="Member" AsOf="1997-03-04" /> |
- | One of the fields is called OpStatus, for Operational Status. We aren't
| + | |
- | required to keep a history for this, so there is only 1 line of
| + | |
- | current information. OpStatus can be:
| + | |
| | | |
- | '''Emergency''' - an Emergency Response Member
| + | This is getting ready for the new organizational membership |
| + | classifications. |
| | | |
- | '''Resource''' - a Resource Member | + | Once we know the membership type for people you'll add new |
| + | entries for them. |
| | | |
- | '''Non''' - a Non-Responding Member
| + | For instance, in my membership record you currently have lines |
- | == BirthDate ==
| + | like: |
- | The BirthDate field is used for reporting for WCB coverage
| + | |
- | and determining operational status policy (must be 18 to be an Emergency Response Member).
| + | |
| | | |
- | The format should be YYYY-MM-DD
| |
- |
| |
- | == Phone ==
| |
- | Example:
| |
| <pre> | | <pre> |
- | <Phone Location="Work"
| + | ... |
- | Format="Live"
| + | </Equipment> |
- | Number="627-2460" />
| + | |
- | </pre> | + | |
| | | |
- | '''Phone''' elements list phone numbers that can reach the person.
| + | <Status Type="Member" AsOf="1997-03-04" /> |
| | | |
- | The '''Number''' is required. It gives the phone number.
| + | <Participation> 1997-03-04 (mtg) |
| | | |
- | Don't use a blank number for an unused entry. Just delete the entire Phone record.
| + | ... |
- | | + | |
- | You don't have to give the area code if it's 403. And you shouldn't add a 1 if it's long distance. If there's an extension that's needed, add it after the phone number.
| + | |
- | | + | |
- | The '''Location''' is optional. It gives a brief description of where the person is being called. Standard locations are abbreviated on the call-out sheet:
| + | |
- | * '''Work''' becomes "w:"
| + | |
- | * '''Home''' becomes "h:"
| + | |
- | * '''Cell''' becomes "c:"
| + | |
- | If you use another value for location, it will appear as is e.g. "Calgary:"
| + | |
- | | + | |
- | If a person wants to indicate that their home number is also a cell number, they can have multiple Phone elements with the same Number.
| + | |
- | | + | |
- | <pre>
| + | |
- | <Phone Location="Home"
| + | |
- | Number="627-2460" />
| + | |
- | <Phone Location="Cell"
| + | |
- | Number="627-2460" />
| + | |
| </pre> | | </pre> |
- | will appear on the call-out sheet as "h/c:627-2460".
| |
- |
| |
- | Numbers should be listed in the order that the person wants them to be called by the call-out people.
| |
- | E.g. if I always have my cell phone on, I would list that number first.
| |
- |
| |
- | The numbers may also be called by a machine as part of PCSAR's automated call-out system.
| |
- | If that is used, all numbers are likely to be called simultaneously.
| |
- | There may be some numbers that shouldn't be called by machine,
| |
- | for example, those that are answered by a receptionist who wouldn't know who to transfer the call to.
| |
- | In that case you can add <code>'''Format="Live"'''</code>. '''Format''' is optional.
| |
- | There's also an old <code>'''Format="Fax"'''</code>
| |
- | which we don't really use any more but is available if you want to record a fax number.
| |
- |
| |
- | == Training ==
| |
- | The training section are the lines between
| |
- | <Training>
| |
- | and
| |
- | </Training>
| |
- |
| |
- | Add lines in free form for major courses and certifications the person has received.
| |
- | === Criminal Record Review ===
| |
- | For the criminal records check add a line to the training section like:
| |
- | <Qualify What="Criminal Record Review" AsOf="2015-01-20" By="Claus Burchert"/>
| |
- | Recording who reviewed the Criminal Records statement and when they did it.
| |
- |
| |
- | == Status ==
| |
- |
| |
- | Each member record has one or more Status lines. E.g.
| |
- |
| |
- | <pre>
| |
- | <Status Type="Applicant" AsOf="2012-01-04" />
| |
- | </pre>
| |
- |
| |
- | These elements indicate when the person applied for membership,
| |
- | when it was granted, and when they ceased to be members.
| |
- | They also show when the person changed their membership status,
| |
- | e.g. going from "Associate" to "Voting".
| |
- |
| |
- | The Alberta Society Act requires us to keep
| |
- | track of this information, even for past members.
| |
- | So we should never delete or change existing "Status" elements,
| |
- | only add new ones with a newer date.
| |
- | In other words, do not change the type and date of an existing Status element;
| |
- | instead add a new one.
| |
- |
| |
- | The Type can be '''Member''' for very old records
| |
- | before the club decided to have separate '''Associate''' and '''Voting''' classes.
| |
- |
| |
- | All current members long been classified
| |
- | as either Associate or Voting,
| |
- | so for long standing members you might see something like:
| |
| | | |
| When you classify me as a "Voting" member you'll add a line to | | When you classify me as a "Voting" member you'll add a line to |
Line 131: |
Line 50: |
| </pre> | | </pre> |
| | | |
- | which shows when they were classified as Voting.
| + | If I stopped attending meetings in 2002, and then dropped out |
- | | + | |
- | If the member stopped attending meetings in 2002, and then dropped out | + | |
| all together in 2003 you might have lines like this: | | all together in 2003 you might have lines like this: |
| | | |
Line 152: |
Line 69: |
| ... | | ... |
| </pre> | | </pre> |
| + | The reason why we keep this information is that when we become a |
| + | society, the Society Act requires us to keep it. |
| | | |
| The possible values for Type are | | The possible values for Type are |
| | | |
- | '''Member''' - a member before we started distinguishing Voting and
| + | "Member" - a member before we started distinguishing Voting and |
- | Associate. This should never be used for new Status elements. | + | Associate. |
| | | |
- | '''Voting''' - Voting Member
| + | "Voting" - Voting Member |
| | | |
- | '''Associate''' - Associate Member
| + | "Associate" - Associate Member |
| | | |
- | '''Non''' - Past Member, i.e. no longer a member. When a person is
| + | "Non" - Past Member, i.e. no longer a member. When a person is |
| no longer a member, they're automatically ignored. So it doesn't | | no longer a member, they're automatically ignored. So it doesn't |
| matter, for instance, if they are listed as being part of a | | matter, for instance, if they are listed as being part of a |
| committee or not. | | committee or not. |
| | | |
- | '''Applicant''' - not yet a member, but wants to be. Use this when
| + | "Applicant" - not yet a member, but wants to be. Use this when |
| entering information off a new form before the board has approved | | entering information off a new form before the board has approved |
| the new member. | | the new member. |
Line 173: |
Line 92: |
| Just a reminder... the society act requires we keep track of at | | Just a reminder... the society act requires we keep track of at |
| what date members had different member status. That means you can | | what date members had different member status. That means you can |
- | not change <Status> entries. You can only add new ones. | + | not change <Status> entries. You can only add new ones. I'm |
| + | adding back the original <Status>'s that you changed. |
| | | |
- | == Committee == | + | == OpStatus == |
- | Each member can be part of one or more committees (or none).
| + | |
- | By recording the committees the member is a part of, they will automatically be added to the mailing list for that committee.
| + | |
| | | |
- | Add committees, by adding lines like:
| + | I've also added a new Field called OpStatus, for Operational Status. We aren't |
- | <Committee Name="Board" Role="President"/>
| + | required to keep a history for this, so there is only 1 line of |
| + | current information. OpStatus can be: |
| | | |
- | The currently defined committees are:
| + | "Emergency" - an Emergency Response Member |
- | * Board
| + | |
- | * Training
| + | |
- | * Membership
| + | |
- | * Preplan
| + | |
- | * Equipment
| + | |
- | * Fundraising
| + | |
- | * Audit
| + | |
- | * Caller (Call-Out Committee)
| + | |
| | | |
- | The Role is optional; it doesn't have to be included, but if stated
| + | "Resource" - a Resource Member |
- | should be one of:
| + | |
| | | |
- | board elected positions:
| + | "Non" - a Non-Responding Member |
- | * President
| + | |
- | * Vice President
| + | |
- | * Secretary
| + | |
- | * Treasurer
| + | |
- | * Secretary/Treasurer
| + | |
- | * Director
| + | |
| | | |
- | board appointed positions:
| + | I've set everyone to "Emergency" for now, as that is how we are |
- | * RCMP Liaison
| + | treating most of our members. You can change them as you get |
- | * Emergency Services Liaison
| + | updates from Jackie. |
- | * Staff
| + | |
| | | |
- | committee appointed positions:
| + | Up until just now, a member was listed as Resource Only if they |
- | * Chair
| + | are marked as CallOut="no". |
- | * Co-Chair
| + | |
| + | After our new policy last year, it should be about whether the |
| + | OpStatus is "Emergency", "Resource", or |
| + | "Non". Your e-mail has prompted me today to fix the script so it |
| + | uses OpStatus= instead of CallOut=. CallOut= is now irrelevant, and I'll remove |
| + | it before giving it back to you. |
| | | |
| == Part and Activity == | | == Part and Activity == |
Line 227: |
Line 135: |
| I'd suggest you use "Board Mtg." rather than "Reg. Mtg." to | | I'd suggest you use "Board Mtg." rather than "Reg. Mtg." to |
| distinguish the board meeting (18:00 -- 19:00) from the general | | distinguish the board meeting (18:00 -- 19:00) from the general |
- | meeting (typically 19:00 -- 19:15). | + | meeting (typically 19:00 -- 19:05). |
| | | |
- | == Activity == | + | == CallOutPriority == |
| | | |
- | <Activity> appears in the list of [[Activities]]. | + | <CallOutPriority> replaces |
- | Each line looks like:
| + | <CallOutCallerOrder>. It changes the order of people |
- | <pre> | + | with a group. I've used it to put Janet Costa ahead of Lynn Bruder |
- | <Activity Date="1995-09-21"
| + | in the Callers group. |
- | Description="mtg"
| + | |
- | Type="Admin" />
| + | |
- | </pre>
| + | |
- | ;Date
| + | |
- | : is the date of the activity.
| + | |
- | ;Description
| + | |
- | : is a description of the activity.
| + | |
- | ;Type
| + | |
- | : is the type of the activity. We track this to be able to produce different types of reports. Possible values are:
| + | |
- | :;Incident
| + | |
- | :: a call-out that we responded to. These count towards maintaining a person's SAR Fundamentals certification.
| + | |
- | :;Other Group Incident
| + | |
- | :: a call-out that the member responded to, but not as a member of PCSAR. Members can record their participation in these types of incidents to show that they are maintaining their SAR Fundamentals certification.
| + | |
- | :;Mock
| + | |
- | :: a mock incident that we attended. These also count towards maintaining a person's SAR Fundamentals certification.
| + | |
- | :;Train
| + | |
- | :: a training event other than a mock search. Organizational meetings for training (training committee meetings) aren't training; they're Admin.
| + | |
- | :;Post Incident
| + | |
- | :: activities that follow up an incident. Critiques, CISM, reviews with the tasking agency.
| + | |
- | :;Public
| + | |
- | :: public outreach and prevention events
| + | |
- | :;Social
| + | |
- | :: social events: barbeques, celebrations
| + | |
- | :;Admin
| + | |
- | :: administration activities. Anything that keeps the organization running but isn't a response or training: board meetings, preplan meetings
| + | |
- | :;Fundraising
| + | |
- | :: any activity which was to raise funds for the organization
| + | |