I think eprints_home is confusing.  I prefer eprints_root – the eprints user also has a home directory, which may or may not be set to the eprints_root directory.  Internally, this directory is called base_path (as in $dir = $repository->config(‘base_path’)), but I still prefer eprints_root.

 

 

 

<slap!>

 

That should be:

[EPRINTS_HOME]/bin/export ARCHIVEID eprint XML 1 2 3 4 5 10 11

 

:o)

 

If you've got perldoc installed on your machine, you can do:

> perldoc [EPRINTS_HOME]/bin/export

To see the documented* details.

 

*sometime code inspection reveals additional magic.

 

 

 

Should be space separated I think e.g. bin/export ARCHIVEID eprint XML 1 2 3 4 5 10 11

 

 

Okay, so I’ve got a full dataset and a single record on export – for testing purposes what is the correct syntax for a range of records? Comma delimited EPrint ID’s?

 

 

And there we have it – export runs properly when you do it from the root with bin/export. Thanks folks!

 

 

That’s… likely to be the issue. Teach me for being a Microsoft noob…

 

 

If you’re *in* the bin folder, you’ll need:

 

./<command>

 

type ‘which <command>’ and it’ll tell you what’s actually running.

 

Unlike MS-Dos, the current directory is never assumed to be in the execution path.

 

 

 

Thanks John,

 

Yes, I’m running these while sat in the /bin folder – probably should have been more specific ;P

 

I’ll give that more specific export a try and see what happens.

 

 

Hi Andrew,

Should you be calling '~/bin/export' and '~/bin/import'?

'export' is a different unix command entirely (as is 'import')!

 

If you're calling the right thing, I'd suggest trying to export a single item using:

 

> bin/export ARCHIVEID eprint XML 1

 

This *should* export eprint #1 - if this doesn't exist, try another one!

 

Cheers,

John

 

 

Right, I’ve been trying to get my head around the back end import/export routine for EPrints.

 

Exporting from our current live box generates an xml file for me, however the xml file is empty. I’ve left this running to see if it would populate in the background but this never seems to happen. The command I’m running is:

 

export <MYARCHIVE> archive XML > filename.xml

 

As this hasn’t been working I decided to take an image from the front end by doing a search and extracting the results as EPrints XML. I don’t know if that is affecting the next step!

 

On Import to a local Virtual Machine with EPrints set up I’ve tried a couple of things. The syntax I’m using is:

 

import <MYARCHIVE> --verbose --enable-import-fields --update --force archive XML filename.xml

 

Running this as the eprints user in this environment throws this error:

 

No protocol specified

Import.im6: unable to open X server ‘:0’ @ error/import.c/ImportImageCommand/368.

 

The “no protocol specified” error, on some Googling, suggests that the eprints user does not have sufficient rights to run this command. So I decided to run it with a sudo. This results in the box sitting there and doing nothing – no output, nothing happening in EPrints. I have to force quite to get any response.

 

So, I’m at a lose end with this! Am I doing something wrong in both of these cases? Any suggestions would be most welcome!

 

Best regards,

Andrew

 

 

Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.

Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.

-- The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302). The Open University is authorised and regulated by the Financial Conduct Authority.