*Creating Database subsets

Open

Technical Article | TA-20201002-TP-44 VDG Sense | Tutorials | Macros Open

Open

Introduction

A database subset is actually a virtual personlist within the person database. These (virtual) personlists allow you to differentiate between the persons in the matchlist. And as a result, you can create unique (macro) actions when a match event occurs. For instance, for a parking site you can make distinction between Regular guests and VIP guests. You can define different behaviour for a license plate/person which has a ‘VIP’ label assigned to and when a person has the label ‘Regular’ assigned to it.

How it works

When adding a person to the database one piece of extra information needs to be added to the ‘Notes’ field to create the subset:

Where [SubsetName] should be replaced by the name of the sub-list (spaces not allowed).

The example below will create a subset with ‘VIP’ as name.

When this person is recognized it will create the CarRMatch or FaceRMatch (Sense 2.4 only) event and a GenericEvent with value ‘VIP’.

The example below will create a subset with ‘Regular’ as name.

When this person is recognized it will create the CarRMatch or FaceRMatch (Sense 2.4 only) event and a GenericEvent with value ‘Regular’.

The Event List example below shows both cases:

How to use the Macro

The combination of the CarRMatch and FaceRMatch (Sense 2.4 only) with the GenericEvent events can be used to distinquish behaviour for the different subset. In the following two macro examples these events are used trigger two different Output ports on an I/O module. The use case for this application could be that there are two gates, a VIP entrance gate and a Regular entrance gate. Either one needs to open based on the visitor access rights; regular access or VIP access.

VIP Access Macro:

Be aware that the signal condition must be set to ‘All’.

Regular Access Macro:

Be aware that the signal condition must be set to ‘All’.