Hi Pradip,

 

(cc’ing to dspace-tech)

 

I can’t guarantee this is the problem, but I’ve encountered this SQL error 
running stat-initial when I’ve had two metadata schemas that both had 
element/qualifier combinations that some Dspace queries expect to be unique.

 

For instance, on one of my instances I have “uow.date.accessioned”, an 
accession date from a previous repository stored in our custom “uow” metadata 
schema, but the subquery run by  stat-initial  (when it’s getting a count of 
non-withdrawn items)  looks for metadata with element ‘date’ and qualifier 
‘accessioned’ but ignores schema ID – both results are returned, and the 
exception is thrown because the subquery should only have returned one result.

 

The quick fix would be to rename the custom metadata field to something other 
than date.accessioned, or to modify the item count query so that 
“element=’date’ AND qualifier=’accessioned’ AND metadata_schema_id=1”. It seems 
pretty likely that Dublin core is always going to be schema ID ‘1’ but I guess 
I wouldn’t want to automatically assume that, either.

 

Cheers,

 

Kim

 

 

From: Pradip Patel [mailto:[email protected]] 
Sent: Monday, 10 August 2009 8:52 p.m.
To: [email protected]
Subject: [Dspace-devel] statistics

 

Dear sir 

 

we are using the following version of Dspace

Dspace 1.4.1

PostgreSQL 8.2

Apache 2.2

Apache ant 1.5

Java JRE/JDK 1.6.0

 

we installed perl  and modify the stat* files

 

# Details used

######################################################

 

$in_prefix = "dspace-log-general-";

$in_suffix = ".dat";

$out_prefix = "report-general-";

$out_suffix = ".html";

$dsrun = "f:/dspace/bin/dsrun";

$in_directory = "f:/dspace/reports";

$out_directory = "f:/dspace/reports/";

 

######################################################

 

 

but when we retun the command  f:\>perl dspace\bin\stat-initial 

 

we found error1(attachment)

 

and when run the command f:\>perl dspace\bin\stat-report-initial 

 

we found error 2 (attachment)

 

 

2 screen shot and a last lo file we are sending to you.

 

what we have to do next. and why we found that errors?

 

and why ous dspace doesn't show statistics?

 

pls help sir

 


-- 
Pradip 

Gujarat 

India

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to