Project News, Scope, and Goals

1
Project News, Scope, and Goals

• 6 October 2008

2
News IT

• Web site up
• Public and Private Wikis
• Development tools and guidelines

3
News Events

• ICT event in Lyon, Nov 08 presentation as
  ideal FET project
• FET event in prague, April 09 - ? DEMO ?
• CNRS workshop http//www.interdisciplines.org/liq
  uidpub
• Snow Workshop http//project.liquidpub.org/events
  /liquidpub-workshop
• CAFETERIA http//cafeteria.ning.com/

4
FET OPEN

• Reminders, also from EU
• Think bold
• Work together on the project
• Team is good if it integrates skills and
  competences, more than existing results (its not
  a STREP or IP)
• The last point was stressed being a FET OPEN,
  reusing existing results by the same team will be
  scrutinized

5
Objectives

• General
• Goals of the project
• In-Scope and Out of scope
• Functional Architecture
• WPs
• Share ideas
• Action plan for 1) deliverables and 2) joint work
  (hope is to do joint work more than integration)
• Organization / development issues
• Programmers team, software dev process

6
Goals

• Concepts, models, metrics, and tools that allow
  better and more efficient dissemination
• How to facilitate and encourage dissemination,
  and in particular early dissemination?
• How to allow open source science, and controlled
  large-scale collaboration?
• How to allow a fair and efficient (as cost free
  as possible) evaluation of scientific
  contributions
• To support search
• To support evaluation of people

7
High level functional architecture dashboard
for researcher (vision)
User Interface scientific desktop for researcher
CENTERS
Information mgmt and personalization
Research Analysis and Performance
SKO management
Lifecycle management
Project management
Job posting/search
Publication/collection
Review
Admin center

User mgmt
Developer center
gDocs
Wikis
SVN

LiquidPub codebase
springerLink
ePrints
ACM

8
Key potential contributions

• Liquid Publications as a conceptual and practical
  tool to achieve the goals
• Evolving complex objects (SKO)
• Multi-author, multi-facet,
• Comments, blogs, reviews, part of the content
• Managing collaborations in LiquidPub
• Access rights, ownerships
• Views and exports who can see what in a complex
  evolving object
• Search, navigation, and consumption
  (rendering/printing)
• Feedback via blogs and reviews and comments
  recognize that all contributes to knowledge
• Bullerd vs rigid borders what if multiple
  publications are based on the same experiment
  data? Is data part of the same object or not? Is
  it a copy?
• Evolution (and tracking changes)
• Version, branches, splitting and merging (and def
  of when there is a new version. Is a new comments
  a new version?)
• Track and view changes done by individuals or
  team. Restrict to changes done by a group of
  users
• How to manage things such as comments or blogs
  attached to an evolving and branching target?
• Citations
• what does it mean to cite a SKO, or a component?
  Especially as the SKO evolves?
• Evaluation and metrics
• How to assess feedback, so to encourage it
• How to rate in general authorship on SKOs

9
Use cases (and, what is and what is not a SKO?)

• Our state of the art document
• And, a survey paper
• And, a state of the art deliverable
• A book
• A book series?
• A course (or set of courses)
• A project?
• A meeting like this one?

10
Process Plug-ins (WP2)
Evaluation Plug-ins (WP 4)
Real-time citation analysis
Analysis of self-referencing authors and
communities
Conference paper selection and publication
Journal paper selection and publication
Classic (waterfall)
open source
Social network analysis
Reputation metrics
agile dissemination

Peer review
Community review

Extensibility/plug-ins support
Create and evolve Creation and extensions of
knowledge objects (by authors, readers,
bloggers) Manage versions, branches Snapshots
(publications)

• Read, navigate, search
• Browse through a SKO
• through its multimedia components
• through its versions and branches
• Search for SKOs of interest, for related /
  referenced content

API/service access
Web access
Core platform SKO management (WP1)
11
LiquidPub Platform High-level Functional
Architecture
User Interface dashboard for researcher
Public API
API (WP3,WP5)
API (WP1, WP5)
API (WP4,WP5)
API (WP2, WP5)
Registry API
Behavior analysis and metrics in the traditional
world (WP3)
Trust and reputation analysis (WP4)
User Registry
Lifecycle, Processes (WP2)
SKO
Non-SKO
Widgets, rendering
WP1
Widgets, rendering
Widgets, rendering
Widgets, rendering
Widgets, rendering
springerLink
ePrints
ACM

12
Short-term goal

• Initial round on high level architecture
• Define high level functional modules
• Define interactions between modules
• Define API that each module provides, at least
  conceptually
• Try to get first versions very quickly, then
  refine
• Should be a great exercise to put our minds
  together and make sure we work together on common
  goal

13
In Scope

• SKO management, navigation, search, blogging,
  tagging, comments, citation, subscriptions,
  access rights mgmt
• Plugging in processes to control arbitrary sko
  lifecycle processes. Define edit process,
  execute, bind to sko, monitor, define access
  rights on lifecycle operations
• Trust and reputation model in a sko / open source
  / web 2.0 world applied to science. Modules to
  help rate SKO, authors, rank to support search
  and evaluation
• Review simulation, analysis, de-biasing,