Skip to content

Development Roadmap and Release Plan Y3

Jump to bottom Edit New page
Phil Gooch edited this page Sep 15, 2015 · 113 revisions

This page gives an overview over the different milestones and planned releases for Year 3. Roughly speaking, there will be a milestone every month which includes a deployment of the components. Details and issues should be handled with the EEXCESS JIRA System. Please also link from your task descriptions below to the corresponding JIRA items for clarification.

Milestone 4th May

[JIRA for this milestone] (https://digital-jira.joanneum.at/browse/EEX/fixforversion/14118/)

WP 2/5

  • Browser Plugin update including entity centric information needs (locations, organisations, persons, categories) (UP) JIRA 264 - solved
  • Provision of a development browser plugin installable either from source or from the chrome web store (UP) JIRA 265 - solved

WP 3

  • Analysis of query strategies and definition of a query strategy (MEN)
    • List of search fields supported by each partner's API
  • Partner Badge extension with additional information (MEN)
  • Analyse source selection feedback from partner guide (MEN)
  • Finish Query Expansion and Diversity Analysis (KC)
  • Deployment of a standalone federated recommender at kc (KC) base-Url
  • Proposal for a new return format (KC) doc
  • Update of the development version recommender (KC)

WP 4

WP 6

  • Finish the implementation of the new version of the user profile GUI (Google Chrome extension).
  • Start the documentation of the code of the user profile GUI (using YUIDoc).
  • Implementation of the getRegisteredPartners on the Privacy Proxy JIRA 263.

WP7

Milestone End May

WP 3

  • Resubmit D3.2 (KC, MEN)
  • Current status of narrative paths (MEN)
  • Getting started guide experiment: reproduce partners' results in Federated Recommender (MEN)

WP 6

  • Start the implementation of the new Privacy Proxy (composed of a receiver and an issuer). -> Change of plan: implementation of the indistinguishability protocol first.
  • Start the implementation of the unlinkability protocol. -> Change of plan: implementation of the indistinguishability protocol first.
  • Integrate the new user profile data in the query generation process. -> Postponed to next month.

Milestone 1st June

[JIRA for this milestone] (https://digital-jira.joanneum.at/browse/EEX/fixforversion/14119/)

WP 2/5

WP 3

  • Step-2-step guide on how to implement a new partner recommender (MEN)
  • Alpha Deployment of Federated Recommender (KC/JRDIG)
  • MUC paper written
  • TIR paper camera ready version finished
  • CLEF paper accepted

WP 4

WP 6

  • Update the user profile UI of the Chrome extension to:
    • Change birth date to age range.
    • Integrate the new user profile data in the query generation process. -> Not finished yet (so moved to next month).
    • Handle the new request and result formats.
  • Merge the legacy code (from hackathon) with the new version (chrome-extension).
    • Get rid of unnecessary dependencies.
  • Finish the documentation of the Chrome extension code.
  • Implement a simplified version of the indistinguishability protocol (Privacy Proxy side):
    • Update the getRecommendations method (recommendation) to ensure compatibility between the two JSON formats.
    • Implement the splitQuery and mergeResult methods.
  • Implement a simplified version the indistinguishability protocol (client side):
    • Implement a dummy obfuscation mechanism to generate fake queries.
    • Implement an advanced obfuscation mechanism using a dummy group profile. -> Not finished yet (so moved to next month).
  • Create the methods to allow the OPTIONS method calls [EEX 263] (https://digital-jira.joanneum.at/browse/EEX-263).

WP 7

Milestone 1st July

[JIRA for this milestone] (https://digital-jira.joanneum.at/browse/EEX/fixforversion/14120/)

WP 2/5

  • Finished Client Modularization (UP) JIRA 270 (discussed and agreed in Lisbon)
  • move visualisations to modularised version of browser extension (KC)
  • URank integrated (KC)
  • URank ready for integration with ZBW. After the experience we can foresee integration with AMBL (KC)
  • Data integration with external portal (KC)
  • create default thumbnail images (UP) [JIRA 277] (https://digital-jira.joanneum.at/browse/EEX-277), client-side overlay with provider logo
  • implement new recommender format (should be defined by WP3 before until end of May) [JIRA-284] (https://digital-jira.joanneum.at/browse/EEX-284)
    • new format has been integrated in jarvis (the demo we showed in lisbon), some issues have been found and reported in git issue tracking
    • integration in standard browser extension still open (focusing on user interface components)
  • Alpha version of new interaction concept for the browser plugin (concept there, working on the interactive prototype)
    • reasoning: found that it would be sensible to provide a structure for gui component integration in the tab panel first, i.e. currently architectural work (the tab panel, resizable and movable)
  • google docs new prototype started (issue tracking in git), currently nearly all the features/issues requested from google reviewers have been solved

WP 3

  • Implementation of the new return format of the Federated Recommender (KC)
  • Source Selection using Language (KC)
  • Add Time Range To Secure User Profile (KC)
  • ResultList: document should contain query (KC)
  • Detailed API documentation (KC) Doc
  • MUC paper accepted (KC)
  • CLEF paper camera ready version finished (KC)
  • Deployment KC Demo Website (KC) KC-DEMO

WP4

WP6

  • Implement an advanced version of the indistinguishability protocol (Privacy Proxy side):
    • Implement an advanced obfuscation mechanism using a dummy group profile (from previous month).
    • Implement the mechanism to build the group profile.
    • Implement the mechanism to pass the group profile from the proxy to the client.
  • Client side:
    • Integrate the new user profile data in the query generation process (from previous month).

(Intermediate) Milestone 1st August

WP 2/5

  • Improvements in GDocs Plugin (UP)
    • completed all requirements from Google reviewer
  • FacetScape is modularized and scalable, can be tested in dev branch (https://github.com/EEXCESS/visualization-widgets/tree/develop) using examples/index.html (UP)
  • experiment on paragraph prediction, first promising results (UP)

Milestone 1st September

[JIRA for this milestone] (https://digital-jira.joanneum.at/browse/EEX/fixforversion/13515/)

WP 2/5

WP 3

  • Beta Deployment of the Federated Recommender (KC)
  • Development version of narrative paths web plugin (MEN)
  • Source selection on Word-Net (KC)
  • First limited evaluation of the result re-ranking and blocking approach (KC)
  • Finish Block Diversity (KC)

WP4

  • Implementation of enrichment - final version (JR-DIG)
  • new Release of ConfigTool including new features: create/share project, data qualtity features
  • new version of data qualtity tools - input data qualtity, enriched data qualtity
  • first version of ParterRecommenderSetupPage with use of maven archetype (JR-DIG)

WP 6

  • Integration of the indistinguishability protocol.

WP 7

Milestone 1st October

[JIRA for this milestone] (https://digital-jira.joanneum.at/browse/EEX/fixforversion/13516/)

WP 2/5

WP 3

  • Final Deployment of Federated Recommender (KC/JRDIG)
  • Deployment of narrative paths demonstrator at dslabs.mendeley.com (MEN)

WP4

  • BugFixes

Milestone 1st November

[JIRA for this milestone] (https://digital-jira.joanneum.at/browse/EEX/fixforversion/13517/)

WP 2/5

  • Early Bugfixes for browser plugin and google docs plugin (UP)

WP 3

  • Bugfixes
  • Concept for a configurable Open Search Partner Recommender Platform

WP4

  • BugFixes

WP 6

  • Two switchable privacy proxies. One proxy that implements the unlinkable protocol and one proxy that is just a proxy.
  • It should be two proxy for easily switching in case of sensitive queries/non-sensitiv queries or in case of performance issues

WP 7

Add a custom footer
Add a custom sidebar

Clone this wiki locally