2 Replies Latest reply on Nov 22, 2014 3:00 PM by claud2134

    Indexing for two audiences

    claud2134


      Hi all,

      I need to index an application with two parts (Manager and General) The application pages and tasks differ for about 30% of the index entries. Thanks for any ideas.

      In webhelp, can you publish two indexes and let the user choose an index to view? If not, here's two methods I can think of. If you haven't had other experiences, which of these do you prefer?

       

      Method 1: Separate the 30% by (application part). Works, but lengthy.

       

      add students (Manager)

      add students (General)

       

      Method 2: Separate the 30% by user section. Easier to view as a list, but not useful when searched.

       

      Manager tasks (see also General tasks):

      add students

      add teachers

      transfer students

      (etc)

       

      General tasks (see also Manager tasks):

      add students

      edit students

      transfer students

       

      Thank you!

        • 1. Re: Indexing for two audiences
          Captiv8r Adobe Community Professional & MVP

          Hi there

           

          There are a few approaches you could consider here. Unfortunately, my crystal ball is on the fritz and my psychic skills are basically non-existant. So it's impossible for me to ascertain the particular version of RoboHelp you may be using. So I'll simply assume version 11 as that's the current shipping version.

           

          Recent versions of RoboHelp make it really easy to create and maintain more than a single index. The following assumes you have created more than one index.

           

          You could create multiple outputs, with each output using its own index. You simply duplicate one output in the Single Source Layout recipe box as many times as you need. Then you configure each output to use the desired index. After you generate, you end up with multiple sets of WebHelp files that would need to be published to different folders on your server. The end user would then need to have the correct link to open the set created for them.

           

          The last two or three versions of RoboHelp offer a feature known as "Dynamic User Centric Content" or DUCC. This is also known as Content Categories. So with this approach you use a Single recipe in your Single Source Layouts pod. You define more than one category and you make the unique index assignment in the Category settings.

           

          tmp1.png

           

          After you generate and publish, the end user is able to see the other categories, but they make the selection that applies to them.

           

          tmp2.png

           

          Cheers... Rick

          • 2. Re: Indexing for two audiences
            claud2134 Level 1

            Thank you, Rick. You are always quick to reply and identify new Robohelp functionality. Very much appreciated.