Grouper Users - Open Discussion List

["Sachdeva, Vivek" <>]

Hi,

I am trying to figure out the best way to achieve a requirement. I need to populate user table in the UI like below.

Name,   User Id,    Primary department,  Primary Division,     Primary School,              Non Primary Departments

Vivek,    786876,   English,                            Humanities,              Letter and Sciences,     Maths, Law

John,      565655,   Neurology,                     blank,                          Medicine,                        blank                     

Our current hierarchy structure which is in the development stage looks like below:

ucla:college-letter-sciences:humanities:english:appointed:[primary]:set of people

ucla:college-letter-sciences:humanities:english:appointed:[non-primary]:set of people

ucla:college-letter-sciences:humanities:english:prospect:[primary]:set of people

ucla:college-letter-sciences:humanities:english:prospect:[non-primary]:set of people

ucla:law:appointed:[primary]:set of people

ucla:law:appointed:[non-primary]:set of people

ucla:law:prospect:[primary]:set of people

ucla:law:prospect:[non-primary]:set of people

The above two examples show that there is not a standard structure. Basically, one school can have a division under it and the other school might not have it. So I have attached the metadata (attributes) to the folder names to figure out if a folder is a school, division, department or sub-department.

So currently I am thinking of achieving the requirement by calling the membership service which will give me all the group names a person is member of. Then, I can look at the last word of the fully qualified group name and tell if it is a primary or non-primary. So, after that for all the groups names I received, I can break the group name into separate words like (ucla , college-letter-sciences, humanities, english) and call the attribute service to know if the folder is a school or department or division. And in the end I can populate the table. 

My concern is that it is going to be slow because I will be doing a lot of string parsing, calling the attribute service to know what is the level of the folder. Plus the use case requires it to be done on a list of users at once. 

Is there a better way of doing it? 

Am I missing any basic grouper component which can help me achieve it ? 

Should I store some data in the separate database for fast lookups ?

Thanks,

Vivek