Re: [Dspace-tech] OAI Harvesting Problem in 3.1

2014-10-04 Thread emilio lorenzo

Hi, Renton
anyway I think (if i´m wrong, please correct me)  that oai import must 
be issued periodically (we do it daily via a cron job)

thanks
Emilio



El 03/10/2014 14:54, RENTON Scott escribió:
Thanks Emilio- that's exactly what it was. I was sure that I had run 
this recently- perhaps something else cleared out the index.


Thanks also Hilton, for replying. I can do a GetRecord in oai_dc as 
well now.


Cheers everyone
Scott

Scott Renton
Systems Developer, Library  University Collections
24 Buccleuch Place, 2nd Floor Right
tel: 515219



From: emilio lorenzo elore...@arvo.es mailto:elore...@arvo.es
Date: Friday, 3 October 2014 13:02
To: Scott RENTON scott.ren...@ed.ac.uk 
mailto:scott.ren...@ed.ac.uk, dspace-tech 
dspace-tech@lists.sourceforge.net 
mailto:dspace-tech@lists.sourceforge.net

Subject: Re: [Dspace-tech] OAI Harvesting Problem in 3.1

Hi
can you re-issue the /bin/dpace oai import command
and checkif  it is importing your  3576 records...
It seems the oai index is completely empty...

regards
Emilio



El 03/10/2014 13:26, RENTON Scott escribió:

Hi folks

I'm quite familiar with the set-up for OAI crosswalks in 1.x, but 
have hit upon some problems with 3.1. If you look at this repo you'll 
see no matches for query for oai_dc, marc or uketd_dc, but 
everything else works.


http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListRecordsmetadataPrefix=oai_dc

I've done nothing to configure oai_dc, presuming that it would all be 
there by default.


However, as with the changes, there is no longer an oaicat.properties 
file, where I would expect to see this:


# List the supported metadataPrefixes along with the class that 
performs the associated crosswalk

Crosswalks.oai_dc=org.dspace.app.oai.OAIDCCrosswalk

...and I see the DC stuff is now in SimpleDCDisseminationCrosswalk.java.
org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = DC, \
org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = dc, \

I assume that it uses the 
config/crosswalks/metadataformats/oai_dc.xsl coming from xoai.xml, 
which mentions oaidc, not oai_dc at the top, but I don't see how 
xoai.xml gets called.


Overall, I suppose what I am not understanding is how it knows  what 
to do when called with oai_dc, which 
http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListMetadataFormats (picked 
up from xoai.xml?) definitely suggests we should be passing in.


Just wondering if there are any known issues with using OAI out of 
the box for oai_dc in 3.1, and if there are any changes or patches I 
need to make it work?


Thanks very much
Scott


Scott Renton
Systems Developer, Library  University Collections
24 Buccleuch Place, 2nd Floor Right
tel: 515219




The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk


___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette:https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette




The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk


___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] OAI Harvesting Problem in 3.1

2014-10-04 Thread Hilton Gibson
Also see: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Daily_Admin

*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025C
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa

Tel: +27 21 808 4100 | Cell: +27 84 646 4758

On 4 October 2014 09:20, emilio lorenzo elore...@arvo.es wrote:

  Hi, Renton
 anyway I think (if i´m wrong, please correct me)  that oai import must be
 issued periodically (we do it daily via a cron job)
 thanks
 Emilio



  El 03/10/2014 14:54, RENTON Scott escribió:

  Thanks Emilio- that's exactly what it was. I was sure that I had run
 this recently- perhaps something else cleared out the index.

  Thanks also Hilton, for replying. I can do a GetRecord in oai_dc as well
 now.

  Cheers everyone
 Scott

  Scott Renton
 Systems Developer, Library  University Collections
 24 Buccleuch Place, 2nd Floor Right
 tel: 515219



   From: emilio lorenzo elore...@arvo.es
 Date: Friday, 3 October 2014 13:02
 To: Scott RENTON scott.ren...@ed.ac.uk, dspace-tech 
 dspace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] OAI Harvesting Problem in 3.1

   Hi
 can you re-issue the /bin/dpace oai import command
 and checkif  it is importing your  3576 records...
 It seems the oai index is completely empty...

 regards
 Emilio



  El 03/10/2014 13:26, RENTON Scott escribió:

 Hi folks

  I'm quite familiar with the set-up for OAI crosswalks in 1.x, but have
 hit upon some problems with 3.1. If you look at this repo you'll see no
 matches for query for oai_dc, marc or uketd_dc, but everything else works.


 http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListRecordsmetadataPrefix=oai_dc

  I've done nothing to configure oai_dc, presuming that it would all be
 there by default.

  However, as with the changes, there is no longer an oaicat.properties
 file, where I would expect to see this:

  # List the supported metadataPrefixes along with the class that performs
 the associated crosswalk
 Crosswalks.oai_dc=org.dspace.app.oai.OAIDCCrosswalk

  …and I see the DC stuff is now in SimpleDCDisseminationCrosswalk.java.
