**NOTE**: The only action required here is for the items in bold, plus "Migrate “Classic ORES” users to New Filters ORES"
-----
When we move users to the New Filters (either in beta or because the new UX graduates to standard), all user preferences will be migrated. This ticket explains the requirements for this process. The ticket also details how particular preference settings in the old system translate to the new one. These translation details come into play in tall the subtasks that belong to parent task T172350.
=Requirements
- {icon check-square color=green} The current default settings for WL and RC will be translated and established as defaults in the new UX (see Current Default Settings below).
- {icon check-square color=green} When a user moves to the New Filters UX, all user preferences from the old system will be transferred to their equivalents in the new UX for that user (see below, under "Preference Conversions" for details about equivalency).
- {icon check-square color=green} When New Filters users bookmark settings to the Saved Filters menu, and declare those settings Default (using the "Set as default" option), the default on-page settings override any existing page preferences that were set on the Preferences pages.
- Many existing user preferences will no longer be visible on the consolidated "Change Monitoring" preference page (as detailed in the subtasks of T172350). However, all such hidden preferences will be stored for each user.
- {icon check-square color=green} In the event a user opts out of the New Filters on RC or WL or both, all their old preferences, including the hidden ones, will be restored. (Their OLD preferences will be restored; i.e., we don't need to send on-page defaults "upstream" to be stored as hidden preferences).
=Current Default Settings
The following are the existing default preferences for RC and WL. The preferences here are described as they will be implemented __in the New Filters UX,__ except for those that do not exist in the new UX and will continue to be presented on the Preferences page.
====Recent Changes
- 7 days, 50 results.
- Active filters = Logged edits, page creations, page edits, human (not bot)
====Watchlist ( existing defaults)
- 3 days, 250 maximum results
- Active filters: Latest revision, Logged edits, page creations, page edits. [Note: unlike RC page, “Human (not bot)” is NOT a default]
- Active WL pref page options: "Add pages I create and files I upload to my watchlist", "Add new files I upload to my watchlist"
====Pending Changes
Currently shown on the RC Page prefs, but not really an RC Page pref. In new system, shown in its own section.
- Active page prefs: "Use small icons and minimal text to show review status of pages", "Use the default settings for each page".
=Preference Conversions
This section spells out how old-style preferences will be realized in the new UX
==Recent Changes preference setting translations (non-ORES)
- Group changes by page in recent changes and watchlist: this setting has been divided, so we need to set it for both WL and RC separately in the new UX.
- {icon check-square color=green} Hide minor edits from recent changes = add “Non-minor edits” filter to defaults.
- {icon check-square color=green} Hide categorization of pages = This is a current default. See "Current Default Settings" above. If UNCHECKED, add “category changes” filter to defaults.
- {icon check-square color=green} Show Wikidata edits by default in recent changes and watchlist = add “Wikidata edits” to defaults. !![ Not sure what to do here: this says this setting works on Watchlist and RC page, but there is ALSO a preference for Wikidata on Watchlist. So try your best to figure out how these two settings actually interact, and reproduce as best as possible]!!
- “Number of edits to show in recent changes, page histories, and in logs, by default:” -- Apply setting to “changes to show” control on RC page AND to new “Number of edits to show” section of Preferences .
- “Days to show in Recent Changes”--apply setting to Recent Days control on RC page .
==Watchlist settings migration (non-ORES)
- {icon check-square color=green} Expand watchlist to show all changes, not just the most recent = if checked, remove “Latest revisions” from default filter set (see above).
- {icon check-square color=green} Hide minor edits from the watchlist = if checked, add “Non-minor edits” filter to defaults.
- {icon check-square color=green} Hide bot edits from the watchlist = if checked, add “Human (not bot)” filter to defaults.
- {icon check-square color=green} Hide my edits from the watchlist = if checked, add “Changes by others” filter to defaults.
- {icon check-square color=green} **Hide edits by anonymous users from the watchlist = if checked, add “Registered” filter to defaults. **
- {icon check-square color=green} **Hide edits by logged in users from the watchlist = if checked, add “Unregistered” filter to defaults. **
- {icon check-square color=green} Reload the watchlist automatically whenever a filter is changed = no action required. Ignore.
- {icon check-square color=green} Hide categorization of pages = this is a current default. See "Current Default Settings" above. If UNCHECKED, add “category changes” filter to defaults.
- {icon check-square color=green} Show Wikidata edits in your watchlist-- if checked, add Wikidata edits” filter to defaults.
- “Maximum number of changes to show in expanded watchlist” -- apply setting to “changes to show” control
- “Days to show in watchlist”--apply setting to Recent Days control.
==Migrate “Classic ORES” users to New Filters ORES
{icon exclamation-triangle color=red} The Revision Scoring (ORES) settings will be translated to the new UX in the following way for both Recent Changes and Watchlist. The Prediction Threshold setting determines which filters and highlights apply.
====Prediction Threshold = “May have problems”
- **If “Highlight likely problem edits” only is checked**
- Apply highlights as follows, May have problems = yellow; Likely have problems = orange; Very likely have problems = red.
- **If “Show only likely problem edits” only is checked (i.e., no highlighting)**
- Activate filter, May Have Problems (only)
- **If BOTH options are checked**
- Activate filter, May Have Problems
- Apply highlights Likely have problems = orange; Very likely have problems = red. (i.e., no highlight for May).
====Prediction Threshold = “Likely have problems”
- **If “Highlight likely problem edits” only is checked**
- Apply highlights as follows, Likely have problems = orange; Very likely have problems = red.
- **If “Show only likely problem edits” only is checked (i.e., no highlighting)**
- Activate filter, Likely Have Problems.
- **If BOTH options are checked (highlighting and filtering)**
- Activate filter, Likely Have Problems.
- Apply highlights as follows: Very likely have problems = red. (i.e., no highlight for May or Likely).
====Prediction Threshold = “Very likely have problems”
- **If “Highlight likely problem edits” is checked:**
- Apply highlights as follows, Very likely have problems = red.
- **If “Show only likely problem edits” is checked:**
- Activate filter, Very likely have problems.
- **If BOTH options are checked (highlighting and filtering)**
- Activate filter, Very likely have problems and apply highlights as follows, Very likely have problems = red (i.e., it doesn't matter if one or both are checked for this one).