Jump to: navigation, search

Difference between revisions of "QUERYSCOPE"


m (Text replacement - "{{UBIKCLIENT}}" to "{{UBIK Client}}")
 
(4 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
| title = Query Scope
 
| title = Query Scope
 
| name = QUERYSCOPE
 
| name = QUERYSCOPE
| internalname = QueryScope
+
| internalname = SystemObjects.{{PAGENAME}}
| namespace = System.ACM.Scopes<br/>Custom.ACM.Scopes
+
| namespace = System.ACM.Scopes
 
| image = [[File:SY_QUERYSCOPE.png|220px]]
 
| image = [[File:SY_QUERYSCOPE.png|220px]]
 
| imagecaption = Query Scope
 
| imagecaption = Query Scope
 
| purpose = Configure content queries
 
| purpose = Configure content queries
 
| version = 2.1.13+
 
| version = 2.1.13+
 +
| typestring = UBIK.Kernel.MetaClass
 +
| runtimetype = UBIK.Content.ACM.QueryScope
 
}}
 
}}
A QueryScope defines how a [[Query]] and its results are visualized on the {{UBIKCLIENT}} and is accessed from the [[Content Browser]] acting as a search mechanism.
+
A QueryScope defines how a [[Query]] and its results are visualized on the {{UBIK Client}} and is accessed from the [[Content Browser]] acting as a search mechanism.
  
 
== Configuration ==
 
== Configuration ==
Line 19: Line 21:
  
 
[[Category:Context scope]]
 
[[Category:Context scope]]
[[Category:System MetaClasses]]
+
[[Category:Metaclasses]]

Latest revision as of 10:13, 8 May 2015

IC METACLASS.gif Query Scope
Name QUERYSCOPE
Namespace System.ACM.Scopes
Internal Name SystemObjects.QUERYSCOPE
TypeString UBIK.Kernel.MetaClass
RuntimeType UBIK.Content.ACM.QueryScope
Purpose Configure content queries
Version 2.1.13+

A QueryScope defines how a Query and its results are visualized on the UBIK® Client and is accessed from the Content Browser acting as a search mechanism.

Configuration

Published MetaProperties as Filter Criteria
Published MetaProperties as Filter Criteria

The configuration of the query has to be done completely on the server side, where the published MetaProperties defined in the ACM serve as filter criteria on the client. If a Query is executed on the client the system verifies for each of the filter criteria if the Query possesses a suitable QueryItem and

  • evaluates the query based on the configuration of the query item using the specified operator, etc. if a query item exist
  • evaluates the query using an equal (=) operator if no query item exist