Las notificaciones/Los esquemas de clasificación

From mediawiki.org
Jump to navigation Jump to search
This page is a translated version of the page Notifications/Sorting schemes and the translation is 36% complete.
Other languages:
Bahasa Indonesia • ‎English • ‎español • ‎español de América Latina • ‎français • ‎polski • ‎中文 • ‎日本語 • ‎한국어

The overall task is: Deciding how to sort the notification types (e.g. "new usertalkpage message", "your edit was reverted", "a page you created has been linked to", "thanks", etc) into two groups. La clasificación actual tiene algunos problemas.

Fueron anteriormente dos propuestas. Después de comentarios, hemos decidido guardar solo una alternativa al esquema actual (Abril 2016). El equipo quiere tus comentarios sobre él (tus preferencias, o preocupaciones). La recomendación es que empezamos con la clasificación "Por urgencia" (prototipo).

Please share your feedback at task T123018 or here on MediaWiki.org.

El problema para solucionar

There are currently two Notification flyout menus, one for Alerts and one for Messages. Diferentes tipos de notificaciónes aparacen en menús diferentes. There have been criticism over time that the scheme for dividing up the messages is unclear and/or inconsistent. Esas críticas incluyen los siguientes:

  • Ideas of "urgency" and "requiring follow up" are mixed together, making it difficult to explain or predict why different items are in each flyout.
  • Actualmente, los artículos "Alerta" son automáticamente "marcados como leídos" al abrir el flyout. Yet some of these require follow-up or other action to be fully understood (e.g., Mention), so this feature's value is not always clear.
  • Because "Alerts" are perceived as "Urgent", the "Thanks" and other items seem out of place in that flyout.

Objetivos

  • Crear un esquema que es fácil de entender, aprender, y predecir.
  • Dar editores información más claro sobre sus nuevas notificaciones.
  • Reducir distracciones innecesarios desde las notificaciones no urgentes.
  • Algo que trabaja bien para los editores quien reciben grandes (y pequeñas) cantidades de notificaciones.
  • Something that scales well, as new (requested) notification types are created.
  • Something that scales well, once cross-wiki notifications are available.

Types

See examples of the most common notification types at:

File:Notifications Catalog.png

Opciónes

  1. Actual
  2. Urgente versus No Urgente
  3. (formerly and now abandoned) Follow-up versus No follow-up (is a reply needed/likely)

(Esta tabla no tiene anotaciones y solo muestra los tipos de notificaciones más comúnes. See a more detailed version here at googledocs which also includes a 3rd and 4th (more complicated) alternative.)

Two Alternative Schemes for Separating Notifications into the 2 Different Flyout Menus
#1: CURRENT DIVISION #2: URGENTE VS. NO URGENTE
View Mockup of this Concept in Action
ALERTAS MENSAJES ALERTAS AVISOS
bienvenido Mensajes en la página de discusión Mensajes en la página de discusión bienvenido
Reversiones de edición flow-new-topic Reversiones de edición Enlaces de página
Enlaces de página flow-post-reply Menciones Agradecimientos
Menciones flow-post-edited Cambios de permisos de usuarios flow-thank
Cambios de permisos de usuarios flow-topic-renamed Correos electrónicos de otros usuarios flow-new-topic
Correos electrónicos de otros usuarios flow-mention flow-post-edited flow-post-reply
Agradecimientos flow-mention flow-topic-renamed
flow-thank cx-first-translation
cx-first-translation cx-tenth-translation
cx-tenth-translation cx-hundredth-translation
cx-hundredth-translation
ANALYSIS ANALYSIS
PROS CONTRAS PROS CONTRAS
Ideas of Urgency and Follow up are mingled in ways that are inconsistent, making this difficult to explain or predict. Division, while subjective, is clear and will track with some users' expectations (given the red badge color). The division is subjective. Given differing working styles, some users will disagree with assignment of individual items.
Because some "Alert" items require follow-up and are not self-contained (e.g., Mention), ability to Mark as Read on open is of questionable value Factor of urgency may provide an aid to triage ("check these first")
Because alerts are perceived as Urgent, Thank Yous and other items seem out of place.
GENERAL POINTS GENERAL POINTS
In this scheme, an effort was made to determine the messages that users would want to know right away vs. those that they may regard as less pressing. Urgency was more or less arrived at by consensus in consultation with various team members. What to label these: "Alerts" works reasonably well, since it does carry a connotation of urgency. But many of the Alerts are arguably Messages as well (e.g., edit-user-talk). Suggest "Notices" as not sounding to deprecatory but connoting a lower level of urgency.
The red, "Urgent," badge color for Alerts is recommended for this scheme. In labelling the non-urgent items, we need to be careful that some groups (e.g., Translation) don't perceive that we are labelling their activities less important.
Many of the Urgent (Alert) items require follow-up (e.g., edit-user-talk), so use of automatic Mark as Read is not recommended.