EPrints Technical Mailing List Archive
Message: #00667
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Fwd: RE: OpenAIRE Compliance Plug-in http://files.eprints.org/649/
- To: eprints-tech@ecs.soton.ac.uk
- Subject: [EP-tech] Fwd: RE: OpenAIRE Compliance Plug-in http://files.eprints.org/649/
- From: Timothy Miles-Board <tmb@ecs.soton.ac.uk>
- Date: Fri, 01 Jun 2012 11:01:38 +0100
-------- Original Message -------- Subject: RE: OpenAIRE Compliance Plug-in http://files.eprints.org/649/ Date: Fri, 1 Jun 2012 10:57:58 +0100 From: Rob Ingram <Rob.Ingram@nottingham.ac.uk> To: Timothy Miles-Board <tmb@ecs.soton.ac.uk> Hi Tim,Thanks for that. However, I no longer work in RSP so I don't really have a setup to allow me to make updates to the plugin unless I can find time to set up a new VM.
May I suggest that you post your notes to the tech list so that if anybody does need to install on a 3.3 repo in the meantime they do at least know what code changes are necessary to get it working?
Cheers, Rob. -----Original Message----- From: Timothy Miles-Board [mailto:tmb@ecs.soton.ac.uk] Sent: 01 June 2012 10:53 To: rob.ingram@nottingham.ac.uk Subject: OpenAIRE Compliance Plug-in http://files.eprints.org/649/ Hi Rob, FYI I've just installed your plugin on an EPrints 3.3 repository. The OAI code has changed in 3.3 so it doesn't work out of the box. $c->{oai}->{v2}->{output_plugins}->{oai_dc} = "OAI_DC_Ext"; The OAI code no longer looks at the output_plugins setting to determine which plugin to use for each metadataPrefix. Each individual export plugin can now advertise support for a metadataPrefix so given a metadataPrefix request, the OAI code just asks the plugin subsystem for a plugin that says it supports that metadataPrefix. So in order to get the OAI_DC_Ext used instead of the default OAI_DC I needed to add the following config settings (eg. to z_oai.pl): # don't use Export::OAI_DC for oai_dc metadataPrefix... $c->{plugins}->{"Export::OAI_DC"}->{params}->{metadataPrefix} = undef; # ...use Export::OAI_DC_Ext instead $c->{plugins}->{"Export::OAI_DC_Ext"}->{params}->{metadataPrefix} = "oai_dc"; Apologies if this has already been reported to you. Regards, Tim -- Timothy Miles-Board EPrints Services School of Electronics and Computer Science University of Southampton, UK +44 (0)23 8059 3980 tmb@ecs.soton.ac.uk http://www.eprints.org/services/ Consultancy - Training - HostingThis message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.
- Prev by Date: [EP-tech] Retrieve metadata from a SWORD zip file
- Next by Date: [EP-tech] question about update an eprint on cli
- Previous by thread: [EP-tech] Retrieve metadata from a SWORD zip file
- Next by thread: [EP-tech] question about update an eprint on cli
- Index(es):