They don't flow the same way because majority of contemporary web design (and documents derived from web pages) hearkens back to real old days when (mobile) documentation was inked on scrolls or (clay) tablets, not one of those newfangled book-thingies.
"Anyway, I passed along that I really like the addition of changing the version option to the latest to see if the information is the same or has changed. For example, doing a Google Search and clicking the link takes me to 18.05. But changing the version to 19.11 allows me to stay on the same page but in the latest version of the document. Then I can add in my comments if necessary."
Yes! I agree, this is great.
The only problem I have is when I'm taken to a version that I don't want...and I choose the version that I want, but instead of taking me to the page I expect, it takes me to the home page of the version I selected....frustrating because it happens often.
1 of 1 people found this helpful
I like the feature too, but I also know LJ's problem.
But I would like to point out that the feature is also part of the problem. Since the switch from major.minor.patch to yymm, the complete documentation is copied twice a year - for very few real changes.
This means that all inaccurate and possibly incorrect content is duplicated. Without comments, of course. Who should keep this editorially under control if there is no system behind it that dynamically compiles the content.
As quality manager I would look for a solution in my company to avoid unnecessary duplication of unchanged contents/pages. Then the editors can concentrate on their actual work and together with us correct the content only once.
We would also benefit from this, because the commentary is only required once and has a cross-version effect.
2 of 2 people found this helpful
Thanks all for your comments. Regarding the version picker, if you are looking at a public page and then change to a version in which that page doesn't exist, you are sent to the Home page (rather than give you a Page Not Found). If the same page exists in the new version, you see that page.
On the excellent point regarding content duplication, on the authoring side we do efficiently only duplicate pages when they are changed. We will evaluate bringing this model to public documentation.
3 of 3 people found this helpful
Great question regarding how to find your own contributions to docs. Stefan, to find your comments, you can try Search: Search - BMC Documentation . In the sidebar to the left, you can configure date ranges, doc sets, etc.
I have a very recent example of a really long delay in responses. I noticed two years ago this month that What is operational catalog information? - Documentation for Remedy IT Service Management Suite 9.1 - BMC Documentation referenced a video but there wasn't actually a video on the page. Someone else had commented about that on 10th October 2017 and I replied that the 8.1 version of the page did have the video.
I didn't see any updates until a couple of weeks ago when a BMC employee commented that the video is now available on 7th Jan 2020. I completely understand that there will always be a backlog of some sort but two years seems like an awfully long time for an update. I suppose this could have been partly influenced by the fact that this page was for the older version 9.1 (which wasn't that old back in late 2017 when the original comment was made though).
Hi Patrick Wilson,
good idea. Unfortunately, your options and mine seem very different. I am just a normal user and can only choose from three types. Comments are not included.
So I lose the overview with the many versions and don't track it anymore. Any other ideas for me?