Skip to main content
6月 8, 2017 3:23 下午 UTC
问题

KCS Article Flagging...taking another look

Taking another look.  Monitoring the following report Articles with topics without AF on a monthly basis displays articles which have been Unsuccessfully flagged gives me insight as to the hang-ups with this process.  I know we can make this easier for all.  Let's put on our thinking caps and give this a try.thinking cap.jpg

Current process:

  1. Click 'Show Feed' on an article in KCS mode
  2. Freeform text in the following format: #feedback #<flag_type> <Comment>
    1. #feedback #improve
    2. #feedback #rework
    3. #feedback #duplicate
    4. #feedback #archive

Suggestions:

  1. Make flagging case insensitive -
    1. Open 3 years, only 280 points, not very popular??
  2. Remove "#feedback" tag since it is redundant
    1. Open 4 months, only 10 votes, not very popular?
  3. Add #translate as a tag
    1. Open 8 days, only 3 votes

 

Do these help?  Should we take it one step further?  What do you think??

    3回复

    6月 8, 2017 5:47 下午 UTC

     

    (like accept most common typos

    or get a tool to flag articles with comboboxes to select the type instead of free text….)

     

     

    6月 9, 2017 4:18 上午 UTC

    I don't have a problem with these three, what I hate is when I type #feedback #improve and return, and hitting enter changes to #[Improve].

    If I want it not to change I need to add two spaces after #improve then hit enter.

    6月 13, 2017 3:51 下午 UTC

    I think we should implement all three during the next implementation cycle/window. They all provide value to TSEs and ultimately will improve the quality of our knowledge.