Large-Scale Element Consolidation

Comments

2 comments

  • Avatar
    Kevin Fairs

    Mike, Just to check you want an easy way to find an element which has the entire set of relationships you want to look at as populated.  

    Ie: the element type you return has 4 possible relationships, you want to test where the set you return has all 4 populated (or a user defined set of 3 populated??

    0
    Comment actions Permalink
  • Avatar
    Michael Sinyangwe

    Yes, I want an easy way to find an element which has the entire set of relationships you want to look at as populated.

     

    If you need an example situation, I'll try and give a step-by-step explanation below:

    1. I have one organisation element, which is connected to 3 permissions elements, each of which have the same three relationship field types on them.

    2. The permission 1 element has project 1 in the project relationship field type, line of business 1 in the line of business relationship field type, and function 1, 2, 3, 4, and 5, in the function relationship field type.

    3. The permission 2 element has no project in the project relationship field type, line of business 1 in the line of business relationship field type, and function 1, 2, and 3, in the function relationship field type.

    4. The permission 3 element has project 1 and 2 in the project relationship field type, line of business 1 in the line of business relationship field type, and function 1 in the function relationship field type.

    5. If I had "Access to the query find block term "Where Is All Of"", I could write a query which returns just permission 1 and 3, because based on relationship field data overlaps,  all of permission 2's relationships are contained within the superset of permission 1's relationships, but permission 3's relationships are a partial overlap with permission 1's relationships. This way, I can just return two elements covering all the relationships, rather than 3.

    6. The result is that in large-scale solutions, I will be able to:

    a. Consolidate lists of possibly tens of thousands of elements, to just hundreds, thereby reducing page-load times.

    b. Allow the admin user to skip the step where they have to individually create and delete permissions elements for each related project, line of business, or function; and indeed also the step where they have to analyse the existing permissions across 100's of organisations before they even make the permissions creations or deletions (taking into account duplicates if you like). They can simply just create a new permissions rule which relates any number of elements to the organisation, and then the solution cleverly consolidates across the many permissions in order to maintain page-load performance.

    0
    Comment actions Permalink

Please sign in to leave a comment.