Knowledgebase Etiquette

Please Do

• Update articles in your area of expertise.
• Review oldest articles and either update them, or mark them REVIEWED, TO BE VERIFIED, DEPRECATED, or TO BE DELETED:
  • Update any article you think is incorrect. Make any and all changes you think are necessary.
  • Add REVIEWED ON date, at bottom of article if the article and links are good.
  • Add TO BE VERIFIED as a tag, at the top if you think an article should be checked by someone specific. Please forward it to them and ask them to make any changes necessary. If you’re not sure who, forward it to the appropriate person in the Help Desk Directory http://programmers.ucla.edu/helpdesk/
  • Add DEPRECATED as a tag, and at the top If an article refers to something that is out of date but might be useful to keep around for institutional memory. If non-obvious, explain why.
  • Add TO BE DELETED as a tag, and at the top of an article if you think an entire article should be deleted. Please explain why. Someone with delete privileges will get around to confirming your judgement and deleting it in a few days.
• If you think an article title should be changed, this will break bookmarked links, but because the kb error page suggests possible alternatives, this might not be so bad. Especially if you keep the first part of the title the same. If you want to notify the original poster and any updaters, that would be great.
• Look for articles where you can contribute, such as anything titled “Has anyone tried …”
• Add yourself to http://kb.ucla.edu/articles/how-do-you-keep-up-with-technology
• Post an article if you want to remember a particular tool, technique, or website, and it’s not private information.
• Post an article if you want to direct people to little know sections of your department website.
• Post an article if you want to collect a set of other articles together, e.g. Advice for new faculty.

Please Don’t

• Post a new article without searching to see if it’s already in the knowledge base.