wp3 and wp4 repository core intelligent maintenance and use n.
Skip this Video
Download Presentation
WP3 and WP4: Repository core, Intelligent maintenance and use

Loading in 2 Seconds...

play fullscreen
1 / 35

WP3 and WP4: Repository core, Intelligent maintenance and use - PowerPoint PPT Presentation

  • Uploaded on

www.sciX.net. WP3 and WP4: Repository core, Intelligent maintenance and use. Žiga Turk (LJU), Tomo Cerovšek , Vlado Stankovski (FGGI), Brian C l ifton ( Salford ). IST- 200 1- 3 3 127. IST- 200 1- 3 3 127. September 8, 2014. introduction. Content. coverage: WP2 (part), WP3, WP4

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'WP3 and WP4: Repository core, Intelligent maintenance and use' - will

Download Now An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
wp3 and wp4 repository core intelligent maintenance and use


WP3 and WP4: Repository core, Intelligent maintenance and use

Žiga Turk (LJU),Tomo Cerovšek, Vlado Stankovski (FGGI), Brian Clifton (Salford)



September 8, 2014



  • coverage: WP2 (part), WP3, WP4
    • D12, D13 (type pilot)
    • reported in D10 due March 31st
  • overview
    • context
    • services
    • applications
  • demonstration of applications
    • Scenario 1: digital library
    • Scenario 2: eJournal
  • demonstration of Web services
    • the WSDL of the interfaces
    • OAI compatibility
    • Office 2003 “research” compatibility
  • WP4 intelligent maintenance and use
    • status and plans
  • future work
scix target users

authors, readers, editors, mentors


journal publishers

conference organizers


readers, editors


search for, study, review, recommend, discuss literature

set up archives, journals, organize conferences

edit sci. publications for professionals

create websites, software …


SciX Target Users
addressing user needs


Addressing user needs
  • all except programmers
    • they will use SciX applications via browser
    • they will SciX services via other clients such as Office 2003, Reference Manager ...
  • programmers, integrators will build new applications by:
    • re-using, modifying SciX applications
    • building new applications using SciX web services interface
    • accessing SciX data using OAI-PMH as well as SciX’s WSDL described interfaces


  • provide building blocks that can be used to support different scientific publishing models
  • these building blocks are the web services
web services in scix


Web Services in SciX
  • HTTP transport for all
  • applications are built on top of services, which are described in WSDL
  • services
    • XML, XML-RPC, SOAP (default)
    • OAI-PMH (metadata harvesting)
    • Office 2003 research


Other User

SciX Scientific User

SciX Industry User

Application layer providing functionality to end user (Web/servlet based)


Value added publications

3rd party application 1

3rd party application 2





web service


citation management, office 2003

XML protocols over HTTP

Business object layer providing web services to applications

other Metadata Harvester OAIster

VAP Content



OAi adapter



User management







Data layer








SciX Metadata Harvester

VAP Syndication



External 3rd party archives (OAI-PMH compliant)

ready now

Personal archives

Society archives




ready later

Institution archives

Hosted archives

non SciX

services and applications


Services and applications
  • services
    • repository,contributions, users (user management), selections, ratings, forum, series, journal workflow, conference workflow
  • applications
    • digital library
      • English (4) itc, elpub, iaps, europia, cumincad
      • German (2)
      • Slovenian (1) filozofija.scix.net
    • journal
      • www.ITcon.org
    • conference
      • 2004.ecppm.org
      • 2004.iaps.org
repository p


Repository (P)
  • Handling metadata and full text
  • The repository provides Dublin Core compatibility in the sense that any Web pages it creates provide proper Dublin Core head elements.
  • Compatible with citation management systems by providing BibTex, Refer and Harvard formats for the data input.
  • Access rights, the repository service can be set up in various ways; in some cases anonymous users would get full rights, in others, only registered users would be allowed access.
knowledge management a


Knowledge management (A)
  • Current implementation is based on the Bow toolkit developed at the University of Michigan for clustering and statistical text analysis.
  • Allows for automatic classification and clustering of works in a repository, searching for similar papers etc.
  • Tested with one application (itc.scix.net). Seamless integration with the rest of the system is subject to work in WP4 and D14.
collections p


Collections (P)
  • Allows end users to publish collections of papers that they have found interesting in a repository, together with an introductory commentary
  • The envisioned use - a teacher collects a reading list for his students and publishes that.
user management p


User management (P)
  • All services have a built with a notion of a user and of a group of users.
  • They use this for access right management and personalization of the services.
  • The generic user management service takes care of adding new users, authentication of users, log-in, preferences management etc.
  • The service allows for user log-in, display end editing of her profile, setting and changing of the password, lost password recovery etc.
  • The maintenance of the user identity allows other services to remember user's search history, subscriptions personalized notifications in the repository (or collection, discussion or any other service).
reviews p b


Reviews (P,B)
  • Works in the repository may be reviewed. The review is part of a workflow that is different in journals, conferences or reviews that take place after a paper has been published in a repository that is not part of a traditional peer-reviewed media.
  • Generic and conference review service have been set up. Reviewing service was only implemented for the IAPS 2004.
  • Also implemented in itcon journal.
discussions p


Discussions (P)
  • Discussions are very similar to annotation with the following differences: they are public and they are structured in the sense that a discussion is followed by another discussion forming a tree-like structure.
ratings p


Ratings (P)
  • Rating service allows users to rate contents of other services. Typically, repository items are rated by the end users.
news p


News (P)
  • News is a content management system that allow repository editors and maintainers to publish news about an application, instructions, documents etc.
  • Also add any other unstructured information to the application.
demonstration scenario 1 itc digital library

DL demo

Demonstration scenario 1:itc digital library
  • searching
  • advanced search
  • export to citation manager
  • various kinds of browsing
    • new items, keywords, authors …
  • machine made categorization (WP4)
  • logging in opens advanced features
    • creating a collection
    • publishing a collection
demonstration scenario 1 cont elpub

DL demo

Demonstration scenario 1 (cont): elpub
  • rating a paper
  • discussing a paper
demonstration scenario 2 e journal infrastructure


Demonstration scenario 2:e-journal infrastructure
  • Process
    • submit a paper to ITcon
    • automatic notification to the editor
    • editor assigns reviewers
    • reviewers do review
    • technical editor does technical review
    • editor does final verdict on the paper
    • editor publishes the paper
  • Only selected steps will be demonstrated
complex process based on earlier analysis


Complex process ... based on earlier analysis
  • Requirements (D8)
  • Process models (D1 and D2)
  • Sequence diagram (D9)
  • implemented in software (D3)
requirements d8


Requirements (D8)
  • 1.1 Journals/journal editors
    • Much of the functionality required here relates to the submission and review process.
  • 1.1.1 Managing editorial board members
    • Editors need to be able to record and manage membership of the editorial board of an online journal, with appropriate profile information.
  • 1.1.2 Selection of Reviewers
    • Editors need to be able to select reviewers for a particular article based on a match with their profile. Some degree of automated support could be provided for this.
  • 1.1.3 Submission of drafts to reviewers
    • Drafts need to be submitted to reviewers either by sending them, or by notification of the availability of a draft at a specified location on the internet. Some mechanism needs to be in place to allow the reviewer to accept or decline a request to review and article.
  • 1.1.4 Status tracking of reviewing and notification of events
    • Editors need to be notified of events occurring in the submission/review/publication process, including: receipt of a submitted paper, receipt of a review,
  • 1.1.5 Statistics about review process
    • Editors need to see statistical information regarding the process of review and acceptance. This includes information about the responsiveness and reliability of particular reviewers as well as general information about average times to publish, etc.
demonstration 3 services

web services

Demonstration 3: Services
  • internal communication using Web Services paradigm
  • WSDL Examples
    • repository service
    • rating service
  • OAI Compatibility
  • Office 2003 Compatibility
  • POSTing data into repository service

web services

  • web services provided by all services are described in WSDL
  • SOAP, HTTP and MIME bindings supported
  • used internally
  • can be used by a generic WSDL/SOAP client such as XML spy

web services

  • OAI 2.0 compliant
  • code based on open source code by Virginia Polytechnic Institute and State University, Department of Computer Science, Digital Library Research Laboratory
  • on-line validation 0 errors
office 2003
Office 2003
  • “research task pane”
  • API documented Nov. 7 2003
  • SOAP based
    • SciX services were ready
  • up and running now
next steps in development deployment


Next steps in development/deployment
  • 1.1.2004 ... ITcon Vol. 9 uses the editorial services
  • 1.1.2004 ... transition of CUMINCAD
  • 31.1.2004 ... clustering, full text indexing
  • 31.1.2004 ... advanced user management
  • 31.3.2004 ... incorporating critique from usability studies, assessment and evaluation