Personnel Database/Processing/How To

From PCSAR

(Difference between revisions)
Jump to: navigation, search
(→personnel records =)
(→printing)
Line 160: Line 160:
** for myself
** for myself
** 4 copies
** 4 copies
-
lpr -#4 -Pofficejet-pcsar -o Collate=True outputorder=reverse run/print-queue/*CallOutList*
+
lpr -#4 -Pofficejet-pcsar -o Collate=True -o outputorder=reverse run/print-queue/*CallOutList*
* To print the print queue:
* To print the print queue:
print-queue-email-bob
print-queue-email-bob

Revision as of 19:28, 2 June 2009

Contents

How to process the membership database

Processing the database requires UNIX scripts, which I (BrettWuth) keep on my laptop. I'm migrating them to the PCSAR virtual machine.

Unless you understand UNIX, you're not likely to understand much of this. If you need to get someone else to do this, you'll need to find someone with UNIX or Linux shell skills.

The scripts check for changes in the database, so they keep a running record of the last changes they've seen. This running record is currently on BrettWuth's laptop.

The Membership Coordinator e-mails me the database as personnel-database.xml. BrettWuth is currently doing the data entry on behalf of the vacant Membership Coordinator position.


Copy my working directory from my laptop to the PCSAR only if my laptop is more up to date. 

wuth@macbook:~/sar/pc/membership$ rsync -avz . wuth@pcsar:sar/pc/membership


Merging Edits to Personnel Records

I may have made changes to my copy of the database at the same time as Bob has. The changes need to be merged.

use: 

rlog personnel-database.xml | head -20

to find out what version I gave to Bob most recently (usually latest).

check in my changes: 

rcsdiff personnel-database.xml
ci -l personnel-database.xml

for 1.18 use whatever version Bob based his changes on: 

c ~/tmp/personnel-database.xml .
rcsdiff -r1.18 personnel-database.xml

to see his changes

make my edits to his changes. 

rcsmerge -r1.18 personnel-database.xml
  • resolve any conflicts: 
rcsdiff personnel-database.xml

to verify only his changes have been propogated

validate

  • Validate Edits to Personnel Records 
 validate

(uses less) or 

validation-report

Check my marked up copy of the call out list to see any changes that may be necessary.

  • Reconcile

make any necessary changes.


check in

Update the "includes changes" date comment at start of the file: 

ci -l personnel-database.xml

Tagged Percent

  • Prepare the TaggedPercent version: 
 RecordTaggedPercentFieldsDefault -v FieldsFile=lib/RecordTaggedPercentFields.txt <tmp/personnel-database.not-validated >tmp/personnel-database.txt

copy to Brett's laptop

Because the remaining steps don't run on the PCSAR virtual machine yet, the file must be copied to Brett's laptop and run from there. 

wuth@macbook:~/sar/pc/membership$ scp -p wuth@pcsar:sar/pc/membership/personnel-database.xml .
wuth@macbook:~/sar/pc/membership$ scp -p wuth@pcsar:sar/pc/membership/tmp/personnel-database.txt tmp

call-out list

  • To print Call-out list for RCMP, FireHall, Recorder, and CallOut Coordinator
  • To Do:
  • commonize elements of {bin,lib}/{call-out,first-call} 
call-out-list-print

first-call list

  • Print and deliver copy to Fire Hall, RCMP 
first-call-list-print
  • Fax to Fire Dispatch in Lethbridge -- not done any more 
first-call-list-fax

personnel records

  • To print the individual personnel sheets: 
xslt <personnel-database.xml lib/MembersAndApplicants.xsl | changes-print recorder 
xslt <personnel-database.xml lib/MembersOnly.xsl | changes-print SARCAR
    • not RCMP because they no longer keep records

etc 

training-coordinator-send
  • Print/Send the Fan-Out list -- no longer done 
fan-out-list-send
  • Report on automatically detected policy issues: 
policy-checks-email
  • To update the pcsar-board/pcsar-preplan mailing lists: 
mailing-lists-update
  • To E-Mail to SARA: 
sara-send
  • To distribute the First Call List: 
