Adding user custom fields to license plate reads and hits - Security Center 5.12

Security Center Administrator Guide 5.12

Product
Security Center
Content type
Guides > Administrator guides
Version
5.12
Language
English
Last updated
2024-09-13

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 ALPR annotation fields.

Before you begin

  • Configure Patroller to require a username and/or password to log on. For more information, see the Genetec Patroller™ Administrator Guide.

What you should know

  • If you add additional attributes to a hotlist, they are automatically added as annotation fields when a hit occurs for the hotlist. For more information on configuring hotlist attributes, see Configuring hotlist and permit attributes.
  • You cannot add custom fields to reads and hits if Patroller is set to “No logon”, because the reads and hits must be attached to a valid username.

Procedure

  1. Create the custom field that applies to user entities.
  2. Define the custom field for your Patroller users.
  3. Add the custom field as an annotation field.

Results

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 ALPR Manager role.

Example

You have several 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.