3,572 bytes added,
12:54, 14 June 2023 Loading and identifying objects via RFID on the {{UBIK Client}} implies that the objects and the search mechanisms are configured and used accordingly. This guide describes how to prepare objects using {{UBIK Studio}}.
Please be aware that since {{Version/ServerSince|4.4.0}} Version 4.4.0 we support defining multiple codes for one object. Even if we support (for downward compatibility) both approaches (one code per object and multiple codes per object) we recommend to use the new technique even if there is only one code per object. If you are using an older version please navigate to .
== ID Marker ==
UBIK provides a new Entity called ID Marker {{Version/ServerSince|4.4.0}} since 4.4.0!
ID Markers are used to define the scannable Codes on a central location. We differ 3 types of Codes: RFID, BarCode and QR-Code.
The Code must be entered in the property "MARKER", the type is specified using the property "MAKER_TYPE" and the property OWNER refers to the object/ubiqule which is presented by the code. You can specify as many codes for one object as you like.
If later a code is scanned and found in the ID Markers, the referenced object will be added to the result collection.
=== Preparing an ID Marker Scan-Query ===
We provide a new MetaClass "RFIDTAGSCANQUERY RFID tag scan queries" deriving from System.Query.QUERY. There is already one instance QRY_RFIDSCANQUERY available in it. As this query is used to support the single Code search we recommend to create a new Query instance.
# Create a new instance of RFIDTAGSCANQUERY
# Set the property "SUPPORT_MULTI_MARKERS" to true to enable the new technique.
# Set the according filter object ('''FILTEROBJECT''') similar as for other queries
# Add this new query to the list of [[SYSREL INFRASTRUCTURE|Infrastructure objects]]
# Prepare and add a [[QUERYSCOPE]] to the [[ACM]]
# Prepare and add a [[VIEWITEMS|View Item]] to the view set in the [[Context]] of the ACM<br/>
=== Preparing the object with multiple codes ===
Ensuring the object can be found by the clients offline search we need to classify the object's MetaClass as [[SYSCLS_OBJECTWITHRFIDTAGS]] <br/>
As this classification is an autonomous classification there is no need to maintain any properties. The properties and the corresponding values (all RFID MARKERS refering to one object) will be managed by the system and sent to the client automatically. <br/>
[[File:UI_RFID_scaning01.PNG|420 px|border|alt=Classify object with multiple codes|Classify object with multiple codes]]
== Single RFID ==
=== Preparing a Scan-Query ===
# [[HowTo:Create a new Query]] classified as [[SYSCLS_RFIDTAGSCANQUERY]]
# Set the according filter object ('''FILTEROBJECT''') similar as for other queries (e.g. [[HowTo:Create_a_new_Query]])<br/>[[File:UI_Marker_scaning01.png|420 px|border|alt=Create a new Query|Create a new Query]]
# Add this new query to the list of [[SYSREL INFRASTRUCTURE|Infrastructure objects]]
# Prepare and add a [[QUERYSCOPE]] to the [[ACM]]
# Prepare and add a [[VIEWITEMS|View Item]] to the view set in the [[Context]] of the ACM<br/>[[File:UI_Marker_scaning02.png|420 px|border|alt=infrastructure|infrastructure]]
=== Preparing the object ===
# Ensuring the object can be found by the clients offline search we need to classify the object's MetaClass as [[SYSCLS_OBJECTWITHRFIDTAG]] and implement the necessary properties<br/>[[File:UI_RFID_scaning02.png|420 px|border|alt=Classify object|Classify object]]
# Enter the value of the RFID in the property
== See also ==
* [[HowTo:Find_Objects_by_Optical_Codes]]