Browse Prior Art Database

Method for Creating a Perspective for Evaluating Relevance of Attributes of an Artifact using Metadata

IP.com Disclosure Number: IPCOM000196854D
Publication Date: 2010-Jun-18
Document File: 5 page(s) / 71K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for creating a perspective for evaluating relevance of attributes of an artifact using metadata. The method disclosed herein involves providing the capability to a user to store perspective information along with an attribute of an artifact. Thereafter, relevance of a query is determined based on the user’s perspective and the stored perspectives of previous users.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 5

Method for Creating a Perspective for Evaluating Relevance of Attributes of an Artifact using Metadata

A method is disclosed for creating a perspective for evaluating relevance of attributes of an artifact using metadata. The method involves providing the capability to a user to store perspective information along with an attribute of an artifact. Thereafter, relevance of a query is determined based on the user's perspective and the stored perspectives of previous users.

Initially, metadata associated with a query is collected and the metadata along with ranking of an item returned from the query is stored. The types of metadata to be provided with the query and stored with each item ranking include keywords entered by user to search on, profile information about user (e.g. novice/expert, developer, accountant, management, United States, etc.) that is provided by the user, and categorization information about search (e.g. programming tools, editors, XP = extreme programming) that is also provided by the user. Two or more of these metadata sets can be used to create a perspective, although all three types of the metadata are optimal.

Fig. 1 shows a relationship of these three metadata spaces used for defining perspective of a rank. Fig.1 shows a combination of three spaces used to create a perspective.

Figure 1

The metadata used in the three spaces is either input manually by a user or it can be inferred. If the metadata is manually input, the information needs to be collected somewhere between the time when a search is initiated and when a ranking is stored on an artifact. The collection can be done using drop-down menus, check-boxes, text, or any other data collection mechanism. Further, if the metadata is inferred, then the system may need to know where to find information about the search. The category space can be inferred using text analytic or similar techniques on the search space text

1

[This page contains 1 picture or other non-text object]

Page 2 of 5

to generate categories or topics. The user space can be inferred by knowing where to find out information about the user, such as their company, department, role, etc. The inferred metadata may need to be validated by the user before storage, or the metadata can be left alone. The user space metadata might also be stored and reused. The three spaces as shown in Fig. 1 combine together to define the perspective space of attributes of an artifact. In the example, an attribute is a ranking for an artifact. A statistical match is performed between a perspective space of a user initiating the query, and those that are stored with a ranking attribute for each previous user for an artifact. A threshold can be set for determining how close the perspectives should be to consider the perspectives as a match. For example, the threshold may be a 9...