Thanks David,

This didn’t work unfortunately, as it already seemed to be configured correctly.  I did create another ‘test’ eprint repository in the same tenancy and the Bazaar worked just fine.  Whatever the cause is, it is likely to be me taking something from the old config but not sure what.  I’m looking to see the differences now.

Best,

David.

Hi David,

This is due to the code where the EPM data object is defined not being included.  You may need to edit the file:

EPRINTS_PATH/flavours/pub_lib/inc

and add the line:

ingredients/bazaar

That said, I have checked backed and both EPrints 3.4 original release (i.e. 3.4.0) and 3.4.3 both have this line.  Although the way the inc file is defined in 3.4.0 is semi-colon rather than new line separated for different paths in this inc file.  If you do have an inc file that looks like:

flavours/pub_lib;site_lib;ingredients/bazaar;

It may be worth changing this to:

flavours/pub_lib
site_lib
ingredients/bazaar

CAUTION: This e-mail originated outside the University of Southampton.

Hello Folks,

 

I have just upgraded from Eprints 3.4 to 3.4.3 and the Eprints Bazaar admin page gives an internal server error.  The apache log displays “Unknown dataset: epm”.  I have no idea why this is happening.  Can anyone help point me in the right direction.  I have spent far to long trying to figure out this alone.

 

Thanks,

 

David.

 

 

---

This email is subject to the following disclaimer(s) available at WIT Disclaimer.
Tá an ríomhphost seo faoi réir an tséanta/na séanta seo leanas atá le fáil ag WIT Séanad

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech

*** Archive: http://www.eprints.org/tech.php/

*** EPrints community wiki: http://wiki.eprints.org/