28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

F<strong>in</strong>ally, users have the right to make their local broker store and publish their local abstracts, disregard<strong>in</strong>g the<br />

popularity of the resources. However, the broker should not supposed to recommend an abstract for replication,<br />

unless the abstract is popular.<br />

Work of a Broker <strong>in</strong> Normal Regime<br />

The normal regime describes work of a broker <strong>in</strong> the case when there is an exist<strong>in</strong>g network of <strong>in</strong>teract<strong>in</strong>g<br />

brokers and the broker we are consider<strong>in</strong>g has been work<strong>in</strong>g long enough to adapt to the environment.<br />

Publish<strong>in</strong>g<br />

Publishers supply abstracts of resources be<strong>in</strong>g published to the brokers to which the publishers have publish<strong>in</strong>g<br />

access. The brokers store these abstracts. After they have been stored and <strong>in</strong>dexed, the abstracts are available for<br />

all the queries com<strong>in</strong>g to the brokers. However, an abstract is not recommended for replication on other brokers<br />

until it becomes popular.<br />

Brokers periodically check which abstracts have collected enough votes for replication but have not been<br />

recommended for replication. For each of the abstracts from this set, the broker tries to determ<strong>in</strong>e the best<br />

broker to replicate it on us<strong>in</strong>g the F<strong>in</strong>dSimilar() function. This function takes a text A and a set of texts B and<br />

returns the texts from B that are close to A. So, the broker performs a cha<strong>in</strong> of trans<strong>format</strong>ions:<br />

F<strong>in</strong>dSimilar( abstract A to recommend, wide view + expertise groups ) -> closest abstracts -> their source<br />

brokers -> the best broker B to recommend the abstract A to. The broker sends a replication request to broker B.<br />

If B decides not to replicate the abstract A, B repeats the procedure and refers A to other brokers. More than<br />

one broker may be selected to recommend an abstract to.<br />

Search<br />

The user submits a query to their preferred broker. The broker uses the function F<strong>in</strong>dSimilar( query, all<br />

abstracts ) to get a result set. If the result set is substantially large and rank<strong>in</strong>g scores are high, the set is sent<br />

back to the user. If the user is not satisfied with the set received, they have option to ref<strong>in</strong>e the query terms or<br />

send a “more” request. Hav<strong>in</strong>g received the “more” request, the brokers that processed this query consider<br />

further distribution of the query if they do not have any more relevant abstracts to send. This enables users to<br />

expand searches more and more if not satisfied with the query results. If the broker failed to f<strong>in</strong>d results with<strong>in</strong><br />

the network of brokers, it can submit the query to an external source, such as InfoSeek.<br />

To route a query, broker performs a cha<strong>in</strong> of trans<strong>format</strong>ions:<br />

F<strong>in</strong>dSimilar( query, wide view + expertise groups ) -> closest abstracts -> their source brokers -> the best broker<br />

to route the query.<br />

Cach<strong>in</strong>g<br />

The cache manager is a component of the broker software that is responsible for implement<strong>in</strong>g the cache policy.<br />

It makes decisions on stor<strong>in</strong>g a copy of abstract <strong>in</strong> the broker. It takes <strong>in</strong>to account the local popularity of the<br />

abstract, relevance to the specialisation area of the broker and whether this abstract is easy to get from another<br />

broker if needed. It replicates an abstract if retrieval of the abstract is expensive (<strong>in</strong> terms of communication<br />

resources) or if it corresponds to the area of broker specialisation. The cache manager also decides which<br />

abstracts have to be discarded from the cache to free space for a new abstract. The cache policy is regulated by<br />

setup parameters, such as portion of the cache to allocate for the wide view group and portion for the expertise<br />

group, the maximal value of retrieval cost before replicat<strong>in</strong>g an abstract, the m<strong>in</strong>imal number of votes collected<br />

by an abstract to be replicated, etc. These values might also be used as weights for components of decision<br />

criteria.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!