Process for Organizations to Join the System

[GoogleCodeExporter]

1. Visit Home Page.
2. Click Link to "Join"
3. Chose the Incident/ Disaster
    3.1 Choose an existing Incident/Disaster
    3.2 If the disaster is not in the database, they can choose, "Request Creation of an Incident/Disaster."  Collect the * Incident Name (E.g. "Hurricane Sandy"; "Colorado Wildfires"; "Dodge City Tornado") and * Approximate Location (E.g. "Eastern Seaboard"; "Larimer County, CO"; "Dodge, KS")
4. If 3.1 is TRUE, Check to see whether their organization is already 
participating by browsing a list of organizations already participating.
    4.1 If the person finds his/her organization, click, "Join as this organization."
    4.2 If not, click "Join as a new organization."
5. Fill out Organization Application (See Issue 138). If 4.1 is TRUE, then only 
personal contact information is entered during the application process. The 
other organizational information is displayed, but not editable.
    5.1 Administrator approves, rejects, or asks for additional information.
6. Administrator Approval of New Organization
    6.1 Administrator receives an email, evaluates the application and approves assuming that the applicant doesn't look fake.
    6.2 If 4.1 is true, then no administrator approval is necessary. Approval (or absence of disapproval) occurs at step 7.1.
7. Confirmation
    7.1 If 4.1 is TRUE, an email is sent to all existing members of the organization offering them a 36-hour right of refusal; or they may approve the person via a link.  The individual is notified who received the right-of-refusal/approval link.
    7.2 If 7.1 occurs, and the 36 hour period expires without action by the existing members, then the person is automatically sent organization credentials.
    7.3 If 7.1 occurs, and the existing member clicks the link to refuse entry to the system, then a confirmation email is sent to member who clicked, the new applicant, and the other members who received the email with the right of refusal, and the administrator, informing them of the refusal, and including all relevant contact information for all parties involved.  The email should include a link, "If this refusal was in error, click this link to allow [Applicant's Name] to be a point of contact for [Organization's Name] within the Collaborative Work Order System."
    7.4 Else, a password comprised of 2-3 randomly chosen words and 3-4 randomly chosen numbers is assigned and sent (in plain text email) to applicant.

Original issue reported on code.google.com by v...@aarontitus.net on 13 Jan 2013 at 11:12

[GoogleCodeExporter]

Is this the only way we should leave open to create a new Incident? We could 
also make sure that you (or an admin) can create an incident before an 
organization suggests it.

That way, we can be a little more proactive in deciding which incidents to 
target.

I'll complete as described above first. We can add the new way without too much 
trouble another time.

Original comment by andy.n.g...@gmail.com on 22 Jan 2013 at 12:01

[GoogleCodeExporter]

I did not mean to imply that this is the only way to create an incident. The 
Admin should be able to create an incident at any time.

Original comment by v...@aarontitus.net on 22 Jan 2013 at 12:41

[GoogleCodeExporter]

Ok, I have nearly finished allowing a user to create an incident, and an 
organization, using the request forms as described in issues 138 and issue 14.

I am going to create an admin panel next, so an admin can review these 
requests, as well as add new ones. After that is done, I am going to change the 
authentication page, so that the logic follows what was written above.

Original comment by andy.n.g...@gmail.com on 22 Jan 2013 at 1:47

[GoogleCodeExporter]

Note: For Item 3.1, one option should be "None." This will allow organizations 
to join in Peacetime, familiarize themselves with the system, and automatically 
sign up for the special "Test" Incident.

Original comment by v...@aarontitus.net on 25 Jan 2013 at 8:59

[GoogleCodeExporter]

Implemented. On sign in page, click Add Organization.

Admin can verify.

Original comment by andy.n.g...@gmail.com on 17 Feb 2013 at 4:32

[GoogleCodeExporter]

Yes, minimally implemented.
Items 3.1, "None" not yet implemented. 
Question: Is the duplicate validation in Item 4.1 and 5 implemented?
Item 6.1 email not implemented.
Logic in 7 is not implemented yet.

Original comment by v...@aarontitus.net on 21 Feb 2013 at 7:52