EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #06369
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- From: John Salter <J.Salter@leeds.ac.uk>
- Date: Wed, 22 Mar 2017 14:51:47 +0000
OK - so it looks like the plugin is loading OK. Next, check whether the metadata prefix is correct - add this line to the end of the script (before $session->terminate). print "Metadata prefix: ", $plugin->param( "metadataPrefix" ), ".\n"; When you run the test now, for Export::OAI_DC you should get an undefined value. For OAI_DC_Ext, you should get 'oai_dc' - as defined
in the cfg.d/z_oai.pl file. If the OAI_DC plugin reports that it's metadataPrevix is also oai_dc, I think this is the problem. That plugin is responding to the
request - not the OAI_DC_Ext one. Cheers, John From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Alfredo Cosco Thanks John, I launched your script, this is the result: eprints@myhost:~/bin/local$ ./check_plugin sandbox2 Export::OAI_DC Checking Export::OAI_DC Plugin Export::OAI_DC seems to be OK... Plugin Export::OAI_DC is module: EPrints::Plugin::Export::OAI_DC. eprints@myhost:~/bin/local$ ./check_plugin sandbox2 Export::OAI_DC_Ext Checking Export::OAI_DC_Ext Plugin Export::OAI_DC_Ext seems to be OK... Plugin Export::OAI_DC_Ext is module: EPrints::Plugin::Export::OAI_DC_Ext. eprints@myhost:~/bin/local$ ./check_plugin sandbox2 Export::DC_Ext Checking Export::DC_Ext Plugin Export::DC_Ext seems to be OK... Plugin Export::DC_Ext is module: EPrints::Plugin::Export::DC_Ext. Everything seems to be OK, but It's not working. Alfredo 2017-03-22 13:04 GMT+01:00 John Salter <J.Salter@leeds.ac.uk>:
|
- References:
- [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- From: Alfredo Cosco <alfredo.cosco@gmail.com>
- Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- From: Alen Vodopijevec <alen@irb.hr>
- Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- From: Alfredo Cosco <alfredo.cosco@gmail.com>
- Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- From: Alfredo Cosco <alfredo.cosco@gmail.com>
- Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- From: Alfredo Cosco <alfredo.cosco@gmail.com>
- Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- From: Alfredo Cosco <alfredo.cosco@gmail.com>
- [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- Prev by Date: Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- Next by Date: Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- Previous by thread: Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- Next by thread: Re: [EP-tech] [Eprints 3.3.4] Plugin doesn't work on OAI-PMH push: OpenAire upgrade attempt to 3.0 compliance
- Index(es):