org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = DC, \
   org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = dc, \

  I assume that it uses the config/crosswalks/metadataformats/oai_dc.xsl
 coming from xoai.xml, which mentions oaidc, not oai_dc at the top, but I
 don't see how xoai.xml gets called.

  Overall, I suppose what I am not understanding is how it knows  what to
 do when called with oai_dc, which
 http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListMetadataFormats 
 (picked
 up from xoai.xml?) definitely suggests we should be passing in.

  Just wondering if there are any known issues with using OAI out of the
 box for oai_dc in 3.1, and if there are any changes or patches I need to
 make it work?

  Thanks very much
 Scott


  Scott Renton
 Systems Developer, Library  University Collections
 24 Buccleuch Place, 2nd Floor Right
 tel: 515219




 The University of Edinburgh is a charitable body, registered in
 Scotland, with registration number SC005336.



 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog 
 Analyzerhttp://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk



 ___
 DSpace-tech mailing 
 listDSpace-tech@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/dspace-tech
 List Etiquette: 
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette




 The University of Edinburgh is a charitable body, registered in
 Scotland, with registration number SC005336.



 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog 
 Analyzerhttp://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk



 ___
 DSpace-tech mailing 
 listDSpace-tech@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/dspace-tech
 List Etiquette: 
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette




 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer

 http

[Dspace-tech] OAI Harvesting Problem in 3.1

2014-10-03 Thread RENTON Scott
Hi folks

I'm quite familiar with the set-up for OAI crosswalks in 1.x, but have hit upon 
some problems with 3.1. If you look at this repo you'll see no matches for 
query for oai_dc, marc or uketd_dc, but everything else works.

http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListRecordsmetadataPrefix=oai_dc

I've done nothing to configure oai_dc, presuming that it would all be there by 
default.

However, as with the changes, there is no longer an oaicat.properties file, 
where I would expect to see this:

# List the supported metadataPrefixes along with the class that performs the 
associated crosswalk
Crosswalks.oai_dc=org.dspace.app.oai.OAIDCCrosswalk

...and I see the DC stuff is now in SimpleDCDisseminationCrosswalk.java.
  org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = DC, \
  org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = dc, \

I assume that it uses the config/crosswalks/metadataformats/oai_dc.xsl coming 
from xoai.xml, which mentions oaidc, not oai_dc at the top, but I don't see how 
xoai.xml gets called.

Overall, I suppose what I am not understanding is how it knows  what to do when 
called with oai_dc, which 
http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListMetadataFormats 
(picked up from xoai.xml?) definitely suggests we should be passing in.

Just wondering if there are any known issues with using OAI out of the box for 
oai_dc in 3.1, and if there are any changes or patches I need to make it work?

Thanks very much
Scott


Scott Renton
Systems Developer, Library  University Collections
24 Buccleuch Place, 2nd Floor Right
tel: 515219


The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] OAI Harvesting Problem in 3.1

2014-10-03 Thread Hilton Gibson
This works for me:
http://scholar.sun.ac.za/oai/request?verb=GetRecordmetadataPrefix=oai_dcidentifier=oai:scholar.sun.ac.za:10019.1/255

Cheers

hg

*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025C
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa

Tel: +27 21 808 4100 | Cell: +27 84 646 4758

