Idea Delivered

Tridion Docs 15.1 will have Metrics feature that will have a set of predefined charts:

- Content reuse chart will show you the reuse level for a selected period highlighting the amount of new content compared to the one that was reused and the reuse level

- Return on Investment chart shows the value of using Tridion Docs for a selected period based on the customer’s reuse level versus creating content from scratch. As well as showing a trend over a specified period to see how much you are saving with Tridion Docs

- Productivity chart shows publishing activity for a selected period indicating the status of published outputs

There is also a recent blog on community explaining the reuse formula:  A guide how to understand Tridion Docs’ new Reuse Metrics 

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