This is the Github repository of the EU-funded project EEXCESS.
EEXCESS develops open source software for augmenting web channels like web sites or social networks with cultural heritage and scholarly content. It consists of several sub-projects that combine into a privacy-preserving, personalized recommendataion service for cultural heritage and scholalry content. It consists of the following components:
-
A federated recommender system, that recommends resources from distributed cultural heritage and scholarly data providers. Recommendations are personalized on the one hand, but also privacy-preserving on the other hand. Besides the federated recommendataion, we also provide tools for data mapping based on Semantic Web standards and for privacy-perservation (see the Privacy Proxy).
-
Client-side augmentation and visualisation technologies to inject cultural heritage and scholarly content into habitually used user channels. This includes injecting recommendations into HTML pages via a Chrome Extension, into content management systems like Wordpress, into Google Apps for Works and into social networks like Twitter.
-
Several proof-of-concept that take up additional usage routes for cultural heritage and scholarly content. For example, a Cultural Heritage Game with a Purpose (CGWAP) as well as an Android App for recommending Europeana Content.
The project is currently under development, so not all functionality is realised yet. Below you can find more details on the architecture and furhter information on the source code managment/components. If you have any qeustion, idea or issue, please get in contact with us.
The EEXCESS source is organised in Git submodules. So every individual sub-module maintains its own Git repository and also provides a standalone solution. This EEXCESS main repositories brings all the parts together.
Note that when cloning the repo you need to init and update the submodule once:
git clone https://github.com/EEXCESS/eexcess.git
cd eexcess
git submodule init
git submodule update
Alternatively you can use '--recursive' as option
git clone --recursive https://github.com/EEXCESS/eexcess.git
-
The Wordpress Plugin for recommending cultural and scholarly content while editing a Wordpress blog. It is foreseen to deploy the Wordpress Plugin Directory.
-
The Google Chrome Extension for recommending cultural and scholarly content while browsing the web. The Extension is also available through the Chrome Web Store.
-
A Twitter Bot recommending scholarly content to Twitter users. The bot listens to certain keywords and send recommendations to users. If a user starts following the Twitter Bot, she gets recommendations regularly.
-
A Google Docs Plugin/App that allows to query for cultural and scholarly resources when writing a Google Docs document. For example, found images can be reused in the document (if they have an apropriate license) or citation can be inserted.
- The Federated Recommender queries distributed partner recommenders and merges their results. Partner recommenders are available for collections of Europeana, ZBW, Collections Trust (via Europeana), Wissenmedia's Brockhaus and KBL-AMBL's KIM Portal.
- The Privacy Proxy serves as privacy ensuring filter for request to the federated recommender. The developed protocol ensures that user id and query are separated. Further, queries can be obfuscated to ensure a high degree of privacy while retaining recommender accuracy.
- Tools for Data Quality Assurance.
- Prototype for the Blog Crawler
- Prototype for the Blog Analyzer
-
An Android App that recommends Europeana results based on your current location.
-
A Cultural Game with a Purpose (CGWAP) which allows players to ask and answer cultural questions. Answers have to be given as links and the goal is to be as fast as possible in finding the answer on Europeana.
- The FacetScape presents a visualisation widget usable for faceted browsing of cultural heritage resources. The visualisation can be used independently of the recommender framework.
Detailed descriptions are given in the individual components. The overall documentation is available in the Wiki of this repository.
All contibutions shoud follow the best practice branching model, as oultined here