On 3 October 2014 13:26, RENTON Scott scott.ren...@ed.ac.uk wrote:

  Hi folks

  I'm quite familiar with the set-up for OAI crosswalks in 1.x, but have
 hit upon some problems with 3.1. If you look at this repo you'll see no
 matches for query for oai_dc, marc or uketd_dc, but everything else works.


 http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListRecordsmetadataPrefix=oai_dc

  I've done nothing to configure oai_dc, presuming that it would all be
 there by default.

  However, as with the changes, there is no longer an oaicat.properties
 file, where I would expect to see this:

  # List the supported metadataPrefixes along with the class that performs
 the associated crosswalk
 Crosswalks.oai_dc=org.dspace.app.oai.OAIDCCrosswalk

  …and I see the DC stuff is now in SimpleDCDisseminationCrosswalk.java.
org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = DC, \
   org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = dc, \

  I assume that it uses the config/crosswalks/metadataformats/oai_dc.xsl
 coming from xoai.xml, which mentions oaidc, not oai_dc at the top, but I
 don't see how xoai.xml gets called.

  Overall, I suppose what I am not understanding is how it knows  what to
 do when called with oai_dc, which
 http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListMetadataFormats 
 (picked
 up from xoai.xml?) definitely suggests we should be passing in.

  Just wondering if there are any known issues with using OAI out of the
 box for oai_dc in 3.1, and if there are any changes or patches I need to
 make it work?

  Thanks very much
 Scott


  Scott Renton
 Systems Developer, Library  University Collections
 24 Buccleuch Place, 2nd Floor Right
 tel: 515219



 The University of Edinburgh is a charitable body, registered in
 Scotland, with registration number SC005336.


 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer

 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 List Etiquette:
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] OAI Harvesting Problem in 3.1

2014-10-03 Thread emilio lorenzo

Hi
can you re-issue the /bin/dpace oai import command
and checkif  it is importing your  3576 records...
It seems the oai index is completely empty...

regards
Emilio



El 03/10/2014 13:26, RENTON Scott escribió:

Hi folks

I'm quite familiar with the set-up for OAI crosswalks in 1.x, but have 
hit upon some problems with 3.1. If you look at this repo you'll see 
no matches for query for oai_dc, marc or uketd_dc, but everything 
else works.


http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListRecordsmetadataPrefix=oai_dc

I've done nothing to configure oai_dc, presuming that it would all be 
there by default.


However, as with the changes, there is no longer an oaicat.properties 
file, where I would expect to see this:


# List the supported metadataPrefixes along with the class that 
performs the associated crosswalk

Crosswalks.oai_dc=org.dspace.app.oai.OAIDCCrosswalk

...and I see the DC stuff is now in SimpleDCDisseminationCrosswalk.java.
org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = DC, \
org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = dc, \

I assume that it uses the config/crosswalks/metadataformats/oai_dc.xsl 
coming from xoai.xml, which mentions oaidc, not oai_dc at the top, but 
I don't see how xoai.xml gets called.


Overall, I suppose what I am not understanding is how it knows  what 
to do when called with oai_dc, which 
http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListMetadataFormats (picked 
up from xoai.xml?) definitely suggests we should be passing in.


Just wondering if there are any known issues with using OAI out of the 
box for oai_dc in 3.1, and if there are any changes or patches I need 
to make it work?


Thanks very much
Scott


Scott Renton
Systems Developer, Library  University Collections
24 Buccleuch Place, 2nd Floor Right
tel: 515219




The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk


___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] OAI Harvesting Problem in 3.1

2014-10-03 Thread RENTON Scott
Thanks Emilio- that's exactly what it was. I was sure that I had run this 
recently- perhaps something else cleared out the index.

Thanks also Hilton, for replying. I can do a GetRecord in oai_dc as well now.

Cheers everyone
Scott

Scott Renton
Systems Developer, Library  University Collections
24 Buccleuch Place, 2nd Floor Right
tel: 515219



From: emilio lorenzo elore...@arvo.esmailto:elore...@arvo.es
Date: Friday, 3 October 2014 13:02
To: Scott RENTON scott.ren...@ed.ac.ukmailto:scott.ren...@ed.ac.uk, 
dspace-tech 
dspace-tech@lists.sourceforge.netmailto:dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] OAI Harvesting Problem in 3.1

