Building an Assets schema - Looking for how others have dealt with the assignment field

Question

Building an Assets schema - Looking for how others have dealt with the assignment field.

For example, you have a laptop object type and assigned to: is an attribute of laptop. Is it better to have assigned to as a User type or an Object type that references a People schema?

Wondering pros and cons on each path.

TYIA

Kai Becker · Answer

Hi @Michael Frade

thank you for your question.

Usually the assignment will be used to identify the hardware and make it selectable in e.g. a customer portal. This is slightly easier in terms of AQL for the custom field configuration when having direct access to the attribute. But the extra link to a user object which then contains the user as an attribute is also feasible.

When it comes to sharing information between two or more schemas, I would tend to create separate user objects. This makes sense for example if you would like to add more data to a user, like software assignments, roles, working hours or anything else that might be located in an extra HR scheme.

Hopefully that helps.

Robert Nadon_4pwkst · Answer

I prefer to do the later.    That way all users are associated to the same scheme., espcially if you want to import from say LDAP.