Deferred Transact integration using Plugin Integration: How to asscociate metadata (and timestamp) with a Video Sources?

MIP
, , , ,
1

We are integrating our ALPR solution (Plate recognition) with Transact: online integration is solved. But, now we have to integrate them into deferred circumstances (to retrive data after an off-line).

To do this, Milestone engineers have proposed us to use "Plugin Integration", using the TransactConnector.csproj MIP SDK example as a base.

However, this is a centralized way of integration and the Integrated Solution will have multiple video sources. Then, this must associate our metadata with a specific Video Source (and a specific timestamp).

  • How can we associate the metadata (and timestamp) with a specific Video Source using this “Plugin Integration”?
  • Is there an alternative way to build a deferred integration with Transact, considering that it is necessary to associate metadata with a specific video source and a specific timestamp?
2

You can associate one camera (video source) with one transact source. This will bind the Transact display and the camera display in the clients together.

3

Thanks Bo for your reply!

That is the idea, but how can we associate them?

Take in account that all metadata that could not be sent online are centralized on our server. Then, a new xProtect’s plugin (based on example TransactConnector.csproj of MIP SDK “Plugin integration”) will ask to our server about these deferred metadata to link with original camera capture.

NOTE: Our metadata are the IDs of the containers. These are obtained online from the video of the cameras.

4

Your connector should split the data into multiple Transact sources so that the association is possible.

I can see how it becomes a headache to associate many sources with many cameras so I have an idea that if you also develop functionality that creates the sources and makes the association it might make it possible.

By using the Config API Client you can see how this is possible..

configAPItransact
configAPItransact514×480 70.5 KB

5

Thanks Bo!

  • A Plugin connector (based on TransactConnector.csproj example) works as a Transact Source (inside of Event Server). How to “split” this in multiple “Transact Sources”?
  • I’ve been reviewing Config API Client: it implements a “Component Integration”, and some of its key Forms are parts of MIP SDK. Then, I cannot understand how it works, how it associate a Transact Source with a Camera (as looks in your screenshot) and if it is possible to work with the “Configuration API” to build a “Plugin Connector”.

Really a big headache!

6

When ever a new Transact Source is created in the Management Client (or using the Configuration API) there will be a new Transact Connector object. You should then develop some sort of singleton to make sure you have just one connection with your back ground integration.