1--- 2title: Survey Tool Guide 3--- 4 5# Survey Tool Guide 6 7### _News_ 8 9_2022-11-28 Updated several images and instructions to reflect improvements, such as revised menus, buttons,regional inheritance, and the Dashboard and Forum._ 10 11[**Survey Tool**](https://st.unicode.org/cldr-apps/v#locales///) **|** [**Accounts**](https://cldr.unicode.org/index/survey-tool/survey-tool-accounts) **|** [**Guide**](https://cldr.unicode.org/translation/getting-started/guide) **|** [**FAQ and Known Bugs**](https://cldr.unicode.org/index/survey-tool/faq-and-known-bugs) 12 13The Survey tool is a web based tool for collecting CLDR data and includes various features that the contributors (vetters) should know before getting started. 14 15Note that the exact appearance in screenshots may change as the tool is enhanced over time and based on your vetter level. 16 17### �� Helpful Tips 18 19- Please read the home page of the [Translation Guidelines](https://cldr.unicode.org/translation) before starting your data contribution. 20 - If you experience a **Loading...** problem with the Survey Tool, try clearing your browser cache. See [Reloading JavaScript](https://www.filecloud.com/blog/2015/03/tech-tip-how-to-do-hard-refresh-in-browsers/#.XOjGNtMzbuM). 21- **Browser support** for Survey Tool includes the latest versions of Edge, Safari, Chrome, and Firefox. 22- Use [Reports](https://cldr.unicode.org/translation/getting-started/guide#TOC-Reports) at the beginning to review the data in your language in a holistic manner for Date & time, Zones, and Numbers. 23 - Capitalization: Translations should be what is most appropriate for ”middle-of-sentence” use. So, for example, if your language normally doesn't spell languages with a capital letter, then you shouldn’t do that here. Please see [Capitalization](https://cldr.unicode.org/translation/translation-guide-general/capitalization) for more details. 24 - Plurals: For important information regarding the use of plural forms for your language, please read [Plurals](https://cldr.unicode.org/translation/getting-started/plurals). 25 26### Vetting Phase 27 28At a point towards the end of Survey Tool period, the Technical Committee will change the survey tool to "Vetting Mode". In Vetting Mode, submitting new data/translations is no longer possible, but you can still change your votes and participate in the forum. (The exception is that you can submit new data if the currently winning value has generated an error or a warning.) 29 30## Login and Import of old votes 31 321. Go to http://st.unicode.org/cldr-apps/survey/ and log in. 33 341. **Import of old votes** is automatically handled when you log in for all your votes **matching** the latest released data. If you have voted previously, upon first log-in, you will see a message showing the number of your votes that matched the currently winning votes that have been auto-imported. 352. Import of your old votes will take some time, but this will be done at 1st log-in only. 36 37 381. **Import old votes manually**. You can still import your old voted data that **DO NOT match** the last released data. 39 1. Go to the **☰ Menu**, look under **My Votes**, and choose **Import Old Votes**. 40  41 42 43 441. Scroll to the bottom to see the category selection for bulk import. 452. Select the categories that you want to import and click **Import selected items** button at the bottom. 463. Go to the data categories in the Survey tool where you have imported your old votes, these will show up in the Others column with no votes. 474. Review and add your vote. The best practice is to create a forum entry explaining why this is the data that should be changed to and drive to gain consensus with other vetters. 48 49 50### Picking Locales 51 521. On the left sidebar, you will see the CLDR locale(s). Your default view will be the languages you have permissions for. All the locales that you have permission to contribute submissions to are marked with PENCIL icon. You can view the others but not submit contributions. For example, if you have permissions to the default language Afrikaans (af), you will not have permissions to Afrikaans (Namibia), and vice versa. 53 54 55 561. Each language is followed by a list of regions that represent specific locales. The locale that is grayed out and preceded by an × is the default. The others are considered “sub-locales”. If you are working on the default locale, select the language name. For example, if you work on Spanish in general (default = Spain), you will see that that Spain is grayed out in the list below: choosing Spanish means that you are working on the default (Spanish for Spain). 57 58 59 601. Only those of you working on a specific variant language (or "sub-locale") will pick a non-default region. If you work on Mexican Spanish, pick **Mexico**. (This should already be pre-selected for you.) 61 62 63_Make sure that you haven't mistakenly turned the Information Panel off! See_ [_**No Information Panel**_](https://cldr.unicode.org/translation/getting-started/guide%23TOC-No-Information-Panel)_**.**_ 64 65### Voting view 66 671. Once you have selected your locale, more options show up in the left sidebar. (You’ll note that the sidebar only shows if you mouse over the **\>** character on the left.) 682. If the locale is relatively new and very complete, start working on the **Core Data** section and go through the rest of the sections. If the locale is mostly complete, then go to [**Dashboard**](https://cldr.unicode.org/translation/getting-started/guide) below. 693. Once you have selected a section, you'll see a table to enter votes in. The main table has these columns: 70 - **Code**: the code CLDR uses to identify this data point. 71 - **English**: the plain English value of the data point (the text you are to translate). 72 - **Abstain**: the default vote value for you. Only use abstain if you don't know a good value to be used. 73 - **A**: The value’s current status. A checkmark means it’s approved and is slated to be used. A cross means it’s a missing value. (Note, for sub-locales, a cross is not necessarily bad. If the parent locale has a good value, the sub-locale will inherit it. Check the **Winning** column.) 74 - **Winning**: this is the currently winning value. If the survey tool would close now, this is the value we would publish. If the value has a blue star next to it, that means it’s also the value that was published in the previous version. Normally it takes at least two votes from two different organizations to change value: in some locales the bar is lower, and for some items it is higher. 75 - **Add**: If the winning value is not correct and is not listed under Others, then use the plus button here to enter the correct value. If you enter a new value, your vote will be applied to it automatically. 76 - If what you want is a variation of what is in Winning or Others, you can cut & paste, and then modify. 77 - **Others**: other suggested values, not currently winning, but available to vote for. 784. Click on one of the radio buttons to make your vote. The winning status changes in real-time so depending on vote requirements and existing votes, your vote may move your desired value to the winning column right away. 79 1. Look at the Regional Variants to see if any should be changed: see **Information Panel** below. 805. Once you are done with all the sections, go to the [**Dashboard**](https://cldr.unicode.org/translation/getting-started/guide)**.** 816. Under the English column, look for "**i**" for additional information and "**e**" for an example. 82 83 84 85### Icons 86 87The main panel uses icons to indicate important information and possible problems. After clicking on the **Code** cell, look to the right-side info panel for more details. 88 89 90 91(Icons for the **Dashboard** are listed in the [**Dashboard Icons**](https://cldr.unicode.org/translation/getting-started/guide) section below.) 92 93### Examples 94 95An example with an ❌ shows a case where the pattern has an inappropriate placeholder substituted. That example should be ungrammatical; if it is grammatical, then either the translated unit or the minimal pair pattern itself is incorrect. The example will show in the Info Panel, and also if you hover over the item. 96 97### Information Panel 98 991. If you hover over an item (including the English item), a tooltip will appear showing a sample value and usage of the item in context. The item itself will have a white background; other text in context will have a gray background. 1002. When you select an item (the text, **NOT** the radio button), additional information will show in the right-hand **Information Panel**. See screenshot below. 1013. Make sure you use a wide-screen monitor and enlarge your window until you can see it, something like the image below. 1024. The box at the top shows information about the code you are translating. _It also has a link that you should click on the first type you encounter that kind of item that will explain any "gotchas"._ 1035. If there is an error or warning for the item, you see that in the middle. 1046. Below that, you'll see an example. This is the same as you get by hovering over the item in the center section. 1057. If there are votes, you'll see a breakdown of them; you also see the number of votes required to change the value. Unicode organization members usually have 4 votes; _vetters which are not representing a Unicode organization usually have 1 vote_. Your vote value and the vote value required for change will show on the right navigation for the selected item as shown in this screenshot (4 and 8 respectively in this case). 1068. Near the bottom, you'll see a pulldown menu that shows the values for different regional Variants. Here, you can quickly compare the values and go to different sub-locales to correct inconsistencies. 1079. You'll also see the New Forum Post button (as shown in the screenshot _to the right_). This is the easiest way to post discussions for the selected item. Remember that the Forum posts are at language level and not at Sub-locale level. For more information, see [Forum](https://cldr.unicode.org/translation/getting-started/guide). 10810. **No Information Panel?** 109 - If you click on the **Code** cell and there is no **Information Panel**, you may have turned it off accidentally. Click on the **Open Info Panel** button near the top right of the window. 110 111 112 113 114## Inheritance 115 116Some items are by default inherited from other places in the data. You have the option of voting for the inherited value or entering a different one. 117 118The inherited values are color coded: 119 120 121 122You can click on the link in the right sidebar to see the original value. 123 124**Note:** Voting on inheritance means "always use the inherited value, even if it changes.” An inheritance vote is advised if there are no differences in spelling conventions and political relations between your locale and the parent locale. Voting for inheritance minimizes duplication of data. 125 126### Regional Variants (also known as Sub-locales) 127 128Language variants by Region are differentiated as Parent-locale and sub-locales. For example, 129 130- **Spanish es** is the parent (or the default) locale for all Spanish locales. Its default content is for Spanish (Spain) es\_ES. 131 132- **Spanish (Latin America) es\_419** is one of the sub-locales for Spanish. Votes on inheritance will ensure that it will only contain content that is different than what is in Spanish. 133 134- **Spanish (Argentina) es\_AR** is one of the sub-locales for Spanish (Latin America). Votes on inheritance will ensure that it will only contain content that is different than what is in Spanish (Latin America) 135 136 137The regional variants menu for a data point is shown on the right navigation information pane. It will look something like the following (the exact appearance depends on the browser). 138 139When you pull it down, it will show which regional variants have different values than the main language locale. The current locale will show as darker gray as shown in the screenshot on the right. 140 141 142 143 144 145In the example in the screenshot above, Switzerland and Liechtenstein have different regional data than German (=Germany). Hover over the menu item to see the value it has. In the above diagram, you'll see "." as the decimal separator for Switzerland in the yellow hover box above as shown in the screenshot above. 146 147If any values are incorrect, please correct them. You can do that by selecting the menu item, which will take you to the same item, but in the regional locale. For example, selecting “Belgium” above goes to the decimal separator for _German (Belgium)_. You can then correct the item. 148 149Normally, the only values that should be different are in date and number formats. In some locales there are other variations: for example, German (Switzerland) spells words with “ss” instead of “ß”, so differences can occur on many different pages. 150 151### Regional Inheritance 152 153If you are voting in a sub-locale such as en\_AU, es\_MX, fr\_CA etc., you can vote to follow whatever the translation is for the locale you inherit from. You do this by voting for the translation highlighted in blue box. When you do this, you are essentially saying "**always use the inherited value, even if it changes in the source parent value**". In the screenshot below, this is the case for the vote for "inglês". If the parent value eventually changes, the value in your locale will also change. Subsequent voting in your locale could still result in having a different value than the parent locale. 154 155An inheritance vote is useful if there are no differences in spelling conventions and political relations between your locale and the parent locale. Abstaining from voting may have the same effect, but if another vetter votes for something different, your Abstained vote means that it's not opposed by you; thus, your intention is not known to others. By voting for the blue inheritance value you make your opinion known to other vetters. 156 157- Inheritance is important, to prevent data duplication. 158- Inheritance is not only limited to “sub locales”. Parent locales (or default language locales) also have inheritance from either other fields or the root. 159- By default, all data are inherited if there are no contributions. The data are indicated as Missing or Abstain. Sub-locales have inherited values that are generally from the parent locale (e.g. de\_CH will inherit values from de\_DE). 160- The inherited values appear in the **Others** column highlighted in blue box (e.g. “embu” and "inglês"). By clicking the radio button in front of those values, you are voting for inheritance. 161- If the inherited value is not correct for your locale or it’s likely for your locale to change the data in the future, click the + button, and enter a new suggestion. 162 163The vote status column will show an orange-up arrow () if the winning item is inherited and it does not have any votes. 164 165 166 167### _Progress Widget_ 168 169_There is a new style for the progress widget that shows your voting progress on the page in the upper right corner of the Survey Tool next to the Info Panel toggle. You will see details of your progress when you hover over the widget, including what progress is being measured, and the total number of items remaining for you to vote on in that category. Your progress is measured based on the coverage level you have set, so make sure that it is set correctly._ 170 171_**Note:**_ _The total progress widget is currently only visible when the dashboard is open._ 172 173### _Page progress_ 174_Progress bar shows progress of items on page for your coverage level._ 175 176 177 178### _Overall progress_ 179 180_Progress bar shows progress of items overall for your coverage level._ 181 182 183 184## Dashboard 185 186The Dashboard will show you a list of data items with warnings of different kinds. Some will require action, some may be false positives. (For the veterans, this is the redesigned Priority Viewer.) 187 188 189 190The goal is that you should work the Dashboard down to show zero items, then review the [**Reports**](https://cldr.unicode.org/index/survey-tool/guide#TOC-Reports), below. 191 192_The first priority is to fix all the_ _**Missing**_ _items by supplying the correct translations._ 193 194### Dashboard Reports 195 196Go through each of the sections to address the problems. These sections are explained below. 197 198At the top of the Dashboard is a header with a button for each section the title (such as **Missing**) and the number of items. Below that header are a series of rows. 199 200### Dashboard Columns 201 202There are six columns in the Dashboard view. 203 204- **Dashboard category**: The first letter of the section name enclosed in a circle. 205- **Data Type**: The section that the item belongs to. 206- **Code**: this links to the field in survey tool. Click on it to go to the item in the Survey Tool. 207- **English**: The English value is highlighted in blue. 208- **Winning** _**XX**_: The currently winning value is highlighted in green. 209- **Hide checkbox**: For items that can be hidden a checkbox to hide that option appears on the far right. 210 211 212 213### How to handle different categories 214 215Following are guidelines on best practices for handling items under each category in Dashboard. 216 217- **Missing** 218 - These are items where there is no localization provided by any contributor. Click on the line to be taken to the item in the Survey Tool where items are highlighted and you can add a translation. When you fix a **Missing** item it will turn to **Changed**. 219 220 221 222- **Losing** 223 - These are items that you already voted on. This indicates that your vote is not for the currently winning value. If you can live with the winning item—if it is reasonable, even if you don't think it is optimal—change your vote to be for the winning item. If not, click the **Forum** button in the **Info Panel** and give reasons for people to change their vote to what you have suggested. If not all users have voted yet, these values may still be approved before the end of the cycle. **Engage with others on the Forum discussions**. Make sure to post the reasons why others should change their votes and **respond to others’ posts**. 224- **Disputed** 225 - This is very similar to **Losing**, except in this case your vote is winning and someone else's is losing. Review all of the items to see if someone else’s item is better and read the forum post, and whether you want to change your vote. Discuss in the forum, then use the Hide button to hide disputes you’ve addressed in the forum. 226- **Changed** 227 - The Changed count is provided in the Dashboard only as a reference. The **Changed** items are either: 228 - Missing items now have a value. 229 - The Winning value of the translation has been changed. 230- **English Changed** 231 - These are items where the English source has changed after the last change in your language. Items that are listed in this section indicates that you need to re-check them and assess the impact to your language and update as appropriate. (Some English changes will have no impact to translations.) 232- **Warnings** 233 - These are issues which appear after automatic checks. (For examples, a message could be "_The value is the same as English"_, which is a quite common warning for languages that are close to English in the spelling of languages or territories. If the value is actually ok, then click on the Hide button (crossed eye). If not, then vote for a fix, or post on the Forum for discussion. 234 235 236 237### Dashboard Summary 238 239There are two ways to clear items from the **Dashboard** list: 240 2411. Fix them (such as adding a translation for a missing item) 2422. Hide them (such as when the English has changed but the translation doesn’t need to change). 243 - _**Only**_ _hide items if it really is a false positive,_ _**not**_ _because you gave up on fixing it…_ 244 - _If you hide an item by mistake:_ 245 - _Unhide all the lines with the top eye button._ 246 - _Click on the orange eye button in the line (a “Show" tooltip will appear)._ 247 - _Hide all the lines again by clicking the top eye button._ 248 249 250## Reports 251 252The reports show lists of items that need to be reviewed for consistency. You should look through these after you do the **Dashboard** to make sure that the items are consistent, when viewed in the context of others. Each of them has a link to instructions at the top. Please read these before continuing. 253 254Reports are under the left navigation. 255 256Reports are a good way to review the data in your language in a wholistic view for the Date and time, Zones, and Numbers. 257 258 259 260_Example:_ 261 262 263 264## Special cases 265 266**You may not make changes to this locale** 267 268You may see a message like the following when trying to modify a regional locale, like pt-BR. 269 270 271 272→ 273 274 275 276The reason that Brazil is grayed out is that it is the default content locale for Portuguese. So to modify pt-BR, you need to simply click on Portuguese. If you do click on Brazil, you will get to a page with the following at the top. Clicking on [default content locale](https://cldr.unicode.org/translation/translation-guide-general/default-content) will explain in more detail. 277 278 279 280### 20 vote items May not be modified 281 282Some items have change protection in place that will stop vetters from changing it, but you can still advocate a change. This is indicated by the message "May not be modified-see details" as shown in the screenshot below, or that the threshold for changing the value is 20 votes, instead of the usual 8 or 4. This indicates that the item is particularly sensitive to data instability and has a broad impact. Changes to these items require Technical Committee review. To suggest a change, you have to "flag" the value. 283 284 285 286To change it, you have to flag the item for committee review: 287 2881. Click on the “**Flag for Review button**”. 2892. On the new page, you'll see a message box. 2903. Enter the change that you want to make, and add a justification for changing it. 2914. Then click **“Post**”. 2925. Towards the end of data collection cycle, the Technical Committee will review the change request and either accept it, or reject it with comments. 293 294Note: The **Flag for Review** button will be available only when the item has a 20 vote value AND there is a suggestion in the **Others** column. 295 296## Forum 297 298Forum is the place to discuss and collaborate with other vetters on questions and issues in your language. The forum is at Language level and not at sub-locale level; if you are talking about a translation in a sub-locale, be sure that you are clear about that. 299 300It's a best practice to **create a Forum post whenever you propose a change to a previously approved value**, and provide an explanation and links to references. 301 302### Forum Etiquette 303 304While creating New Posts on Forum or participating in discussions please follow these general etiquette guidelines for best productive outcomes: 305 306- Be professional. Provide accurate, reasoned answers so that other participants can easily understand what you are talking about. 307- Be courteous. Refrain from inappropriate language and derogatory or personal attacks. 308- Don’t “SHOUT”; that is don’t use all capitals. 309- In case of disagreement, focus on the data and provide evidence to support your position. Avoid challenges that may be interpreted as a personal attack. 310- Be prepared to have your own opinions challenged or questioned, but don’t take answers personally. 311- It’s possible that participants have different expectations on the intent of the data. Clarify what you think is the intent may help especially if disputes continue. 312- Remember that open discussion is an important part of the process; abiding by these guidelines will encourage active participation by all vetters and a better end result. 313 314### Forum Workflow 315 316Forum posts work with the following workflow: 317 3181. Create a new **Request** 3192. Responses by other vetters in your language with Agree, Decline, or Comment. 3203. Once resolved, the creators of the the initial Request or Discuss closes the post. 321 322 323### How to create a new forum post 324 325A forum post can be specific to a particular data point or a general issue. In either case, create a new forum post to an item. 326 327- A post that is specific to a particular data point. 328- A general issue that impacts multiple data points. In a general case that impacts multiple data points, you do not need to post new forum posts for every item impacted. The general issue should be flagged to other vetters and once a consensus is reached, it is expected that vetters update their votes on all impacted items. New forum posts can be used to flag to other vetters if others fail to update their votes on all impacted items. ONLY request if others have missed or have not updated consistently. 329 330 331**Create forum posts from the** [**Information pane**](https://cldr.unicode.org/translation/getting-started/guide#TOC-Information-Panel)**l in the voting window.** 332 3331. Vote on an item (or add new +) for the item you want to suggest changing. 334 335 336 3372. In the Information panel on the right, there are two buttons to indicate the type of forum posts: 338 1. **Request** You have voted on a non-winning item, and you want to Request others to change their votes. 339 2. **Discuss -** Currently only TC members can make discuss posts. 340 3413. Click **Request** button and fill out the details of your request. (Note: The **Request** button is disabled unless you have voted) 342 343 344 345**Request** 3461. A precomposed text is included to help start your post. **Important!: Request works WITH the item you voted for currently.** 3472. _Please consider voting for “{your voted-value}”. My reasons are:_ Complete the text by filling out your reasons and links to references. 3483. Then **Submit.** 349 350 351 352### Responding to Request posts 353 354There are two ways to respond to forum posts: 355- Info Panel (This is the recommended option.) 356- In the Forum view (See [Working in the Forum view](https://cldr.unicode.org/translation/getting-started/guide#TOC-Working-in-the-Forum-view-)) 357 358**Respond from the** [**Info Panel**](https://cldr.unicode.org/translation/getting-started/guide#TOC-Information-Panel) **in the voting window.** 359 360In the **Info Panel**, select the **Comment** button 361- Each posted response is labeled in Red and its response type: Agree, Decline or Comment. 362 363 364 365**Choosing your Response:** Vote, or Comment 366 3671. When you make a vote on an item that already has a Request post by another vetter, then an Agree or Decline post will be made for you automatically. If you agree with the reasons for change, you don't need to add more explanations for agreeing. 3682. An **Automated** _**Agreement** will be posted if you vote for the requested value. Your agreement will be automatically posed with a precomposed reply_: I voted for “{requested-value}” 369 370 371 3723. **Comment:** Use this option if you do not Agree or Decline, and you have other input to bring to the discussion or if you want to ask for more information. 373 374### Responding to Discuss posts 375 376There are two ways to respond to new forum post: 377- Info Panel (This is the recommended option.) 378- In the Forum view (See [Working in the Forum view](https://cldr.unicode.org/translation/getting-started/guide#TOC-Working-in-the-Forum-view-)) 379 380 381**Respond to forum posts from the** [**Info Panel**](https://cldr.unicode.org/translation/getting-started/guide#TOC-Information-Panel) **in the voting window.** 3821. In the Info Panel click the **Comment** button and add your input to the open discussion. 3832. The label **Discuss** in Red indicates that this is a Discuss post (to distinguish from Request posts) 384 385 386 387### Working in the Forum view 388 389In the Survey Tool [Forum](https://st.unicode.org/cldr-apps/v#forum/fr//) view, there are multiple filtering options available for you to work more effectively. 3901. The Forum view can be accessed from the left navigation **Forum.** 391 392 393 3942. By default, the filter is for **Needing action**. 395 396 397 3983. Filter options: 399 - **Needing action**: Forum posts included in this filter are Requests and Discussion posts by someone in your language. You have not yet taken action on either agreed or declined or posted a discussion asking for additional information. For Discussion posts, these are where you are not the last poster. 400 - **Open requests by you**: Forum posts included in this filter are Requests that you have posted that you have not closed yet. 401 - **All Open topics**: All posts that are open. This includes both Request and Discussions that have not closed yet. 402 - **All topics:** All topics, open or closed, including forum posts from previous releases. 403 - Note that Forum posts that were active in previous releases will be marked as Closed at the start of a new Survey tool cycle. 404 405**Respond to forum posts in the Forum view** 406 407In the Forum view, you can respond to Request and Discuss posts. 408 409For **Request posts**, you can select your decision using the 3 available buttons: **Agree, Decline, Comment.** 410 411See [Responding to Request posts in Information Pane](https://cldr.unicode.org/translation/getting-started/guide#TOC-Responding-to-Request-posts). 412 413 414 415## Reporting Survey Tool issues 416 417If you run into a problem with the Survey Tool functionalities, please see [FAQ & Known Bugs](https://cldr.unicode.org/index/survey-tool/faq-and-known-bugs) to see whether it has already been reported (and whether there is a work-around). If not, or if you have suggestions for improvements, please file a bug using the Feedback link at the bottom of each window. If you encounter problems or have enhancement suggestions for the survey tool, please [file a ticket](https://cldr.unicode.org/index/bug-reports#TOC-Filing-a-Ticket). 418 419 420 421**Email notification** 422 4231. Another way to check for posts that may need your attention is to review email notifications to the e-mail account for your locale. You can delete these notifications if they are for changes initiated by you. You can open the post directly from a link in the email. 4242. When you make a forum entry, it will be emailed to all other linguists working on locales with the same language, parent or sub-locale (i.e. **forum is at Language level and not at sub-locale level**). If you are talking about a translation in a sub-locale, be sure that you are clear about that. 425 426 427### Forum posts for CLDR ticket feedback 428 429CLDR users can send in data feedback using [JIRA](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md). Tickets filed in JIRA will be processed as described below. Please expect to see posts by CLDR Technical Committee members (TCs) in Forums, and participate by providing your response to any tickets needing your input. 430 431The goal is to bring it to the attention to all linguists contributing in a particular language, and gather their input, so an informed decision can be made and/or suggested. 432 4331. CLDR TC members accept JIRA tickets. 4342. For each ticket assigned to them, the TC member will post a forum topic in each language mentioned in the ticket, asking for vetters to look at the issue and either make the requested change, or explain in a forum post why changes should not be made. 4353. A reason for not changing could be for example that it is a reasonable change, but doesn't exceed the 'stability' bar in the translation guidelines. 4364. TC members will monitor the forum discussion/change during the Submission phase, and will close the JIRA ticket after the forum discussion is concluded. 437 438 439## Advanced Features 440 4411. Users familiar with CLDR XML format can upload votes (and submissions) for multiple items at once. See [**Bulk Data Upload**](https://cldr.unicode.org/index/survey-tool/bulk-data-upload)**.** 4422. Organization managers can manage users for their organization (add, remove, send passwords, set locales, etc.) For more information, see [**Managing Users**](https://cldr.unicode.org/index/survey-tool/managing-users)**.** 443 1. Some users may want to reset their Coverage Level, with the menu that looks like the image to the right. 444 2. The Coverage Level determines the items that you will see for translation: the minimal level has the highest priority items. You normally start with the level marked "Default" (which will vary by your organization and locale). Each successively higher level adds more items, at successively lower priorities. You will not normally go beyond "Modern", unless you have special instructions for your organization. 445 3. _Note that some companies won't use the data until it is complete at a certain coverage level, typically_ _**Modern**._ 446 447
