# Best Practices for Marking Solutions - A Discussion **URL:** \ **Category:** Meta\ **Created:** [September 17, 2020, 11:40pm UTC](https://www.rubin.community/t/best-practices-for-marking-solutions-a-discussion/4402 "2020-09-17T23:40:48Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![MelissaGraham](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/melissagraham/32/2549_2.png) [@MelissaGraham](https://www.rubin.community/u/MelissaGraham)\ **Post date:** [September 17, 2020, 11:40pm UTC](https://www.rubin.community/t/best-practices-for-marking-solutions-a-discussion/4402/1 "2020-09-17T23:40:48Z")
As an experiment in community engagement, I’ve been reviewing all Support topics and marking a post as the solution if it appears the issue has been addressed. [Only the original poster and forum moderators may mark solutions.](http://www.rubin.community/t/who-can-choose-a-solution/242) There are two main reasons why I thought reviewing and marking solutions would be helpful: (a) it allows moderators to immediately identify unresolved topics on the Support category page, and (b) it allows users searching for existing answers to quickly identify topics with solutions. However, I’ve identified two issues with marking topic solutions: 1. In some cases no single post is the full solution. Various people supply different pieces of the puzzle, which amounts to a solution. I pick the most complete answer as “the solution”. I worry this could be confusing to future readers, who see a partial solution marked as “the solution”. But there is no way to mark a full topic as “resolved” (that I know of). 2. There is no way to see who marked the solution: the original reporter or a moderator. There is a danger of a moderator marking a solution which they think is clearly correct, but might not actually work long-term for a user’s particular case. The user (or other users) might feel like the discussion has been “shut down” if a solution is marked, and then not contribute, which is counterproductive. These aspects of marked solutions might be resolved by switching to a system in which only the original poster is allowed to mark a solution to their own question. In this case, perhaps moderators should switch to using internal flags to track unresolved topics in need of attention (i.e., instead of using the “solution” flag to mark resolved topics that _don’t_ need attention). Thoughts? ---
**Author:** ![ktl](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/ktl/32/1373_2.png) [@ktl](https://www.rubin.community/u/ktl)\ **Post date:** [September 17, 2020, 11:54pm UTC](https://www.rubin.community/t/best-practices-for-marking-solutions-a-discussion/4402/2 "2020-09-17T23:54:51Z")
A “solved” tag might be an appropriate solution that operates at the topic level rather than at the post level. > [@How to use tags for forum topics](http://www.rubin.community/t/how-to-use-tags-for-forum-topics/43): > > This wiki post outlines how to use tags on [community.lsst.org](https://community.lsst.org). Categories vs Tags This forum uses both categories and tags to organize posts. We use categories to broadly organize and set the tone for different types of content in the forum. You can see a list of categories on its [index page](https://www.rubin.community/categories) (look for a ‘Categories’ button in the navigation bar or site menu). Read the descriptions of each category before posting to see where your discussion belongs. A moderator might recategorize your post if … ---
**Author:** ![swinbank](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/swinbank/32/24_2.png) [@swinbank](https://www.rubin.community/u/swinbank)\ **Post date:** [September 18, 2020, 4:33pm UTC](https://www.rubin.community/t/best-practices-for-marking-solutions-a-discussion/4402/3 "2020-09-18T16:33:56Z")
> [@MelissaGraham](#): > > switching to a system in which only the original poster is allowed to mark a solution to their own question This relies on the original poster to do some extra work. I’d expect that many will be willing to, but some will forget, and some answers will slip through the cracks. ---
**Author:** ![jsick](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/jsick/32/672_2.png) [@jsick](https://www.rubin.community/u/jsick)\ **Post date:** [September 18, 2020, 6:46pm UTC](https://www.rubin.community/t/best-practices-for-marking-solutions-a-discussion/4402/4 "2020-09-18T18:46:42Z")
First, I’ve enabled a feature that’s relatively new where you can filter the support categories (or any category where the Solutions plug in is enabled) by topics that are solved or not. At a minimum, this could help with some aspect of triage: ![image](https://us1.discourse-cdn.com/flex002/uploads/rubin/original/2X/7/7f16e622150bd28b8c0cb0401c5f2e98e7514676.png) > [@MelissaGraham](#): > > However, I’ve identified two issues with marking topic solutions: > > 1. In some cases no single post is the full solution. Various people supply different pieces of the puzzle, which amounts to a solution. I pick the most complete answer as “the solution”. I worry this could be confusing to future readers, who see a partial solution marked as “the solution”. But there is no way to mark a full topic as “resolved” (that I know of). I agree it can be hard to piece together a solution from a conversation. In cases like this, could the CET staff write a succinct summary post containing the comprehensive solution (possibly with links to revised documentation as I think we should use the forum to inform documentation improvements), and then mark _that_ post as the solution? > [@MelissaGraham](#): > > 1. There is no way to see who marked the solution: the original reporter or a moderator. There is a danger of a moderator marking a solution which they think is clearly correct, but might not actually work long-term for a user’s particular case. The user (or other users) might feel like the discussion has been “shut down” if a solution is marked, and then not contribute, which is counterproductive. > > These aspects of marked solutions might be resolved by switching to a system in which only the original poster is allowed to mark a solution to their own question. In this case, perhaps moderators should switch to using internal flags to track unresolved topics in need of attention (i.e., instead of using the “solution” flag to mark resolved topics that _don’t_ need attention). I still think that both moderators and the original poster should be able to mark solutions, as we currently do. I think its important for the observatory to reserve the right to curate the forum, and ensuring solutions are marked at the end of the day is part of that. I don’t think there will be an issue with shutting down follow-up if CET staff explicitly invite the original poster to ask more questions if the solution or summarized solution aren’t clear. @ktl’s suggestion of a discourse flag is neat but I think it might be confusing to have two public ways of marking solutions. It sounds like it might be worth it to connect posts to internal ticketing software to help track support work and assign staff to topics, like [https://zapier.com/apps/discourse/integrations/jira-service-desk](https://zapier.com/apps/discourse/integrations/jira-service-desk) ---
**Author:** ![MelissaGraham](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/melissagraham/32/2549_2.png) [@MelissaGraham](https://www.rubin.community/u/MelissaGraham)\ **Post date:** [October 21, 2020, 11:55pm UTC](https://www.rubin.community/t/best-practices-for-marking-solutions-a-discussion/4402/5 "2020-10-21T23:55:15Z")
Thanks @ktl, @swinbank, and @jsick for the thoughts, and @jsick for that new useful functionality. I agree that both moderators and the original topic creator should retain the ability to mark reply posts as “solutions”. In order to avoid cases where a moderator marks a reply post as a solution because it seems to be one – but unbeknownst to them it didn’t actually work for the original topic creator – I’ve changed my approach to only mark a post as the solution when it’s _very clear_ that it resolved the issue (meaning, the original poster confirmed it worked). I also like @jsick’s idea of writing a small summary reply post in cases where the issue was clearly solved but the solution is distributed across multiple replies, and then marking that summary as the solution – I’m going to try that when I next find such a case. For topics without _very clear_ solutions, I’ll continue to post replies that solicit confirmation (or follow-up) from the original topic poster. In a few cases already this has lead to the original poster marking a solution. Continued discussion and feedback on moderation techniques very welcome.