User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "User:Machete808/WME Event Mode" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(491 intermediate revisions by 5 users not shown)
Line 1: Line 1:
WME Events Editor Guide:
<!-- ========================
Major Traffic Events, or MTEs are large-scale events that have associated road closures. MTEs can be sport events (marathons, triathlons, etc), festivals, parades, significant construction works (ex: closure of the Golden Gate Bridge), VIP visits, etc. Reporting MTEs enables better communication by alerting your local community about closures and congestion due to relevant events nearby.
    ↓  EDITS TO THIS TABLE ARE MADE BELOW THE INSTRUCTIONS    ↓
If a road closure is part of a larger event, it can now be added to the WME through the Events tool in the beta WME.
==============================
This page is only viewed directly in the Major Events table on the Closures subpage.--><noinclude>[[Category:{{RootPage2}}]]
[{{fullurl:{{BasePage2}}/Closures|action{{=}}purge}} {{u|Click here to return to the {{RootPage2}}/Closures Subpage}}]<br/>


In this first phase of the tool, you will be able to create events and upload closures through the WME, but automatic push message and website creation will still be turned off. If you have any big events that you added through the WME but want a push for, please email waze-closures@google.com with a permalink to the area and the event name and we will consider it.  
These rows fill the major Event table, and are modified using the template {{tl|Event/Item}}. If you are working on a Major Event in {{RootPage2}}, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the <code>updated=</code> parameter.


[[File:EventMode.png|right|300px|WME Modes]]To create an event:
*IMPORTANT* For a push to be sent, all event closures need to be created in the WME 48 hours in advance of the event start time.


1. Open the beta WME
This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically  the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).
2. Click the mode selection button next to the search bar.
3. Select “Event Mode”.
4. Create a new event and check the left panel.
5. Add event name in English (mandatory) - the event name should be as short as possible while accurately representing the event.
6. Add secondary event name in local language (optional) - the event name should be as short as possible while accurately representing the event.
7. Fill in details of the event. The event dates/times do not have to be when the closures start.
8. Save!!!


To create event closures:
==Accepted parameters:==
*IMPORTANT* You must be in default mode to add closures to an event. This will change in later product phases, but for now, it is the only way to add them. You can only create and edit events in events mode. All adding/editing/manipulating of other features must be in default mode.


1. Create closures as you normally would, but instead of leaving the event as “none”, you should see your event name in the drop down menu.
*<code>name=</code> The name of the event.
2. Save your closures . They will now be visible on the closures tab of the event in the event editor.
*<code>area=</code> The county or are the event takes place in.
3. Once the closures are attached to the event, go back to the event in event mode and mark it “ready for review”. Save!
*<code>date=</code> The estimated date(s) this event happens on.
*<code>road=</code> The main road(s) affected by this event.
*<code>pl=</code> A [[permalink]] to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
*<code>source=</code> A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
*<code>status=</code> Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
**<code>not submitted</code> produces a red background
**<code>submitted</code> produces a light green background
**<code>in progress</code> produces an orange background.
*Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
*<code>updated=</code> the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.


Once your event is marked as “ready for review”, somebody from the Waze closures team will review the event and decide whether to send a push message for it.
 
Once this tool is fully operational, the community will have all permissions to self manage this process.
The updated parameter (<code>|updated=YY/MM(/DD)|</code>) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).
 
 
The <code>|date=|</code>, and <code>|updated=|</code> parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.
 
 
For example an Event row should look like this;
 
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}
 
 
If there are multiple editors it should look like this
 
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}
 
 
 
'''Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box.'''
————————————————————————————————————
 
 
 
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''
 
==TO EDIT THIS TABLE CLICK HERE >> ==
</noinclude><includeonly><!--
------ DO NOT MODIFY ABOVE THIS LINE -----
======                              ======
======                              ======
======                              ======
====== DO NOT MODIFY ABOVE THIS LINE ====-->
{{Event/Item|name=New Years Celebration|area=NYC|road=Times Sq/Coney Island|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1716991474|date=12/31-01/01 annual|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}
 
{{Event/Item|name=NYC 1/2 Marathon & St. Patricks' Day Parade|date=03 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=339510355|area=NYC|road=5 Boroughs|status=submitted|updated=2017/02/09|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
 
{{Event/Item|name=July 4th Celebration|area=NYC|status=submitted|updated=2017/02/12|Rfrsw101|jdelosa|johnsninja58|PesachZ|road=FDR Dr|date=07/04 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1864894199|source=http://www.nyc.gov/html/dot/html/motorist/wkndtraf.shtml}}
 
{{Event/Item|name=Summer Streets|road=Park Ave|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1984749524|source=http://www.nyc.gov/html/dot/summerstreets/html/home/home.shtml|date=08 First 3 Sundays|area=NYC|status=submitted|updated=2017/02/10|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
 
{{Event/Item|name=West Indian Day Parade|date=09 Labor Day annual|area=Kings|road=Eastern Pkwy, Classon-Rochester St Johns-Empire|source=http://maps.nyc.gov/streetclosure/|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1605830763|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/10}}
 
{{Event/Item|name=TD 5 Boro Bike Tour|area=NYC|date=05 First Sunday annual|road=5 Boroughs|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=790135118|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}
 
{{Event/Item|name=NYC TCS Marathon|area=NYC|date=11 First Weekend annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=0|road=5 Boroughs|source=http://www.tcsnycmarathon.org/race-day/course|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/07}}
 
{{Event/Item|name=UN General Assembly|area=NYC|road=East Midtown|date=09 Last Two Weeks Annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1895099030|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}
 
{{Event/Item|name=Macy's Thanksgiving Day Parade|area=NYC|road=Herald Square|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1774745119|date=11 Last Thursday Annual|source=http://social.macys.com/parade/#route|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}
 
{{Event/Item|name=Chinese New Year Parades|date=01 or 02 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1190958434|area=NYC|road=Chinatown/8th Avenue/Flushing|status=submitted|updated=2017/02/08|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
<!--- DO NOT MODIFY BELOW THIS LINE ------=====                                =====
=====                                =====
=====                                =====
----- DO NOT MODIFY BELOW THIS LINE ----->
</includeonly>

Latest revision as of 05:15, 19 February 2017

Click here to return to the PesachZ/Closures Subpage

These rows fill the major Event table, and are modified using the template {{Event/Item}}. If you are working on a Major Event in PesachZ, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the updated= parameter.


This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).

Accepted parameters:

  • name= The name of the event.
  • area= The county or are the event takes place in.
  • date= The estimated date(s) this event happens on.
  • road= The main road(s) affected by this event.
  • pl= A permalink to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
  • source= A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
  • status= Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
    • not submitted produces a red background
    • submitted produces a light green background
    • in progress produces an orange background.
  • Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
  • updated= the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.


The updated parameter (|updated=YY/MM(/DD)|) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).


The |date=|, and |updated=| parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.


For example an Event row should look like this;

{{Event/Item|date=14/10|in progress|username|updated=14/08}}


If there are multiple editors it should look like this

{{Event/Item|date=14/10|in progress|username1|username2|updated=14/08}}


Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box. ————————————————————————————————————


The actual contents of this page will only be visible in the Major Events table, or when editing this page.

TO EDIT THIS TABLE CLICK HERE >>