Slashdot: News for Nerds


Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Documentation Naming Conventions

realsilly (186931) writes | more than 4 years ago


realsilly writes "I am a requirements analyst, and I often find myself in companies where they either have an extremely rigid naming convention and structure for storing documents or there is no structure in place at all. I find myself in the latter of the two situations, where I'm trying to come up with an easy to use and implement naming convention that will be followed by those who don't name things formally. I am avoiding using numbers and dates within document names and in many cases, I have much of my early documentation on internal wiki pages. I'm looking for some best practices ideas from the Slashdot community."

cancel ×

1 comment

No easy solution (1)

hatemonger (1671340) | more than 4 years ago | (#29995486)

I'm active duty military, and worked this problem recently for a ~2000 person operation. In the end, we had a fairly complex set of rules laid out in a 2 page instruction, but also provided a tool (an html file that used text input and javascript) that simplified the process. There was a checkbox for "Is this a draft?", "Is this a template?", a dropdown for classification and another for originating unit. There was only 1 mandatory text field, and that was for Base Document. Each input field had a brief description of what went into it.

Other things we required: no punctuation other than spaces, no "v1", "v2" (instead we used versioning on SharePoint), date-time group format was yymmdd hhmm and was only used in certain files like recurring reoprts. Also, don't forget to set up rules for creating folders. The last ~2000 person operation we did ended up with 17 pages of 9pt font to print our folder structure.

In the end, the hardest part is going to be convincing users that a standard naming convention is worth their time. You have to show them how bad it can be when done ad hoc, and how easy you've made it to follow the rules.

Check for New Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Create a Slashdot Account