Hi
can you re-issue the /bin/dpace oai import command
and checkif  it is importing your  3576 records...
It seems the oai index is completely empty...

regards
Emilio



El 03/10/2014 13:26, RENTON Scott escribió:
Hi folks

I'm quite familiar with the set-up for OAI crosswalks in 1.x, but have hit upon 
some problems with 3.1. If you look at this repo you'll see no matches for 
query for oai_dc, marc or uketd_dc, but everything else works.

http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListRecordsmetadataPrefix=oai_dc

I've done nothing to configure oai_dc, presuming that it would all be there by 
default.

However, as with the changes, there is no longer an oaicat.properties file, 
where I would expect to see this:

# List the supported metadataPrefixes along with the class that performs the 
associated crosswalk
Crosswalks.oai_dc=org.dspace.app.oai.OAIDCCrosswalk

...and I see the DC stuff is now in SimpleDCDisseminationCrosswalk.java.
  org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = DC, \
  org.dspace.content.crosswalk.SimpleDCDisseminationCrosswalk = dc, \

I assume that it uses the config/crosswalks/metadataformats/oai_dc.xsl coming 
from xoai.xml, which mentions oaidc, not oai_dc at the top, but I don't see how 
xoai.xml gets called.

Overall, I suppose what I am not understanding is how it knows  what to do when 
called with oai_dc, which 
http://openaccess.sruc.ac.uk/dspace-oai/request?verb=ListMetadataFormats 
(picked up from xoai.xml?) definitely suggests we should be passing in.

Just wondering if there are any known issues with using OAI out of the box for 
oai_dc in 3.1, and if there are any changes or patches I need to make it work?

Thanks very much
Scott


Scott Renton
Systems Developer, Library  University Collections
24 Buccleuch Place, 2nd Floor Right
tel: 515219





The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.




--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk



___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.netmailto:DSpace-tech@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

[Dspace-tech] OAI Harvesting- Problem With ID/NCName

2010-03-25 Thread RENTON Scott
Hi folks

I've got a test repository that I'm checking for harvestability using the OAI 
Repository Explorer at http://re.cs.uct.ac.za/. I get an error for this (and 
any other repository I have access to)- see end of e-mail. It concerns the 
handle value assigned to amdSec and dmdSec ID and NCName.

I'm assuming this problem stops harvesting from taking place (especially as 
it's on GetRecord!). Everything else seems ok.

As the URI is created on-the-fly, I'm unaware of what I can do to prevent this 
error; however the handle it's using is obviously one set up by default on 
dspace, and I have not gone to handle.net to set a 'real one'. Might that solve 
the problem? Or could it be because I am using /oai (which does exist as a 
webapp)/request and my syntax is not quite right?

If anyone's seen it before and has any suggestions, I'd be very grateful.

Thanks
Scott

