2.0: Help or Hindrance?
Originally posted on the Vista discussion board for LIBR 559M on July 21, 2011.
For my money, any jargon, such as the “2.0” suffix, is helpful when it successfully serves as shorthand for a more complicated concept, and becomes a hindrance when it is used erroneously or with an audience that isn’t privy to the jargon.
Medical terminology is a good example of this concept. Having worked with doctors and nurses in the field of medical publishing, I have been exposed to, and come to understand, a great deal of medical jargon, abbreviations, and acronyms. The first law of medical school appears to be, “Never use words when a string of letters will do.”
Take the sentence, “With GERD, we have to avoid NSAIDs. We’ll start with an OTC H2 antagonist and move up to a PPI if necessary.” If a doctor says that to a nurse, no problem. If a doctor says that to a patient and then walks out of the room with no further explanation, it’s potentially a serious problem.
(By the way, that sentence translates to: “With gastroesophageal reflux disease [i.e., heartburn], we have to avoid nonsteroidal anti-inflammatory drugs [e.g., aspirin, ibuprofen]. We’ll start with an over-the-counter [i.e., non-prescription] histamine antagonist [e.g., Tagamet] and move up to a proton-pump inhibitor [e.g., Prilosec] if necessary.”)
Here’s when I think it’s appropriate for information professionals to use the “2.0” suffix in describing their library’s programs or services:
- With other members of staff if there have been previous discussions of what, specifically, the 2.0 suffix means for that library’s programs and services, and everyone has agreed to those definitions.
- Never with patrons. There’s no way to establish with each patron that what you mean by “2.0” is what they understand by “2.0” – if they understand it at all. If you mean chat reference, say chat reference. If you want to say that the new online catalogue allows user tagging, say that. (And don’t call the catalogue an “OPAC,” either.) It’s possible that even these specific terms may need further explanation, depending on the patron. As information professionals, our job is to provide information, not to obfuscate it with jargon.
Here’s Balko’s First Law of Librarianship: Never use jargon with patrons when plain old English [or insert other culturally appropriate language here] will do. (By the way, that’s always.)