DSpace

Hi,

> Hi, is there anyone who can help me to add user statistics in dspace. I am
> using 1.4 and running this in Fedora core 7.

See: http://www.dspace.org/index.php?option=com_content&task=view&id=147

Instructions are under the section titled 'Configuring System Statistical
Reports'.

Thanks,


Stuart
_________________________________________________________________

Gwasanaethau Gwybodaeth                      Information Services
Prifysgol Aberystwyth                      Aberystwyth University

            E-bost / E-mail: Stuart.Lewis@...
                 Ffon / Tel: (01970) 622860
_________________________________________________________________

On Mon, Apr 28, 2008 at 8:14 PM, Stuart Lewis <sdl@...> wrote:

> See: http://www.dspace.org/index.php?option=com_content&task=view&id=147
>
> Instructions are under the section titled 'Configuring System Statistical
> Reports'.
>

I have already followed this doc. But, i am facing problem at the time of
$in_directory. What is it actually??
I gave the directory location of *log* of dspace directory there. *
/usr/src/dspace/log*

But, it didn`t work! When i go to run the *
/usr/src/dspace/bin/stat-report-initial*   command, then the error comes:
"*Failed to read input file"
"Failed to read input file"
"Failed ......"
.....
*


-- 
Best,
Z

On Tue, Apr 29, 2008 at 9:14 AM, Cameron, Jacob <jacob.cameron@...>
wrote:

>  Did you run stat-initial first?
>
>
>
Yes, I ran it before. And this stat-initial can save it`s data to it`s
$out_directory=/usr/src/dspace/logs/
And, i gave the same location ( /usr/srce/dspace/logs/ ) for $in_directory
of stat-report-initial.
But, it didn`t solve!

-- 
Best,
Z

On Tue, Apr 29, 2008 at 10:45 AM, Zico <mailzico@...> wrote:

>
>
> On Tue, Apr 29, 2008 at 9:14 AM, Cameron, Jacob <jacob.cameron@...>
> wrote:
>
> >  Did you run stat-initial first?
> >
> >
> >
> Yes, I ran it before. And this stat-initial can save it`s data to it`s
> $out_directory=/usr/src/dspace/logs/
> And, i gave the same location ( /usr/srce/dspace/logs/ ) for $in_directory
> of stat-report-initial.
> But, it didn`t solve!
>

And, another thing. The reports files are creating in
/usr/src/dspace/reports. Cause, i can see those files in html form in
/usr/src/dspace/reports. But, the thing is, these reports cannot connect  my
192.168.3.36 ( that server ).
On the top of these html files, it shows the error that, "cannot connect to
localhost.localdomain".

I am really waiting for your word.


-- 
Best,
Z

Hi Zico,

>> I have already followed this doc. But, i am facing problem at the time of
>> $in_directory. What is it actually??

When you run stat-initial (or stat-monthly / stat-general) it takes the
files [dspace]/log/dspace.log* and makes some statistical data files in
[dspace]/log/*****.dat

When you then run the jobs to create the reports (e.g. stat-report-initial)
the $in_directory relates to the location of these .dat files.

Some checks to carry out:

 - Do the [dspace]/log/dspace.log files appear as expected?
 - After running stat-initial, are [dspace]/log/***.dat files created?
 - Are $start_year and $start_month the same in all the stat scripts?

>> I gave the directory location of log of dspace directory there.
>> /usr/src/dspace/log
>> 
>> But, it didn`t work! When i go to run the
>> /usr/src/dspace/bin/stat-report-initial   command, then the error comes:
>> "Failed to read input file"
>> "Failed to read input file"
>> "Failed ......"
>> .....

Assuming all the checks above are OK, then you'll need to edit some java
code to work out what exactly is going on. (This has been included in 1.5 by
default). 

Open [dspace-src]/src/org/dspace/app/statistics/ReportGenerator.java and
find the following code around line 632:

  632         String record = null;
  633         try
  634         {
  635             fr = new FileReader(input);
  636             br = new BufferedReader(fr);
  637         }
  638         catch (IOException e)
  639         {
  640             System.out.println("Failed to read input file");
  641             System.exit(0);
  642         }

