Accepted, Not Yet Planned

We will look at it after modernization of our platform

Add OOTB Reuse Snapshot Report

We would like to have a very basic reuse report added to Knowledge Center. This report could simply include all topics  in the repository that are used in more than one publication.

The user group put together the attached document, but it is intended as a guideline only. We are open to different ways of presenting (and calculating) reuse in a very basic, out-of-the-box way. For example, the document says that only topics should be counted, but we would be open to counting all objects.

KC User Group Reuse Snapshot Report Request.docx

Elizabeth Gschwind
Parents

  • We're looking at this now, but needless to say, the OOTB report can be a real utility for customers to achieve success in making the transition to DITA by providing a helpful objective measure to augment opinion and heuristics.  I'm sold on Hackos's case for word count:

    Percent Repository Words Reused in Context (PRWRC) = (Words in All Produced Content –Words in the Repository)/(Words in the Repository)

    But it would be interesting to hear from people who think that an alternative approach would be better, and why they think that would be so.

    In the absence of any strong argument to the contrary, again, I really think implementing this feature as an OOTB option would greatly strengthen SDL's value proposition. When we're successful refining our reuse practices with objective measurements, you become even more a vital partner to our organization.

Comment

  • We're looking at this now, but needless to say, the OOTB report can be a real utility for customers to achieve success in making the transition to DITA by providing a helpful objective measure to augment opinion and heuristics.  I'm sold on Hackos's case for word count:

    Percent Repository Words Reused in Context (PRWRC) = (Words in All Produced Content –Words in the Repository)/(Words in the Repository)

    But it would be interesting to hear from people who think that an alternative approach would be better, and why they think that would be so.

    In the absence of any strong argument to the contrary, again, I really think implementing this feature as an OOTB option would greatly strengthen SDL's value proposition. When we're successful refining our reuse practices with objective measurements, you become even more a vital partner to our organization.

Children
No Data