This object is in archive! 
Merge "deletes" old topic, thus breaks old URL and throws away existing text
The use Response staff seems to have merged my response https://help.useresponse.com/responses/how-to-increase-precision-of-search-results-eg-using-and-or-not with https://help.useresponse.com/responses/can-search-on-partial-matches-be-improved
Two problems with the current behaviour of simply "deleting" old topics during merge:
- The old URL (first one) is broken. That's bad, because that URL is in several other systems, so when visitors click it, they get a 404. That subscribers did receive a merge notification mail does not help those visitors - they have no idea why the topic is gone / the URL broke, and even searching for the topic name won't work, as the merged topic won't have the exact same name.
Some possible solutions: Add a redirect from old to new URL, or keep old topic "alive in read only mode" and simply add a big fat merge notification at the top. - The two topics are only similar that they're about search, but they have completely different content: One is about introducing search operators (AND, OR,..) to increase search precision, and the other about finding search terms if they are parts of words to increase search recall. Hence the topics's texts are not the same as assumed in https://help.useresponse.com/responses/can-given-answers-be-merged-while-visible-for-users but they provide quite different aspects. It's not only information loss, but also renders the "surviving" topic not findable by searching for the words that appeared in the "lost" topic.
Some possible solutions: Merge the texts of the "lost" topic into the "surviving" optic, or keep the old topic "alive in read only mode" and simply add a big fat merge notification at the top (and add a comment in the "surviving" topic about the merge, with a link to the "decativated" topic).
At least the URL shall not be broken.
The behavior of accessing merged topic will be changed in 3.x. In fact it's already working like that in 3.0.1 beta release.
So once you access merged topic it will redirect you to the main one. Though there is no away to split them again.
The behavior of accessing merged topic will be changed in 3.x. In fact it's already working like that in 3.0.1 beta release.
So once you access merged topic it will redirect you to the main one. Though there is no away to split them again.
The behavior of accessing merged topic will be changed in 3.x. In fact it's already working like that in 3.0.1 beta release.
So once you access merged topic it will redirect you to the main one. Though there is no away to split them again.
The behavior of accessing merged topic will be changed in 3.x. In fact it's already working like that in 3.0.1 beta release.
So once you access merged topic it will redirect you to the main one. Though there is no away to split them again.
So I hope v3.x is soon live for Locus.
It's OK that they can't be split again - if required, users can create simply a new topic.
So I hope v3.x is soon live for Locus.
It's OK that they can't be split again - if required, users can create simply a new topic.
3.0.x should be live in weeks and it will be more flexible in merging.
3.0.x should be live in weeks and it will be more flexible in merging.
Replies have been locked on this page!