Edit line 640 so that it reads:

System.out.println("Failed to read input file: " + input);

Run an 'ant -Dconfig=[dspace]/config/dspace.cfg update' and then re-run the
stats script. It should now report what file it is not finding, and this
will help with working out what is going wrong.

Thanks,


Stuart
_________________________________________________________________

Gwasanaethau Gwybodaeth                      Information Services
Prifysgol Aberystwyth                      Aberystwyth University

            E-bost / E-mail: Stuart.Lewis@...
                 Ffon / Tel: (01970) 622860
_________________________________________________________________

On Mon, Apr 28, 2008 at 10:59:07PM +0600, Zico wrote:
> I gave the directory location of *log* of dspace directory there. *
> /usr/src/dspace/log*

Um, you shouldn't be putting logs, abstracts, or reports into
[DSpace-source]; these should be in [DSpace].  Depending on the
account used to run the statistical scripts, you may have permission
problems.

In addition to the modification mentioned in a previous reply, you may
want to add $! to the error message so you see *why* the file could
not be opened.
 
-- 
Mark H. Wood, Lead System Programmer   mwood@...
Typically when a software vendor says that a product is "intuitive" he
means the exact opposite.

While we're talking about the bin/stat-* scripts:  they really
shouldn't be configured in the scripts themselves; the file paths at
least should be placed in config/dspace.cfg so they don't get blown
away by code updates.  Shall I cook up a patch, or is someone else
already working on that?

While I'm at it, I might suggest making the start_year and start_month
commandline parameters to stat-initial and stat-report-initial.

-- 
Mark H. Wood, Lead System Programmer   mwood@...
Typically when a software vendor says that a product is "intuitive" he
means the exact opposite.

On Tue, Apr 29, 2008 at 8:04 AM, Mark H. Wood <mwood@...> wrote:
> While we're talking about the bin/stat-* scripts:  they really
>  shouldn't be configured in the scripts themselves; the file paths at
>  least should be placed in config/dspace.cfg so they don't get blown
>  away by code updates.  Shall I cook up a patch, or is someone else
>  already working on that?
>
>  While I'm at it, I might suggest making the start_year and start_month
>  commandline parameters to stat-initial and stat-report-initial.

Honest question, no snark intended: isn't DSpace jettisoning this
stats system soon anyway? Is patching it really worth the effort and
further dspace.cfg bloat?

Dorothea

-- 
Dorothea Salo dsalo@...
Digital Repository Librarian AIM: mindsatuw
University of Wisconsin
Rm 218, Memorial Library
(608) 262-5493

Hi Mark,

> While we're talking about the bin/stat-* scripts:  they really
> shouldn't be configured in the scripts themselves; the file paths at
> least should be placed in config/dspace.cfg so they don't get blown
> away by code updates.  Shall I cook up a patch, or is someone else
> already working on that?
> 
> While I'm at it, I might suggest making the start_year and start_month
> commandline parameters to stat-initial and stat-report-initial.

Some of this has already been done and is in 1.5. See the log for revision
2630 and 2680:

http://dspace.svn.sourceforge.net/viewvc/dspace?view=rev&revision=2630
http://dspace.svn.sourceforge.net/viewvc/dspace?view=rev&revision=2680

The start month and year are now stored in dstat.cfg rather than in each
script. The scripts have been replaced with Java classes, so that people
running DSpace on windows don't have to worry about installing Perl.

The values for the input and output directories are taken from dspace.cfg,
using the log.dir and report.dir properties.

Does that cover everything you wanted?

Cheers,


Stuart
_________________________________________________________________

Gwasanaethau Gwybodaeth                      Information Services
Prifysgol Aberystwyth                      Aberystwyth University

            E-bost / E-mail: Stuart.Lewis@...
                 Ffon / Tel: (01970) 622860
_________________________________________________________________

That should do nicely.  Thank you!

-- 
Mark H. Wood, Lead System Programmer   mwood@...
Typically when a software vendor says that a product is "intuitive" he
means the exact opposite.