Difference between revisions of "Modifying the information for an existing community PWL"

From InfoEx Help Information
Jump to navigation Jump to search
(Step-by-step description)
(Step-by-step description)
Line 19: Line 19:
 
|-
 
|-
 
|class="StepNum" | 3.
 
|class="StepNum" | 3.
|[[File:CommunityPWLSetting.png|300px|thumb|right|Fig. 2: Community PWL settings]]Click on the [[file:ButtonEdit.png]] button beneath the 'Community PWL' title to open a pop-up window where you can modify the information for Community PWL (Fig. 2).
+
|[[File:CommunityPWLEdit.png|300px|thumb|right|Fig. 2: Editing the information for a Community PWL]]Click on the [[file:ButtonEdit.png]] button beneath the 'Community PWL' title to open a pop-up window where you can modify the information for Community PWL (Fig. 2).
  
 
Provide the following baseline information for your new Community PWL:
 
Provide the following baseline information for your new Community PWL:

Revision as of 07:40, 3 January 2014

REQUIREMENTS
Permission Operation administrator and higher
Connectivity Online

This document describes how to modify the information of a community PWL in the InfoEx system.

Background

Community persistent weak layers (Community PWLs) is a new concept in the InfoEx system. 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 in the InfoEx. 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 taking full advantage of PWL information the InfoEx report has not been implemented yet!

Step-by-step description

1.
Fig. 1: Accessing the Community PWL menu
Click on the PWL menu in the header of the InfoEx application 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. Highlight the Community PWL you would like to edit by clicking on it in the list. The row of the selected PWL will be highlighted in a pale yellow.
3.
Fig. 2: Editing the information for a Community PWL
Click on the ButtonEdit.png button beneath the 'Community PWL' title to open a pop-up window where you can modify the information for Community PWL (Fig. 2).

Provide the following baseline information for your new Community PWL:

  • Name
    A meaningful name for your Community PWL.
  • Date
    A rough formation/burial date for your Community PWL. This date is only used for sorting the list of community PWLs.
  • Comment
    A descriptive comment about your 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. To delete a Operation, click on the ButtonDelete.png button in the label of a chosen Operation PWL to delete from the list.
  • Colour
    A default colour that will identify any assessments and observations associated with this Community PWL in the InfoEx report.
3. Click on the Okay to submit the changes for the Operation PWL to the InfoEx system.
NOTE At this point any user with Submission Moderator permissions can create Community PWLs. However, once the necessary filtering functionality, the idea is that the CAC would be taking the lead in managing the Community PWLs that they are in the best position to assess large scale patterns. However, operators always has 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