The order of the attributes shouldn’t ever matter as long as the content of each is correct and they are. I’ve no idea why that is happening.

If there are no other problems, you should see new records, at least, being indexed quite quickly, e.g., weeks. In the past however it took Google Scholar months to re-index records.

Cheers

Mark

Hi Mark,

                Default.xml now includes <epc:pin ref="head" />. The meta tags are now present in all pages generated by Archipel. However, “name” and “content” attribute are inverse :

http://www.archipel.uqam.ca/4992/

I don’t think that robot indexer will be affected by this. Any idea why this behavior ?

Thanks,

Pierre Nault

It’s notable that neither the DC or Simple metadata is appearing in the output HTML.

Check that <archivename>/cfg/lang/<lang>/templates/default.xml includes <epc:pin ref="head" /> within the head element of the html doc and add it if it’s not there. If you have multiple languages you may need to check the default template for each language.

Regards

Mark

Hi Mark,

                Thanks for the reply. In eprint_render.pl I have :

my $links = $session->make_doc_fragment();

                $links->appendChild( $session->plugin( "Export::Simple" )->dataobj_to_html_header( $eprint ) );

                $links->appendChild( $session->plugin( "Export::DC" )->dataobj_to_html_header( $eprint ) );

I’m pretty sure that Export::DC is working based on the response we have from OAI-PMH protocol. For Export::Simple I’m not sure -> where should I look if plugins are disabled ? One other thing, base code of our repository have been modified substantially. Where can I verified if the name of the field of the schema have been changed ?

Thanks,

Pierre Nault

Hi Pierre

Have a look in eprints/<archivename>/cfg/cfg.d/eprint_render.pl in the anonymous function starting:

$c->{eprint_render} = sub {

If the EPrints native metadata is being rendered you should be able to find the following lines:

my $links = $session->make_doc_fragment();

$links->appendChild( $session->plugin('Export::Simple')->dataobj_to_html_header($eprint) );

If it’s not there you should be able to add it, reload the configuration/restart httpd and it will just work.  There are caveats, e.g., if you have changed the name of fields in the schema or the plugin has been disabled.

Regards

Mark

Mark Gregson | Applications and Development Team Leader
Library eServices | Queensland University of Technology
Level 3 | R Block | Kelvin Grove Campus | GPO Box 2434 | Brisbane 4001
Phone: +61 7 3138 3782 | Web: http://eprints.qut.edu.au/
ABN: 83 791 724 622
CRICOS No: 00213J

Hi all,

                We have removed the <meta name="robots" content="noindex,nofollow" /> from default.xml. We confirm that we are running on Eprints version 3.1-2008-12-03-r3984. Anurag : you mention that all versions of eprints over 3.0 can generate the machine-readable bibliographic metadata. Obviously this is not the case for us. Following your assertion, something is probably missing in the configuration of our repository. I’m not too familiar with the config of eprints: I would much appreciate any help on activating this feature.

Best regards,

Pierre Nault