Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Tags Encapsulate Queries

IP.com Disclosure Number: IPCOM000235425D
Publication Date: 2014-Feb-26
Document File: 6 page(s) / 164K

Publishing Venue

The IP.com Prior Art Database


Disclosed is a tag that encapsulates a query and works with conventional tags.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 50% of the total text.

Page 01 of 6

Tags Encapsulate Queries

Disclosed is a tag that encapsulates a query and works with conventional tags. Tags are useful for simple grouping/filtering, but more sophisticated grouping/filtering requires a programming language. The language typically performs queries on a data model. The language for the query can be written by hand, but is often created with a visual builder. For example:

Rational Team Concert* features a query editor that visually builds a query for database of work items.

IBM Systems Director* features a visual editor to create dynamic groups of resources; the

dynamic groups are actually queries to the resource database.

    In these examples, there is an underlying language that a user can type by hand if desired, instead of using the visual builder. The problem is that many users need the power of a query language, but do not want to use one because of the time and complexity required. Visual builders help with this problem, but are not simple enough. The user still must think in nested expressions that are ANDed and ORed together in order to create a query. This problem exists in many applications that use queries, but especially in workload placement. There is a need for the administrator to create complex queries for placement as well as grouping/filtering, and for the operators to leverage the administrator's work when forming new queries--but without having to work at the language level themselves. Disclosed is a tag that encapsulates a query, and works with conventional tags.

    The user creates a tag that contains a query--a query tag . The query is like a database select statement; it is applied to a set of resources to retrieve a subset of matching resources. The query can be written in a language or created visually. In a UI that already uses tags, the query tag can be combined with conventional tags and with other query tags. A casual user who does not know the query language can use the query tag alongside other tags. Advanced users will also save time and reduce complexity. This method applies to any application that uses tagging. For example, it could be added to Evernote**, GMail***, etc., where tags are used for grouping/filtering in the conventional way. However, the method is especially needed when the tags are used to control workload placement.

    Figure 1 below is a Tag Management screen that shows both conventional tags and query tags. The query tags have select statements in the Query column, and the tags are always shown with bold text in the UI.


Page 02 of 6

Figure 1

    For example, the "x86" tag has a select statement that matches resources with a cpuType of "x86". There is currently one resource of this type. In contrast, the "Rochester" tag is a conventional tag that must be applied manually by the user; it has been applied to five resources. The user can create a new tag by clicking the Create button, and filling out the dialog depicted in Figure 2 below:


Page 03 of 6

Figure 2

    The Query fie...