Tagging

<< Click to Display Table of Contents >>

RayVentory Scan Engine > 12.6 u4 > User Guide > Settings > Inventory 

Tagging

Tagging allows users to brand all incoming or outgoing NDI files with specific meta information, which can be used later on to identify the origin of each scan. This advanced feature is useful in case of multi-tier architecture of several RayVentory Scan Engine instances or many Distribution Servers / Upload locations.

 

Settings_Tagging

 

This Settings screen contains three fields to be configured by the user:

 

Organization

This is the name of the organization performing the scan. You can enter any value that uniquely identifies your company, branch, or division.

 

Location

The location name. You can enter any value that uniquely identifies your physical, geographical, or infrastructure related location.

 

Contact

The information about the Point-Of-Contact for that particular scan. This can be a name, e-mail address, telephone number or any other value that uniquely identify the person responsible for the scan results.

 

The information provided by the user are merged with a few dynamically generated values. All NDI files receive the following information:

 

Automatically created values:

oThe date and time of the scan (property RVP-Time).

oThe name of the server that initiated the scan (property RVP-Server).

oThe version of RayVentory Scan Engine instance that initiated the scan (property RVP-Server).

Values specified by the user (only non-empty values are being written):

oThe name of the organization (property Organization).

oThe name of the location (property Location).

oThe name of the contact (property Contact).

 

All values are saved in a special entry (Hardware), having MGS_Identity as its class name and MGMT API as its evidence.

 

Conflict Handling

In case of processing of files that have already been branded by any other RayVentory Scan Engine, the original branding is kept intact. This way, the results always contain fine grained information about the low-level entity that initiated the scan.