Personnel Database/Processing
From PCSAR
(Difference between revisions)
(→What It Does:) |
(→Future Things To Do:) |
||
| Line 18: | Line 18: | ||
[[HowToProcessMembershipDatabase]] | [[HowToProcessMembershipDatabase]] | ||
| - | ==Future Things To Do | + | ==Future Things To Do== |
| - | * Add <Solo> for solo activities, in-line with | + | * Add <Solo> for solo activities, in-line with <Part> |
| - | <Part>* Print lines in blank personnel record to be written on.* Reorder fields in printed personnel record | + | * Print lines in blank personnel record to be written on.* Reorder fields in printed personnel record |
| - | * see mail/pcsar -> 13 DF Bob Costa Oct23 Brett Wuth personnel | + | * see mail/pcsar -> 13 DF Bob Costa Oct23 Brett Wuth personnel record |
| - | + | * difference between work phone number for emergency contact and for administrative contact | |
| - | for administrative contact* Produce a report of whose first aid certification is about to | + | * Produce a report of whose first aid certification is about to expire |
| - | expire==New Things to Ask For | + | ==New Things to Ask For== |
| - | + | If you're searching the database by hand for the same | |
information over and over again, it's worthwhile to have a script | information over and over again, it's worthwhile to have a script | ||
written (by [[BrettWuth]]) to produce a report. As a rule | written (by [[BrettWuth]]) to produce a report. As a rule | ||
of thumb if you're about to do exactly the same report a second | of thumb if you're about to do exactly the same report a second | ||
time, give [[BrettWuth]] a call and let him scope out how | time, give [[BrettWuth]] a call and let him scope out how | ||
| - | difficult it would be to write a report for you. | + | difficult it would be to write a report for you. |
| + | |||
| + | If on the other hand you're doing a lot of ''different'' | ||
queries, all only once, then it would be a good idea to export the | queries, all only once, then it would be a good idea to export the | ||
data to general purpose database that has a good GUI (graphical) | data to general purpose database that has a good GUI (graphical) | ||
| - | query front-end. | + | query front-end. |
| + | |||
| + | As an aside, I already have and use a simple script that | ||
extracts just the current members from the database. | extracts just the current members from the database. | ||
Revision as of 02:46, 8 December 2008
This task is currently handled by BrettWuth. It is my intention to eventually redesign this process so it can be done by anyone.
Contents |
What It Does
Each month the database is processed to accomplish
- creates the call out list
- creates the first call list, and distributes it via e-mail
- updates the e-mailing lists (members, board, various committees)
- creates the personnel records for members whose information has changed: PersonnelRecordPrinting
- e-mails the fan out list
- e-mails the membership list to SAR Alberta
- e-mails the above documents to the MembershipCoordinator for printing and distribution
When requested, the database can be processed to
- create mailing labels
- print participation dates
How To Do It
HowToProcessMembershipDatabase
Future Things To Do
- Add <Solo> for solo activities, in-line with <Part>
- Print lines in blank personnel record to be written on.* Reorder fields in printed personnel record
- see mail/pcsar -> 13 DF Bob Costa Oct23 Brett Wuth personnel record
- difference between work phone number for emergency contact and for administrative contact
- Produce a report of whose first aid certification is about to expire
New Things to Ask For
If you're searching the database by hand for the same information over and over again, it's worthwhile to have a script written (by BrettWuth) to produce a report. As a rule of thumb if you're about to do exactly the same report a second time, give BrettWuth a call and let him scope out how difficult it would be to write a report for you.
If on the other hand you're doing a lot of different queries, all only once, then it would be a good idea to export the data to general purpose database that has a good GUI (graphical) query front-end.
As an aside, I already have and use a simple script that extracts just the current members from the database.
