Changes between Version 14 and Version 15 of BluePrintCERT/RHoK2011
- Timestamp:
- 11/28/11 23:09:19 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrintCERT/RHoK2011
v14 v15 32 32 1c. Some of the students are already AED / CPR certified, so Joe also creates qualification for that. The students will send Joe a copy of their certification which he will then attach to their profile. 33 33 34 35 34 [[Image(AddQualification2.png)]] 36 35 37 1c. Joe willenters (or import) a list of the students in the class. If they already exist in the volunteer database, the class is added to their existing profile. If they do not exist in the database, a new volunteer record is created.36 1c. Joe then enters (or import) a list of the students in the class. If they already exist in the volunteer database, the class is added to their existing profile. If they do not exist in the database, a new volunteer record is created. 38 37 39 38 1d. Determining which volunteers have completed all the requirements for a given qualification will be refreshed on a non-configurable time interval or forced by selecting "Refresh All Qualifications" on the Qualifications page. 40 39 41 [[Image( ShowQualifications.png)]]40 [[Image(ViewQualifications.png)]] 42 41 43 42 1e. When volunteers first complete all the required classes for Basic Training, their status is changed from "Pending" to "Active" and are eligible for additional call-outs and training. … … 45 44 === Sample volunteer profile pages === 46 45 46 The info page is pretty straightforward. The "text" checkbox indicates that the volunteer can receive SMS messages at that number. The "Contact Lists" indicate what types of communications this volunteer will receive from CERT. I'm signed up for everything, but if I wanted to stop receiving notifications about drills I would be removed from the "Drills" contact list. 47 (TODO: preferred method of communication) 48 47 49 [[Image(VolunteerProfile_Info.png)]] 50 51 The qualifications and level boxes (from left to right, level 1, 2 and 3) are pulled from the qualifications database. The notes and attachments are part of the volunteer's profile. The paperclips indicate an an attached file with verification of that qualification. 48 52 49 53 [[Image(VolunteerProfile_Qualifications.png)]] 50 54 55 This is just a list of the events in which the volunteer has participated. In the future we'd like to be able to filter by event type. 56 51 57 [[Image(VolunteerProfile_Participation.png)]] 52 58 59 This is where CERT leadership can make notes that are important or helpful for an incident commander. The information on this page will be added to the volunteer roster that is sent to the incident commander, and instructions on the appropriate types of things to write in this area will be part of our SOP. 60 53 61 [[Image(VolunteerProfile_Notes.png)]] 62 63 This is a read only page that indicates which past deployments the volunteer has responded to at what his / her response was. 54 64 55 65 [[Image(VolunteerProfile_Events.png)]] … … 62 72 [[Image(AddDeployment.png)]] 63 73 64 By default all Active members are shown in the recipient list who are assigned to the appropriate contact list. For instance, if sending a deployment for a Training event, only volunteers who belong to the "Training" contact list will be shown in the recip eient list. The list can be further filtered by selecting "Restrict recipients by qualification" and using multi-select to choose.74 By default all Active members are shown in the recipient list who are assigned to the appropriate contact list. For instance, if sending a deployment for a Training event, only volunteers who belong to the "Training" contact list will be shown in the recipient list. The list can be further filtered by selecting "Restrict recipients by qualification" and using multi-select to choose. 65 75 66 76 The deployment notice is a standard template. Joe wants to edit before sending so he selected "Edit Request Before Sending" to bring up the preview pane. He adds a couple of notes and select "Send Deployment" 67 77 68 [[Image(AddDeployment _WithPreview.png)]]78 [[Image(AddDeploymentWithPreview.png)]] 69 79 70 80 Here is a flow chart of the whole deployment process:
