• Like
  • Save
Initial proposal for DSpace statistics application
Upcoming SlideShare
Loading in...5
×
 

Initial proposal for DSpace statistics application

on

  • 3,866 views

Initial proposal for DSpace statistics application

Initial proposal for DSpace statistics application

Statistics

Views

Total Views
3,866
Views on SlideShare
3,863
Embed Views
3

Actions

Likes
0
Downloads
69
Comments
1

1 Embed 3

http://www.slideshare.net 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • hi....nice presentation...however, to avail all sorts of web services click on www.webcatalyst.org
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Initial proposal for DSpace statistics application Initial proposal for DSpace statistics application Presentation Transcript

    • Statistics application for DSpace (initial proposal) Federico Paparoni
    • Architecture
    • Request Layer
      • Informations are collected by different sources
      • The main points that will log the statistics data are:
      • Filter : a filter that logs informations about general hits and visitors of the DSpace platform
      • View: every JSPTag (ItemTag, CollectionListTag and so on) will log informations about hits and everything that can be read from HttpRequest
      • Search : searches on the DSpace platform will log searched queries
    • Request Layer/2
      • These point of logging will use a particular logger, defined in a new Log4j file properties
      • So the structure of DSpace logging will not change and a more detailed log, for statistics purposes, will be created
    • Request Layer/3
      • A possible layout of this log file:
      • 2007-04-19 17:10:28,031 INFO [Filter] Page hits from 151.100.41.12
      • 2007-04-19 17:10:30,031 INFO [Filter] Page hits from 151.100.41.12
      • 2007-04-19 17:11:40,031 INFO [View] ItemView : NameOfItem : 151.100.41.12
      • 2007-04-19 17:11:41,031 INFO [View] ItemView : HttpReferer : http://www.somehost.com
      • 2007-04-19 17:11:42,031 INFO [View] CollectionView : HttpReferer : http://www.somehost.com
    • Request Layer/4
      • The work that has to be done for this layer is :
      • Identify points of logging
      • Identify informations logged
      • Create a logfile with a suitable format
    • Core Layer
      • This layer, as the old stats application, will parse the log file and will submit informations on the DB
      • The communications between Core Module and DB can be created in different ways:
      • DSpace lib: Org.dspace.storage.rdbms
      • Hibernate
      • iBatis
    • Core Layer/2
      • Tables created and managed by Core Module will mantain the statistics informations
      • There will be also a “Cleanup module”, that will aggregate old informations on some tables, to don’t have a waste of resources
      • This “Cleanup module” can be also executed from the Web interface
    • Web Layer
      • The Web Layer will create different views, containing the informations collected
      • Communication with DB using some library (as Core Module)
      • Informations will be organized in different views, using different formats
    • Open questions
      • Open questions:
      • Private access or Public access?
      • Configuration based views?
      • JMS logging based?