Adding user custom fields to reads and hits

To associate a user’s metadata with individual Genetec Patroller™ reads and hits so you can query and filter for those user custom fields in Security Desk Reads and Hits reports, you can add user custom fields to LPR annotation fields.

Before you begin

Configure Genetec Patroller™ to require a username and/or password to log on (see the Genetec Patroller™ Administrator Guide).

What you should know

You cannot add custom fields to reads and hits if Genetec Patroller™ is set to “No logon”, because the reads and hits must be attached to a valid username.

To add user-related custom fields to reads and hits:

Create the custom field that applies to user entities.
Define the custom field for your Genetec Patroller™ users.
Add the custom field as an annotation field.

The custom field is now available as two separate columns in Security Desk “Reads” and “Hits” reports. One is a Custom field column that displays the latest value configured for the User entity. The other column is an Annotation field column that displays the value for the User entity when the read or hit was stored by the LPR Manager role. For more information about Viewing LPR events in Security Desk, see the Security Center User Guide.

Example

You have several Genetec Patroller™ users that alternate between different patrol teams, such as police officers moving between different city zones. By defining each patrol team as a user custom field, you can generate a report in Security Desk that displays the reads or hits collected when the officer was in patrol team A, patrol team B, and so on.