first-call-list-pdf ~/tmp/PincherSARFirstCall.pdf

To: pcsar-firstcall@castrov.cuug.ab.ca
Subject: Pincher SAR First Call List

Hi,

Please find attached Pincher Creek Search and Rescue's (PCSAR) current
First Call List.  This list is provided for agencies that initiate
requests to PCSAR or relay those requests from other areas.

For details on PCSAR's incident notification, see:

  http://pcsar.webhop.org/emergency.html

Thank you for your participation in this process.
  • E-mail call out list: 
To: PCSAR Emergency Callers <pcsar-caller@castrov.cuug.ab.ca>,
    Pincher Creek SAR Board <pcsar-board@castrov.cuug.ab.ca>,
    PCSAR Preplan Committee <pcsar-preplan@castrov.cuug.ab.ca>
Subject: Call Out List

FYI,

Please find attached the current call-out list.

printing

  • Personnel records: 
lpr -Pofficejet-pcsar -o outputorder=reverse run/print-queue/*{recorder,SARCAR}*
  • First Call List:
    • 1 copy (for binder) 
lpr -Pofficejet-pcsar run/print-queue/*FirstCall*
  • Call Out List:
    • for binder
    • for SARCAR
    • for overhead box at firehall
    • for myself
    • 4 copies 
lpr -#4 -Pofficejet-pcsar -o Collate=True -o outputorder=reverse run/print-queue/*CallOutList*
  • To print the print queue: 
print-queue-email-bob
    • (to Bob Costa)
    • or 
print-queue-email
    • (to Roy Davidson)

Non-monthly processing

These are tasks that aren't done on a regular basis. Some of them haven't been done in long time and their instructions are now out of date.

To prepare a list of addresses and phone numbers of all our members

This was required for a casino application. 

 xslt lib/MembersOnly.xsl < personnel-database.xml |

xslt lib/NamePhoneAddress.xsl >tmp/addresses.txt

To print blank Personnel Records

  • keep 10 copies at hand 
 personnel-blank-print 10

To send call-out list via e-mail

  • NOTENOTENOTENOTENOTENOTENOTE * NOTE
  • Stop sending in September 2003* NOTENOTENOTENOTENOTENOTENOTE * NOTE 
 call-out-list-email

Call-out list to executive.

  • verify doesn't send when no change:
  • Add note about any deletions
  • automate production of

To e-mail mailing labels

  • Does not require anymore 
mailing-labels-email

Mailing Labels sent to Jackie.

To e-mail changes for Resource database

      • Stop doing October, 2003. Need another way to handle resource database 
personnel-database-mail-resource-database

When new members join, or e-mail addresses filled in

To: Subject: Welcome 
--text follows this line--
Thanks for joining Pincher Creek SAR. Can you please check if I've correctly
copied your membership record:

---cut---
---cut---

Training sessions/meetings are the first Tuesday of every month,
usually starting at 19:00.

If you'd like to join in a club discussion and receive notices
via e-mail, please send a "subscribe" message to pcsar-discuss-request@castrov.cuug.ab.ca

Take Care,Brett Wuth wuth@acm.org
wuth@telusplanet.net bwuth@cuug.ab.ca Box 1251-U, Pincher Creek,
Alberta T0K 1W0, CANADA Tel:+1 403 627-2460 pgp-public-keys@uit.no
has mine; Print=E4F8EDEECBE01AD2FA3D8B2D94B1A292 What is the meaning of life?! Yes.
<pre>
===To print the participation dates===
 xslt <personnel-database.xml Activities.xsl | awk -v FS=":" {printf "%-24s:%-7s:%s\n", $1, $2, $3 } | mail -s "activity history" `MailRCAliasAddressGet "Bob Costa"` wuth

 participation-report-make

* Add any missing entries to partitipation-type.txt

Brett Wuth, 2006/07/15 09:35 MST (via web):
Reformat the database after automatic translation using:

   xml-tidy "Training, Experience, Equipment, Notes" <personnel-database.xml >reformatted.xml
Retrieved from "http://pcsar.dyndns.org:8080/mediawiki/index.php/Personnel_Database/Processing/How_To"
Personal tools