(24) Testing : GetRecord (identifier, metadataPrefix)
URL : 
http://image-projects-test.lib.ed.ac.uk/oai/request?verb=GetRecordidentifier=oai:repo-test.lib.ed.ac.uk:123456789/9metadataPrefix=mets
-- Response from Xerces Schema Validation --
[Error] re.DvZjvM:7:35: cvc-datatype-valid.1.2.1: 'DMD_hdl_123456789/9' is not 
a valid value for 'NCName'.
[Error] re.DvZjvM:7:35: cvc-attribute.3: The value 'DMD_hdl_123456789/9' of 
attribute 'ID' on element 'dmdSec' is not valid with respect to its type, 'ID'.
[Error] re.DvZjvM:23:66: cvc-complex-type.2.3: Element 'mods:relatedItem' 
cannot have character [children], because the type's content type is 
element-only.
[Error] re.DvZjvM:23:66: cvc-complex-type.2.4.b: The content of element 
'mods:relatedItem' is not complete. One of 
'{http://www.loc.gov/mods/v3:titleInfo, http://www.loc.gov/mods/v3:name, 
http://www.loc.gov/mods/v3:typeOfResource, 
http://www.loc.gov/mods/v3:genre, http://www.loc.gov/mods/v3:originInfo, 
http://www.loc.gov/mods/v3:language, 
http://www.loc.gov/mods/v3:physicalDescription, 
http://www.loc.gov/mods/v3:abstract, 
http://www.loc.gov/mods/v3:tableOfContents, 
http://www.loc.gov/mods/v3:targetAudience, http://www.loc.gov/mods/v3:note, 
http://www.loc.gov/mods/v3:subject, 
http://www.loc.gov/mods/v3:classification, 
http://www.loc.gov/mods/v3:relatedItem, 
http://www.loc.gov/mods/v3:identifier, http://www.loc.gov/mods/v3:location, 
http://www.loc.gov/mods/v3:accessCondition, 
http://www.loc.gov/mods/v3:extension, 
http://www.loc.gov/mods/v3:recordInfo}' is expected.
[Error] re.DvZjvM:25:45: cvc-complex-type.2.3: Element 'mods:titleInfo' cannot 
have character [children], because the type's content type is element-only.
[Error] re.DvZjvM:25:45: cvc-complex-type.2.4.b: The content of element 
'mods:titleInfo' is not complete. One of '{http://www.loc.gov/mods/v3:title, 
http://www.loc.gov/mods/v3:subTitle, http://www.loc.gov/mods/v3:partNumber, 
http://www.loc.gov/mods/v3:partName, http://www.loc.gov/mods/v3:nonSort}' 
is expected.
[Error] re.DvZjvM:26:59: cvc-complex-type.2.3: Element 'mods:titleInfo' cannot 
have character [children], because the type's content type is element-only.
[Error] re.DvZjvM:26:59: cvc-complex-type.2.4.b: The content of element 
'mods:titleInfo' is not complete. One of '{http://www.loc.gov/mods/v3:title, 
http://www.loc.gov/mods/v3:subTitle, http://www.loc.gov/mods/v3:partNumber, 
http://www.loc.gov/mods/v3:partName, http://www.loc.gov/mods/v3:nonSort}' 
is expected.
[Error] re.DvZjvM:31:35: cvc-datatype-valid.1.2.1: 'TMD_hdl_123456789/9' is not 
a valid value for 'NCName'.
[Error] re.DvZjvM:31:35: cvc-attribute.3: The value 'TMD_hdl_123456789/9' of 
attribute 'ID' on element 'amdSec' is not valid with respect to its type, 'ID'.
[Error] re.DvZjvM:32:13: cvc-complex-type.4: Attribute 'ID' must appear on 
element 'rightsMD'.
[Error] re.DvZjvM:72:245: cvc-datatype-valid.1.2.1: '123456789_9_1' is not a 
valid value for 'NCName'.
[Error] re.DvZjvM:72:245: cvc-attribute.3: The value '123456789_9_1' of 
attribute 'ID' on element 'file' is not valid with respect to its type, 'ID'.
[Error] re.DvZjvM:77:248: cvc-datatype-valid.1.2.1: '123456789_9_3' is not a 
valid value for 'NCName'.
[Error] re.DvZjvM:77:248: cvc-attribute.3: The value '123456789_9_3' of 
attribute 'ID' on element 'file' is not valid with respect to its type, 'ID'.
/tmp/re.DvZjvM: 9005;29;0 ms (53 elems, 59 attrs, 0 spaces, 3445 chars)

Scott Renton
MIMS Project Officer
Digital Library Development
University Of Edinburgh
2 Buccleuch Place
Edinburgh
EH8 9LW

0131 651 5219

scott.ren...@ed.ac.uk 
-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

[Dspace-tech] OAI Harvesting problem

2009-10-13 Thread George Kozak
Hi...

Someone contacted me and told me that they can only harvest 199 records 
from our various collections.  We are using DSpace 1.5.2.  They said 
that they only get 1 resumption token in the harvest.

I know in the config file it says:
# Optional: DSpace uses 100 records as the limit for the oai responses. 
You can
# alter this by changing 
$DSPACE_SOURCE_DIR/src/org/dspace/app/oai/DSpaceOAICatalog.java to 
modify the
# declaration:
# private final int MAX_RECORDS = 100 to private final int MAX_RECORDS = 30
# oai.didl.maxresponse = 0

But does that limit the number of resumption tokens as well?

-- 
***
George Kozak
Digital Library Specialist
Division of Library Information Technologies (DLIT), Digital Media Group
501 Olin Library
Cornell University
607-255-8924
***
g...@cornell.edu


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech