mirror of
https://github.com/13hannes11/bachelor_thesis.git
synced 2024-09-04 01:11:00 +02:00
move definition to concept
This commit is contained in:
@@ -191,12 +191,6 @@ A hybrid recommender combines different recommendation approaches to use the str
|
|||||||
|
|
||||||
A group recommender system is a recommender system aimed at making recommendations for a group instead of a single user. To make recommendations group members preferences have to be aggregated. This can be done by either aggregating single user recommendations or by merging preferences of each user into a group preference model. Based on the resulting preference model recommendation strategies as described in \autoref{sec:Foundations:RecommenderSystem} can be used to generate recommendations \cite{jamesonRecommendationGroups2007}.
|
A group recommender system is a recommender system aimed at making recommendations for a group instead of a single user. To make recommendations group members preferences have to be aggregated. This can be done by either aggregating single user recommendations or by merging preferences of each user into a group preference model. Based on the resulting preference model recommendation strategies as described in \autoref{sec:Foundations:RecommenderSystem} can be used to generate recommendations \cite{jamesonRecommendationGroups2007}.
|
||||||
|
|
||||||
For a group recommender system additional definitions are needed. The attitude of a user is represented by their preferences $P$ which is directly related to the utility a user has from a domain value being present in the configuration. Let
|
|
||||||
\begin{gather} \label{tab:Foundations:GroupRecommenderSystem:Preferences}
|
|
||||||
P = \{ P_1, \dotsc, P_n\},\ \text{where} \\
|
|
||||||
P_i = \{(d,\ u_i(d)) \ | \ \forall d \in \mathfrak{D}(i),\ i=1,\dotsc,m \} \notag
|
|
||||||
\end{gather}
|
|
||||||
|
|
||||||
\todo[inline]{example of a group recommender}
|
\todo[inline]{example of a group recommender}
|
||||||
\todo[inline]{go more into detail about preference aggregation}
|
\todo[inline]{go more into detail about preference aggregation}
|
||||||
|
|
||||||
|
|||||||
@@ -46,6 +46,14 @@ a users \emph{utility function} that maps a domain value to a utility value and
|
|||||||
\end{split}
|
\end{split}
|
||||||
\end{equation}
|
\end{equation}
|
||||||
|
|
||||||
|
\subsection{Group Recommender}
|
||||||
|
|
||||||
|
For a group recommender system additional definitions are needed. The attitude of a user is represented by their preferences $P$ which is directly related to the utility a user has from a domain value being present in the configuration. Let
|
||||||
|
\begin{gather} \label{tab:Foundations:GroupRecommenderSystem:Preferences}
|
||||||
|
P = \{ P_1, \dotsc, P_n\},\ \text{where} \\
|
||||||
|
P_i = \{(d,\ u_i(d)) \ | \ \forall d \in \mathfrak{D}(i),\ i=1,\dotsc,m \} \notag
|
||||||
|
\end{gather}
|
||||||
|
|
||||||
|
|
||||||
\section{Requirements}
|
\section{Requirements}
|
||||||
\label{sec:Concept:Requirements}
|
\label{sec:Concept:Requirements}
|
||||||
|
|||||||
Reference in New Issue
Block a user