Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Search-oriented portal access

IP.com Disclosure Number: IPCOM000132008D
Original Publication Date: 2005-Nov-28
Included in the Prior Art Database: 2005-Nov-28
Document File: 2 page(s) / 31K

Publishing Venue

IBM

Abstract

Disclosed is a usability improvement for portal interactivity which makes use of a singular search function for access

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

Page 1 of 2

Search-oriented portal access

Today's portals are typically organized by hierachal navigation bars or menus. Users, administrators, or explicit metadata define portal pages as invididual aggregations of available content and applications which are available to users when they select that page using a link. As the sheer number of applications available to the user grows, it becomes repetitive and increasingly cumbersome for the user to continually construct task specific pages which consist of an aggregation of related applications. Navigation also becomes increasingly deep to find content as more content becomes available. One solution to the task specific view problem is that templates are made available by a user or administrator which define the set of applications, but it is predefined, and once added to the user's portal customizations, it becomes yet another portal page which they need to manage. Navigation also becomes increasingly deep to find content as more content becomes available.

Because we're in such a well defined environment of available applications and content in a portal environment, we have a explicit domain of content which can be searched. We propose a system by which a search field is made available as the primary control for driving interaction with the portal, with one or more of the following features entering a query such as 'customer service' would update the viewed portal page to aggregate all the


1.


2.


3.

user's available applications which correlate strongly with that query entering a query such as 'customer service' would update the viewed portal page to aggregate all the

user's available applications whose contents correlate strongly with that query relevance weighting can be given to application instances which already reside on the portal user's

pages layout and/or decorate dynamically aggregated applications in such a way as to provide feedback on


4.

their relevance to the query ability to quickly 'bookmark' or store a dynamically aggregated page so that it is easily available later

to a user ability to provide continual feedback _during typing the query_ as to number of hits or a flat list

summary of content to be retrieved ability to provide continual feedback _during typing the query_ as to possible completions and their

hits (query assist) ability to provide continual content re-layouts _during typing the query_ of applications that are

relevant to the the partial query or likely completions of the partial query ability to dynamically connect and integrate dynamically provided components using any number of


9.

component integration technologies an available component sidebar which provides query filtering of available components, and in the

main page displays selected items from the result list

These functions will allow even the most content laden portal to be fluidly and quickly navigated, configured, and driven for any task.

Some implementation details are provided f...