Difference between revisions of "Creating a new community PWL"

From InfoEx Help Information
Jump to navigation Jump to search
(Created page with "__NOTOC__ {{Requirements|UserLevel=Operation administrator and higher|Connectivity=Online}} This document describes how to create a community PWL in the infoex system. ==Back...")
 
(Step-by-step description)
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
{{Requirements|UserLevel=Operation administrator and higher|Connectivity=Online}}
+
{{Requirements|UserLevel=Submission moderator and higher|Connectivity=Online only}}
 +
 
 +
This document describes how to create a new [[Definitions#CommunityPWL|community PWL]].
  
This document describes how to create a community PWL in the infoex system.
 
 
==Background==
 
==Background==
A community PWL is a defined snowpack layer that applies to multiple operations. The dating, description and name of the PWL is common to the entire infoEx community.
+
Since [[Definitions#PWL|PWLs]] often exhibit significant spatial variability and might be buried on a range of days, individual operations might create their [[Definitions#OperationPWL|Operation PWLs]] differently. Community PWLs provide a mechanism for linking operation controlled Operation PWLs that relate to the same PWL in nature. This grouping of Operation PWLs allows for more meaningful queries. For example, the community PWL functionality will allow users to more efficiently get a comprehensive picture on the assessments of a PWL that covers a large area and effectively visualize the associated observed avalanche activity.
  
The following information assumes you are logged in to the InfoEx application and you have selected an operation (if you have more than one valid operation).
+
{{Note|Please note that the avalanche problem/PWL filtering functionality for taking full advantage of PWL information in reports has not been implemented yet!}}
  
 
==Step-by-step description==
 
==Step-by-step description==
Line 12: Line 13:
 
|-
 
|-
 
|class="StepNum" | 1.
 
|class="StepNum" | 1.
|Activate the PWL menu from the main infoEx menu.
+
|[[File:CreateCommunityPWL.png|300px|thumb|right|Fig. 1: Accessing the Community PWL menu]] Click on the PWL menu and select 'Community PWL'(Fig. 1). This will get you to a page that lists of all of the Community PWLs that have been created by the community.  
 
|-
 
|-
 
|class="StepNum" | 2.
 
|class="StepNum" | 2.
|[[File:CreateCommunityPWL.png|300px|thumb|right|Fig. 1: Creating a community PWL]]Select 'community PWL' beneath 'Pwl' (Fig. 1). The current list of community PWLs is displayed.
+
|[[File:CommunityPWLSetting.png|300px|thumb|right|Fig. 2: Community PWL settings]]Click on the [[file:ButtonAdd.png]] button beneath the 'Community PWL' title to open a pop-up window where you can provide the baseline information for your new Community PWL (Fig. 2).
 +
 
 +
Provide the following baseline information for your new Community PWL:
 +
* '''Name'''<br/>A meaningful name for your new Community PWL.
 +
* '''Date'''<br/>A rough formation/burial date for your new Community PWL. This date is only used for sorting the list of community PWLs.
 +
* '''Description'''<br/>A descriptive comment about your new Community PWL, if desired.
 +
* '''Operation PWLs'''<br/>The drop down list of this field lists all of the Operation PWLs that have defined by InfoEx subscribers. Select any Operations PWLs that you believe are linked to the PWL that this Community PWL represents.
 +
* '''Colour'''<br/>A default colour that will identify any assessments and observations associated with this Community PWL in the InfoEx report.
 
|-
 
|-
 
|class="StepNum" | 3.
 
|class="StepNum" | 3.
|[[File:CommunityPWLSetting.png|300px|thumb|right|Fig. 2: Community PWL settings]]Select [[file:ButtonAdd.png]] beneath the 'Community PWL' title. This will open a popup window where you can provide the baseline information for your Community PWL.
+
|Click on {{ButtonGrey|Okay}} to submit.
|-
 
|class="StepNum" | 4.
 
|Provide the following information for your Community PWL (see Fig. 2)
 
{|class="TblSteps"
 
|-
 
|class="StepNum" | Name:
 
|Provide a meaningful name for your Community PWL.
 
|-
 
|class="StepNum" | Date:
 
|Provide the date that your Community PWL was buried.
 
|-
 
|class="StepNum" | Comment:
 
|Provide a descriptive comment for your Community PWL, if desired.
 
|-
 
|class="StepNum" | Operation PWL:
 
|You may link your Community PWL to all relevant Operation PWLs (see: [[Operation PWLs]])
 
|-
 
|class="StepNum" | Colour:
 
|Provide a colour that will identify your PWL in hazard assessments.
 
|}
 
 
|}
 
|}
 +
 +
{{Note|At this point any user with Submission Moderator permissions can manage Community PWLs. However, once the necessary filtering functionality is available, the idea is that Avalanche Canada would be taking the lead in managing the Community PWLs as they are in the best position to assess large scale patterns. However, operators always have the ability to unlink their Operation PWLs from a specific Community PWLs if they disagree with the grouping.}}
  
 
==Related documents==
 
==Related documents==
* [[Operation PWLs]]
+
{{PagesPWLs}}
* [[Persistent weak layer overview]]
 
  
 
==Functionality tested by==
 
==Functionality tested by==
* Date: Nov. 30, 2013 / John Kelly / QA Server / Version 3.0.0
+
* Jan. 2, 2014: Pascal Haegeli
  
[[Category:PWL]]
+
[[Category:Super User]][[Category:Operation Administrator]][[Category:Submission Moderator]]
 +
[[Category:PWL]][[Category:Version 3.4.0]]

Latest revision as of 14:03, 31 May 2017

REQUIREMENTS
Permission Submission moderator and higher
Connectivity Online only

This document describes how to create a new community PWL.

Background

Since PWLs often exhibit significant spatial variability and might be buried on a range of days, individual operations might create their Operation PWLs differently. Community PWLs provide a mechanism for linking operation controlled Operation PWLs that relate to the same PWL in nature. This grouping of Operation PWLs allows for more meaningful queries. For example, the community PWL functionality will allow users to more efficiently get a comprehensive picture on the assessments of a PWL that covers a large area and effectively visualize the associated observed avalanche activity.

NOTE Please note that the avalanche problem/PWL filtering functionality for taking full advantage of PWL information in reports has not been implemented yet!

Step-by-step description

1.
Fig. 1: Accessing the Community PWL menu
Click on the PWL menu and select 'Community PWL'(Fig. 1). This will get you to a page that lists of all of the Community PWLs that have been created by the community.
2.
Fig. 2: Community PWL settings
Click on the ButtonAdd.png button beneath the 'Community PWL' title to open a pop-up window where you can provide the baseline information for your new Community PWL (Fig. 2).

Provide the following baseline information for your new Community PWL:

  • Name
    A meaningful name for your new Community PWL.
  • Date
    A rough formation/burial date for your new Community PWL. This date is only used for sorting the list of community PWLs.
  • Description
    A descriptive comment about your new Community PWL, if desired.
  • Operation PWLs
    The drop down list of this field lists all of the Operation PWLs that have defined by InfoEx subscribers. Select any Operations PWLs that you believe are linked to the PWL that this Community PWL represents.
  • Colour
    A default colour that will identify any assessments and observations associated with this Community PWL in the InfoEx report.
3. Click on Okay to submit.
NOTE At this point any user with Submission Moderator permissions can manage Community PWLs. However, once the necessary filtering functionality is available, the idea is that Avalanche Canada would be taking the lead in managing the Community PWLs as they are in the best position to assess large scale patterns. However, operators always have the ability to unlink their Operation PWLs from a specific Community PWLs if they disagree with the grouping.

Related documents

Operation PWLs

Community PWLs

Assessing PWLs

Functionality tested by

  • Jan. 2, 2014: Pascal Haegeli