So you want to give ezPAARSE a try, and get it to operate with an ezProxy/BiblioPAM/Squid installation.
Here are a few questions you might ask and the answers we may provide you, based on what has been done where ezPAARSE is currently installed and used.
R Although ezPAARSE itself is provided at no cost under a GPL-compatible licence, the costs involved, outside the working time necessary to set it up, are related to the prerequisites :
R : Only as an estimate :
R : At the Inist-CNRS and at the Université de Lorraine, currently, no.
R : At the Inist-CNRS : Yes, a directory with logins and passwords corresponding to the search units of the CNRS.
R : At the Université de Lorraine : Yes, we use the University's LDAP directory.
R : At the Inist-CNRS : Local, on a server deidated to statistics management.
R : There's an Excel sheet provided with the Windows installation and also available in the download page for minimal analysis. For optimal use though, you may consider using data visualisation software, such as Business Object, Visokio Omniscope or QlikView.
R : Yes. The SSL configuration is everything but trivial and requires a good knowledge of the network configuration (domain name) and Public Key Infrastructure (abbr. PKI).
Each of our log files can be as much as 100 MB, whereas as the CSV files created from 7 days of these files is only 5-10 MB.
R : EZPaarse CSV files will only contains “consultation event”. Every other lines of log as CSS, PNG ou JS file will be automaticaly ignored by ezpaarse because as a documentary point of view these lines are noise. The technical reality is the user's browser will download a lot of things which are not, for example, a PDF ARTICLE or an EPUB BOOK_SECTION … When visiting a web page, the browser will download a lot of noise. Furthermore, maybe some publisher platforms are not still handled by ezpaarse. These platforms will also be ignored by ezpaarse until someone create a parser. Ezpaarse platforms are listed on this page.
(Since version 2.2.0) You tried the latest version of the Windows installer and expected a command window would start up and run node.js and then be able to access your local Ezpaarse installation from a web browser (using http://localhost:59599).
We have actually discontinued the delivery of a complete and Windows compatible ezPAARSE replaced it with the lighter install you experienced that only redirects to our public sites http://ezpaarse.couperin.org and http://analogist.couperin.org
We made this choice because a lot of functionalities were difficult to port on windows, especially the way ezPAARSE is able to synchronise with the github repository for its source code and parsers' code.
The virtualbox + docker approach is now actually this only way to go for a windows installation. It is described on https://github.com/ezpaarse-project/ezpaarse#use-with-docker