Tópicos vinculados (divisão e gerenciamento de megatópicos)

[techAPJ (Arpit Jalan)]

I’ve just merged a feature which creates a new linked topic automatically when a topic is auto-closed based on auto close topics post count site setting.

This feature is especially useful for automatically splitting and managing megatopics.

Here’s how it works

Let’s say auto close topics post count setting is set to 10000 posts and a topic (with title “Introduce yourself!”) just reached that limit.

Now we’ll close that topic and create a new linked topic to continue the discussion. The first post of new topic will link to all prior discussions (topics).

The original topic title will be appended with “Part 1” and the new topic title with be appended with “Part 2”.

The subsequent topics will follow similar title naming convention.

There will also be a moderator post at the bottom of auto-closed topic indicating that there is a new topic available to continue discussion.

This feature is enabled by default. To disable the feature simply disable the site setting auto close topics create linked topic.

Note that this feature will be disabled if auto close topics post count is disabled (set to 0).

[jrgong]

That’s awesome!

Is that something that could be used as solution to the “babble 10,000 messages issue”?

[seanblue]

I have a small suggestion regarding these lines of code (and whatever else I missed):

previous_topics += "- [#{topic.title}](#{topic.url})\n"

parent_topic.add_moderator_post(system_user, I18n.t('create_linked_topic.moderator_post_raw', new_title: "[#{new_topic_title}](#{new_topic.url})"))

I’d recommend replacing [title](url) with just url, and relying on existing Discourse functionality that displays the title of the topic from the URL. If I’m not mistaken, this would have the bonus of auto-updating the topic title displayed if the topic is renamed, which I think would be a nice touch.

[codinghorror (Jeff Atwood)]

Yes, that’s a good idea @techAPJ we should probably do that.

Also, can we make it so there’s a single message rather than two? Why not have the “continue discussion” part be edited into the close message? Like:

This topic was automatically closed after reaching the maximum limit of 10000 replies. Continue this discussion at {link}

[techAPJ (Arpit Jalan)]

@seanblue

relying on existing Discourse functionality that displays the title of the topic from the URL

Done via:

UX: when creating linked topic use URL and let onebox work its magic (#11118)

@codinghorror

Why not have the “continue discussion” part be edited into the close message?

Sure, done via:

UX: update topic small action post to add link for new linked topic URL (#11132)

[riking (Kane York)]

@seanblue

relying on existing Discourse functionality that displays the title of the topic from the URL. If I’m not mistaken, this would have the bonus of auto-updating the topic title displayed if the topic is renamed, which I think would be a nice touch.

This won’t work as well when you’re continuing the discussion from an access-restricted topic into another category without the exact same access restrictions.

[seanblue]

Is that a likely use case? It seems like generally the continuing topic would stay in the same category as the original topic. If this situation does happen, you say it won’t work as well, but what specifically would the behavior be?

[JonathanShaw]

@riking

won’t work as well when you’re continuing the discussion from an access-restricted topic into another category without the exact same access restrictions.

Even without the linking issue, I’d expect the continuing topic to have inherited the exact same access restrictions. I’d see it as a bug if it didn’t.

[riking (Kane York)]

Good point - it’s probably fine, then!

[Paracelsus]

Hi, very nice feature, but two issues:

1. How do we change the “Part” (1, 2 and so on) text? In English based forums is probably fine, but we would like to be able to change it.
2. The category of the new topic. We’ve just got our first automatically linked topic and it was “uncategorized”. What we would like is the new topic to assume the category of the previously automatically closed topic.

[codinghorror (Jeff Atwood)]

Yes those are good points but the last time I checked the category was inherited properly, is that so @techAPJ?

[techAPJ (Arpit Jalan)]

@Paracelsus

How do we change the “Part” (1, 2 and so on) text?

You’ll need to update translation for these keys. See: Contribute a translation to Discourse

@Paracelsus

We’ve just got our first automatically linked topic and it was “uncategorized”. What we would like is the new topic to assume the category of the previously automatically closed topic.

That is a valid bug. I’ll fix this on priority today.

@codinghorror

the last time I checked the category was inherited properly

I believe that might have been a manual update. I don’t see code for assigning category to linked topic.

[techAPJ (Arpit Jalan)]

@Paracelsus

We’ve just got our first automatically linked topic and it was “uncategorized”. What we would like is the new topic to assume the category of the previously automatically closed topic.

Fixed via:

FIX: when creating linked topics make sure they belong to same category (#11188)

[JoelZaslofsky]

@jrgong

Is [this functionality] something that could be used as solution to the “babble 10,000 messages issue ”?

I’m also highly interested in this question.

[codinghorror (Jeff Atwood)]

@elijah did you wish to continue your conversation here? This is a more correct place to have it, IMO.

[codinghorror (Jeff Atwood)]

@elijah apparently you want the topic notification status (watching, tracking, muted, etc) for every single user in the old topic, to be copied across to the new topic, yes?

I see the rationale, but my worry is that could be a bit invasive for some of the users … long topics can involve hundreds or thousands of people. Anyone else have thoughts about this, pros and cons?

[elijah (Eli the Bearded)]

Yeah, let me repeat my suggestions here, for context.

On megatopics I was proposing either of two ways to make splitting more seamless for the less-than-regular user.

Method Watchlist Copy: when splitting a topic, copy over muted / tracking / watching status for the new topic. (And if the last topic only had copied, not set originally there: unset the the tracking status for the now closed one.) Rational: If the user hasn’t been around to read the topic for a while, but is generally interested in it, help them catchup by not highlighting the unread posts in the old topic, only the new.

Method Top Split: when splitting a topic, facilitate having posts 2 to N moved post 1 copied to a new topic (closed on creation), and replace those moved posts with a linked topic message. Rational: mucking with watch settings is messy. This allows archiving old content without breaking external links (bookmark, RSS, baked into an app, etc) or internal watch settings.

I like the top split method better, but either seems a way to help users out who are interested in very long (or long term but split) topics.

[jimkleiber]

@techAPJ

Acabei de mesclar um recurso que cria automaticamente um novo tópico vinculado quando um tópico é fechado automaticamente com base na configuração do site auto close topics post count.

Estou usando WP e Discourse para fazer educação em áudio e reflexão em grupo, e estava pensando o quão útil seria se, quando o plugin WP criasse um novo tópico no Discourse, um evento acionasse a criação de um tópico vinculado como tópico de reflexão para esse tópico principal. Dessa forma, isso me permitiria manter o tópico original como somente leitura, para que as pessoas não vejam as reflexões antes de ouvirem o áudio, e ter o tópico vinculado como o local para onde elas iriam para refletir.

Semelhante a isto:

@pfaffman

Organizei as tarefas (ou missões) em categorias somente leitura e instruí os alunos a responderem como tópico vinculado (agora no ícone de link abaixo de uma postagem) e colocarem sua postagem na categoria de sua turma com uma tag específica para essa tarefa.

Estou correto em assumir que pode ser apenas um pequeno ajuste neste código aqui para que aconteça em um novo plugin?

      if SiteSetting.auto_close_topics_create_linked_topic?
        # enfileira um trabalho para criar um tópico vinculado
        Jobs.enqueue_in(5.seconds, :create_linked_topic, post_id: @post.id)
      end

Além disso, estou curioso se existem aplicações suficientes para a criação automática de um tópico vinculado onde faria sentido tê-lo como parte do Discourse Automation?