Ezpaarse Versions Save

ezPAARSE can ingest your (proxy) log files and show how users access suscribed electronic ressources.

3.2.4

4 years ago

Changes

  • Update node-ezpaarse

3.2.3

4 years ago

Changes

  • Fix: always finalize report before terminating response
  • Migrate docs to Vuepress
  • Add Github Actions in order to deply docs to github pages

3.2.2

4 years ago
  • Bug fix : trust proxy headers (fix https links)

0.0.1

4 years ago

Accesses events are produced for ScienceDirect only from log files via a RESTful web service.

0.0.2

4 years ago

The MVP implemented in the first sprint can now be installed on various OSes: Ubuntu, fedora, RedHat, Suse

0.0.3

4 years ago
  • Clear documentation describing how accesses events are recognized
  • New parsers developped for various platforms
    • sd (Science Direct) : a parser without a knowledge base because a normalized identifier is found in the URL
    • npg (Nature Publishing Group) : a parser with a knowledge base because the publisher's platform uses proprietary identifiers
    • edp (EDP Sciences) : a parser for a platform that only publishes one journal (every journal is hosted on a distinct plaform but all platforms work the same way)

0.0.4

4 years ago

More log formats are accepted by ezPAARSE: EZproxy, Bibliopam, Squid

0.0.5

4 years ago
  • a windows installer is provided
  • a form for submitting logs is provided

0.0.6

4 years ago
  • upgrade to node v0.10
  • new parsers (dalloz, wiley)
  • new execution traces

0.0.7

4 years ago
  • better access events definition (rtype, MIME, unitid)
  • testing for large log quantities
  • new parsers (BMC, lamyline, lextenso, lexisnexis)
  • form redesign with dynamic metrics
  • access to traces and reject files (not recognized formats, unknown domains, etc)