TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: When is it too much information? From:"Peter Hirons" <peter -at- galley -dot- ie> To:"'Debbie Hemstreet'" <D_Hemstreet -at- rambam -dot- health -dot- gov -dot- il> Date:Wed, 20 Feb 2013 10:07:07 -0000
Because they are not the meaning of deprecated.
A deprecated feature is one that still exists but has been superseded by
another (newer) feature that performs the same function. There is the
implied warning that it is only kept in to support legacy code and may
not continue to exist in the next version.
Peter
-----Original Message-----
From: techwr-l-bounces+peter=galley -dot- ie -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+peter=galley -dot- ie -at- lists -dot- techwr-l -dot- com] On Behalf Of
Debbie Hemstreet
Sent: Wednesday, February 20, 2013 7:37 AM
To: Ryan Young; Ryan Pollack
Cc: tech2wr-l
Subject: RE: When is it too much information?
Except why make the user have to think by using the term "Depracated" Why
not "Deleted Features" or "Removed Features"?
Debbie
דבורה
_____________________
Deborah Hemstreet
English Editor
Rambam Health Care Campus
Ext. 1285
Tel. 04 854-1285
Mobile: 050.206.1273
Fax: 04 854-2657
From: Ryan Young [mailto:ryangyoung -at- gmail -dot- com]
Sent: Tuesday, 19 February, 2013 19:07 PM
To: Ryan Pollack
Cc: Debbie Hemstreet; tech2wr-l
Subject: Re: When is it too much information?
The release notes at my new position have a section called "Deprecated
Features" as well as a section called "Changed Functionality." I feel
like that's not a bad idea. Seems like it would address situations like
the one described in the original post.
On Tue, Feb 19, 2013 at 6:57 AM, Ryan Pollack
<ryan -at- clicksecurity -dot- com<mailto:ryan -at- clicksecurity -dot- com>> wrote:
Ah, that is a really good idea. I second that! I do something similar in
my release notes. I have these sections:
- New
- a
- b
- c
- Changed
- d
- e
- f
- Fixed
- g
- h
- i
- Known Issues
- j
- k
- l
On Tue, Feb 19, 2013 at 12:36 AM, Debbie Hemstreet <
D_Hemstreet -at- rambam -dot- health -dot- gov -dot- il<mailto:D_Hemstreet -at- rambam -dot- health -dot- gov -dot- il>
> wrote:
> I think you can best solve this problem by having a section:
>
> Deleted features:
>
> XXX information is no longer displayed in XXX location. The same
> information can be found XXXX.
>
> In the release notes I write for one of my clients we go for
redundancy.
> Hence, for the above example, under NEW features, we would also have:
>
> XXX information is now accessible only via XXXX (and not in XXX
location).
>
> So the user sees where to get the information but also knows that it
> is no longer displayed in a certain spot. If a user was relying on the
> displayed information, there will be a support call to find out where
> the heck the information went to and how do I get it now.
>
> If there is no way to get the information that is no longer displayed
> -- bad move on the developers part and you need to point this out.
>
> Hope this contributes to the discussion
>
> Deborah
>
>
> -----Original Message-----
> From:
techwr-l-bounces+d_hemstreet=rambam -dot- health -dot- gov -dot- il -at- lists -dot- techwr-l -dot- com<mail
to:rambam -dot- health -dot- gov -dot- il -at- lists -dot- techwr-l -dot- com>[mailto:
> techwr-l-bounces+d_hemstreet=rambam -dot- health -dot- gov -dot- il -at- lists -dot- techwr-l -dot- com<m
> techwr-l-bounces+ailto:rambam -dot- health -dot- gov -dot- il -at- lists -dot- techwr-l -dot- com>] On
> Behalf Of yehoshua paul
> Sent: Monday, 18 February, 2013 17:07 PM
> To: tech2wr-l
> Subject: When is it too much information?
>
> While reviewing the latest release notes that my company sends out
> every couple of weeks, one of the support guys suggested that I add
> the following words (or something similar) to one of the change
> descriptions: "The user does not need to do anything." What changed is
> information that was displayed in one area of the UI is no longer
> displayed. The support guy thought the users might think they need to
> do something, now that they no longer see this information.
>
> I told him, if the users needed to do something, I would write this in
> the release notes like I did with some of the other changes, and
> include the relevant steps, or the appropriate reference to the online
> help. If I didn't write anything, why would the users think they need
to do something?
> His argument was that it doesn't hurt to add the sentence, and it may
> prevent confused customers from calling customer support.
>
> What do you guys think? Would adding a superfluous sentence (in my
> opinion) help or hinder users.
>
> Yehoshua
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses
> tips for creating EPUB, the file format used for e-readers, tablets,
> smartphones, and more.
>
> Learn more: http://bit.ly/12LyN2z
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as
>
d_hemstreet -at- rambam -dot- health -dot- gov -dot- il<mailto:d_hemstreet -at- rambam -dot- health -dot- gov -dot- il>
.
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com<mailto:techwr-l-leave -at- lists -dot- techwr-l
> .com>
>
>
> Send administrative questions to
> admin -at- techwr-l -dot- com<mailto:admin -at- techwr-l -dot- com>. Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources
and info.
>
> Looking for articles on Technical Communications? Head over to our
> online magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our
> public email archives @ http://techwr-l.com/archives
>
>
>
>
> **********************************************************************
> ************** This footnote confirms that this email message has been
> scanned by PineApp Mail-SeCure for the presence of malicious code,
> vandals & computer viruses.
>
> **********************************************************************
> **************
>
>
>
>
>
>
>
> **********************************************************************
> ************** This footnote confirms that this email message has been
> scanned by PineApp Mail-SeCure for the presence of malicious code,
> vandals & computer viruses.
>
> **********************************************************************
> **************
>
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses
> tips for creating EPUB, the file format used for e-readers, tablets,
> smartphones, and more.
>
> Learn more: http://bit.ly/12LyN2z
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as
ryan -at- clicksecurity -dot- com<mailto:ryan -at- clicksecurity -dot- com>.
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com<mailto:techwr-l-leave -at- lists -dot- techwr-l
> .com>
>
>
> Send administrative questions to
> admin -at- techwr-l -dot- com<mailto:admin -at- techwr-l -dot- com>. Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources
and info.
>
> Looking for articles on Technical Communications? Head over to our
> online magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our
> public email archives @ http://techwr-l.com/archives
>
--
Ryan Pollack
Senior Technical Writer | Click Security
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips
for creating EPUB, the file format used for e-readers, tablets,
smartphones, and more.
Looking for articles on Technical Communications? Head over to our
online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public
email archives @ http://techwr-l.com/archives
*************************************************************************
***********
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
*************************************************************************
***********
*************************************************************************
***********
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
*************************************************************************
***********
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips
for creating EPUB, the file format used for e-readers, tablets,
smartphones, and more.
Looking for articles on Technical Communications? Head over to our
online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public
email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips for creating EPUB, the file format used for e-readers, tablets, smartphones, and more.
