Hello Everyone,
I thought I'd share my
tip for doing a full text search against DocOps documentation, using a workaround.
In short, it is:
"Save the whole DocOps section to a PDF, and then search it there."Why do we want to do this? Doesn't DocOps and Google already have "search" functionality?
Well, yes, they do. And good functionality at that. However, there is a limitation in that only the first part of any web page is indexed by these sources. So if you have a key term that you are looking for that is at the
bottom of a long web page, then these searches won't find it.This can be a bit of an issue for site application administrators and support staff. Especially when searching for strings like error codes or database field names, which are usually very specific (and so would appear in a search string), but also be liable to be buried in a long list (and hence won't be found).
The DocOps search may return "Search returned no results" even for strings that exist.
Please see my Knowledge Document for the full procedure: How to do a full text search against DocOps documentationThen you can be doing fast searches that pull back results like this:
CAUTION: You should only use this method as a supplement in order to find data that does not change often.
The DocOps sites are the primary source of information and are kept current. Please use DocOps before beginning any procedure, as there may be last minute revisions.
Thanks, Kyle_R.
------------------------------
Broadcom
------------------------------