5 Replies Latest reply: Apr 3, 2012 7:49 AM by Pradeepkumar Haragoldavar RSS

Best practice for Classification?

Mikael Lindstrom
Currently Being Moderated

Hi experts,

We have scenario where we will have up to 50 characteristics in a single DIR type. The characteristics can be grouped in 8 different groups and I now wonder what best practice is.

To start with I added all characteristics in one class(Class "DIR) which I defined for my DIR Type.

This is working fine but then I read that you should not have “too many” characteristics in one class. I then created 8 new classes which all are inheriting down their characteristics to Class “DIR” (Ie, class DIR is the child class)

This solution also seems to work fine.

-Is there another way of doing this and what are the pros and cons?

(I also tried to have class "DIR" as the partent class but in this way the characteristics in the subclasses where not shown by default in my DIR)

-How many are "too many" characteristics?

 

BR

Mikael

  • Re: Best practice for Classification?
    Pradeepkumar Haragoldavar
    Currently Being Moderated

    50 characteristics for a single DIR is unusually high!! Please see if object dependencies in Classification can help you to simplify scenarios and bring down the actual number of characteristics required for various scenarios.

    Regards,

    Pradeepkumar Haragoldavar

    • Re: Best practice for Classification?
      Mikael Lindstrom
      Currently Being Moderated

      Thanks for your answer

       

      Yes, I agree that the number of characteristics are high

       

      Unfortunately we can't reduced the number of characteristics that much. Do you ahve any advise regarding the class?
      Should we try to split them into several classes or is it no point in doing so?

       

      Best Regards

      Mikael

       

      But r

      • Re: Best practice for Classification?
        Pradeepkumar Haragoldavar
        Currently Being Moderated

        Like i indicated earlier,the easiest approach for you to optimize your solution is by classifying your characteristics under categories and then applying object dependencies.

        Using this, you can ensure,for example,that a 17 inch LCD monitor is always associated with a desktop.It will help you bring down the number of characteristics applicable for a DIR.This is critical since the number of characteristics also plays a role in the search performance in DMS.

        Regards,

        Pradeepkumar Haragoldavar

        • Re: Best practice for Classification?
          Mikael Lindstrom
          Currently Being Moderated

          Thanks Pradeepkumar,

          I have looked at the object dependencies and this is reducing the number of characteristics a little bit but i still have quite many to handle.

           

          Just to confirm, regarding performance it's only object dependencies(reducing number of characteristics) that will affect it?
          So it doesn't matter if I use one or several classes?
          (execpt for maintainenace)

          BR

          Mikael

          • Re: Best practice for Classification?
            Pradeepkumar Haragoldavar
            Currently Being Moderated

            Just to confirm, regarding performance it's only object dependencies(reducing number of characteristics) that will affect it?

            Obj dependencies optimization is one of the critical areas that can enhance search performance!! Typically, when the search function is carried out in combination with document data and classification data, it results in poor response time.You may want to look at BADI_DOCUMENT_SEARCH01 for influencing the search sequence to improve the performance.


            So it doesn't matter if I use one or several classes?

            Not unless you intend to reuse the classes elsewhere,else even one class would suffice.

             

            Regards,

            Pradeepkumar Haragoldavar

Actions