Re: [Dspace-tech] OAI Harvesting Problem in 3.1
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
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
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
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
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
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
