04.11.2014 Views

elektronická verzia publikácie - FIIT STU - Slovenská technická ...

elektronická verzia publikácie - FIIT STU - Slovenská technická ...

elektronická verzia publikácie - FIIT STU - Slovenská technická ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

232 Selected Studies on Software and Information Systems<br />

need to have a static snapshot available as it is with WebVip. WET is based on principle of processing<br />

of events generated by web browser. The disadvantage of such an approach could be<br />

an overhead of records because what we would define as one user interaction could fire a vast<br />

amount of events. E.g., a simple click on a hyperlink could result in a sequence of mouseover,<br />

mousedown, mouseup a click. To address this issue, WET allows for setting explicitly which<br />

types of actions are to be logged. That means that we can trace only clicks, page loads etc.<br />

The problem of WET is its tight connection to the domain of web sites usability evaluation.<br />

In fact, it creates an additional layer above the displayed page, providing control buttons to<br />

manage the monitoring process. The Click tool (Client side action recorder) is inspired by<br />

the logging part of WET (simple reference in a header part, optional types of events etc.) and<br />

sends acquired data asynchronously using SOAP messages to the server side, to a specialized<br />

web service.<br />

UAR tool (User Action Recorder) is a standalone desktop application for Microsoft Windows<br />

environment. It allows for monitoring not only user’s work within a web application<br />

but whole user – computer interaction by tracking keyboard and mouse usage in individual<br />

windows. These practically unlimited monitoring possibilities represents a significant disadvantage<br />

of this standalone desktop application approach as many users would feel this as<br />

a privacy threat.<br />

8.5.3 Bootstrapping the User Model by Exploting Communities<br />

We, people, are naturally integrated into several social communities (our relatives, friends,<br />

colleagues etc.) and are strongly influenced by these communities. If one needs to solve<br />

a “never-seen before” kind of a problem, she will very likely ask her friends for some hints<br />

and help. We rely on other people if we are in some new and unknown situation, where we<br />

are not sure about the most suitable action (e.g., “I will take the same food as others on the<br />

conference dinner”). We are behaving socially.<br />

The idea and advantages of social aspects in the real life is being transformed to the<br />

web and its applications, namely to the Web 2.0. In fact, the models of social networks are<br />

suppressing and replacing the traditional role of user model in web-based systems [3]. It is<br />

becoming the community which has ever evolving characteristics and a helpful adaptation<br />

can be provided on their basis (the system is performing community-based personalization<br />

instead of user-model-based one).<br />

The idea is taking advantage of the fact, that users are humans and humans tend to have<br />

a lot in common. Use of social relationships in computer systems is not new. We know<br />

collaborative filtering and history-enriched environments [30] as the results of pioneering<br />

work from the early 90’s [27].<br />

In fact, the cold-start problem got its name in the field of recommender systems based on<br />

collaborative (social) filtering. User is rating the content and system is using these ratings to<br />

compute user’s similarity to other users of the system. Then the system is able to recommend<br />

new content which got high ratings from similar users. A recommender system can produce<br />

good recommendations only after it has accumulated a large set of ratings, which is obviously<br />

not the case for the new user, hence the cold-start problem arises.<br />

The solution is to combine pure collaborative filtering with a content-based filtering<br />

techniques, which selects items based on the correlation between the content of the items<br />

and the user’s preferences [62] and to bootstrap the user model by other means.

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

Saved successfully!

Ooh no, something went wrong!