Honestly it should be all of them. Being a former developer.. you should create a hyper search, it works in the same fashion as a Google search. You have that now in a paired down manner. If I enter in the name "Jeff" I get the member Jeff and any assets assigned to Jeff. But if I have a custom field that has Jeff in it or Jeff's email has jeff in it those relations are not returned by the search. Code a real traversing solution, that returns all the hits and/or that can be filter by the intended field or asset/member/item. It will be more work up front, but then will cover everything and no longer need to be added to. Code to the relationship tree of the data fields, each parent has a child that has a relationship(many to many) (thats how the custom fields work), tie into that relationship to create the dynamic search. return the hit and it's identifer (custom or regular field name) and its relationship type (group, member asset, etc...)