[EP-tech] Correct EPrints Export/Import syntax and issues

Peter West pjw at repositoryservices.co.uk
Wed Feb 1 10:22:27 GMT 2017


I quite like eprints_root but I worry that it is introducing another 
version of base_path which does have the advantage that you can (almost) 
see what base_path means when you look at the config.
N.B. at install time it is referred to as --prefix in the configuration 
process and the indexer uses $prefix :)

Peter

On 31/01/17 23:12, Matthew Kerwin wrote:
> I use $EPROOT (including setting up environment variables so I can use
> it as-is on UNIXy systems). It’s pretty arcane, though, and would have
> to become %EPROOT% in Windows.
>
>
>
> As far as words, my preference is root > base_path > home.
>
>
>
> Cheers
>
> --
>
> *Matthew Kerwin
> <http://staff.qut.edu.au/details?id=kerwinm>** *| ITS-EIS:AS:LS | _KG-SYN <https://map.what3words.com/cards.reader.steer>_ | QUT
>
>
>
> *From:*eprints-tech-bounces at ecs.soton.ac.uk
> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] *On Behalf Of *John Salter
> *Sent:* Wednesday, 1 February 2017 00:33
> *To:* eprints-tech at ecs.soton.ac.uk
> *Subject:* Re: [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> Adam,
>
> I agree with you.
>
> I'm happy to go with whatever is least confusing to all - but a standard
> to try to stick to would be good!
>
>
>
> Anyone else with any alternative suggestions?
>
> eprints_base_path?
>
>
>
> Is there a normal way this is referred to across software in general?
>
> I'm thinking of JAVA_HOME sort of thing
> http://softwareengineering.stackexchange.com/questions/18439/why-is-catalina-home-named-that-way-and-other-interesting-program-names/18470
> - but the examples there are all Java oriented.
>
>
>
>
>
>
>
> *From:*eprints-tech-bounces at ecs.soton.ac.uk
> <mailto:eprints-tech-bounces at ecs.soton.ac.uk>
> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] *On Behalf Of *Adam Field
> *Sent:* 31 January 2017 13:56
> *To:* eprints-tech at ecs.soton.ac.uk <mailto:eprints-tech at ecs.soton.ac.uk>
> *Subject:* Re: [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> 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.
>
>
>
>
>
> isc <http://www.jisc.ac.uk/>
>
> *Adam Field*
> SHERPA services analyst developer
>
>
>
>
>
> *From: *<eprints-tech-bounces at ecs.soton.ac.uk
> <mailto:eprints-tech-bounces at ecs.soton.ac.uk>> on behalf of John Salter
> <J.Salter at leeds.ac.uk <mailto:J.Salter at leeds.ac.uk>>
> *Reply-To: *"eprints-tech at ecs.soton.ac.uk
> <mailto:eprints-tech at ecs.soton.ac.uk>" <eprints-tech at ecs.soton.ac.uk
> <mailto:eprints-tech at ecs.soton.ac.uk>>
> *Date: *Tuesday, 31 January 2017 13:42
> *To: *"eprints-tech at ecs.soton.ac.uk
> <mailto:eprints-tech at ecs.soton.ac.uk>" <eprints-tech at ecs.soton.ac.uk
> <mailto:eprints-tech at ecs.soton.ac.uk>>
> *Subject: *Re: [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> <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.
>
>
>
>
>
> *From:*eprints-tech-bounces at ecs.soton.ac.uk
> <mailto:eprints-tech-bounces at ecs.soton.ac.uk>
> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] *On Behalf Of *Alan.Stiles
> *Sent:* 31 January 2017 13:28
> *To:* eprints-tech at ecs.soton.ac.uk <mailto:eprints-tech at ecs.soton.ac.uk>
> *Subject:* Re: [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> Should be space separated I think e.g. bin/export ARCHIVEID eprint XML 1
> 2 3 4 5 10 11
>
>
>
> *From:*eprints-tech-bounces at ecs.soton.ac.uk
> <mailto:eprints-tech-bounces at ecs.soton.ac.uk>
> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] *On Behalf Of *Andrew Beeken
> *Sent:* 31 January 2017 13:13
> *To:* eprints-tech at ecs.soton.ac.uk <mailto:eprints-tech at ecs.soton.ac.uk>
> *Subject:* Re: [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> 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?
>
>
>
> *From:*eprints-tech-bounces at ecs.soton.ac.uk
> <mailto:eprints-tech-bounces at ecs.soton.ac.uk>
> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] *On Behalf Of *Andrew Beeken
> *Sent:* 31 January 2017 11:49
> *To:* eprints-tech at ecs.soton.ac.uk <mailto:eprints-tech at ecs.soton.ac.uk>
> *Subject:* Re: [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> And there we have it – export runs properly when you do it from the root
> with bin/export. Thanks folks!
>
>
>
> *From:*Andrew Beeken
> *Sent:* 31 January 2017 11:34
> *To:* 'eprints-tech at ecs.soton.ac.uk' <eprints-tech at ecs.soton.ac.uk
> <mailto:eprints-tech at ecs.soton.ac.uk>>
> *Subject:* RE: [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> That’s… likely to be the issue. Teach me for being a Microsoft noob…
>
>
>
> *From:*eprints-tech-bounces at ecs.soton.ac.uk
> <mailto:eprints-tech-bounces at ecs.soton.ac.uk>
> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] *On Behalf Of *Adam Field
> *Sent:* 31 January 2017 11:12
> *To:* eprints-tech at ecs.soton.ac.uk <mailto:eprints-tech at ecs.soton.ac.uk>
> *Subject:* Re: [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> 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.
>
>
>
>
>
> sc <http://www.jisc.ac.uk/>
>
> *Adam Field*
> SHERPA services analyst developer
>
>
>
>
>
> *From: *<eprints-tech-bounces at ecs.soton.ac.uk
> <mailto:eprints-tech-bounces at ecs.soton.ac.uk>> on behalf of Andrew
> Beeken <anbeeken at lincoln.ac.uk <mailto:anbeeken at lincoln.ac.uk>>
> *Reply-To: *"eprints-tech at ecs.soton.ac.uk
> <mailto:eprints-tech at ecs.soton.ac.uk>" <eprints-tech at ecs.soton.ac.uk
> <mailto:eprints-tech at ecs.soton.ac.uk>>
> *Date: *Tuesday, 31 January 2017 11:06
> *To: *"eprints-tech at ecs.soton.ac.uk
> <mailto:eprints-tech at ecs.soton.ac.uk>" <eprints-tech at ecs.soton.ac.uk
> <mailto:eprints-tech at ecs.soton.ac.uk>>
> *Subject: *Re: [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> 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.
>
>
>
> *From:*eprints-tech-bounces at ecs.soton.ac.uk
> <mailto:eprints-tech-bounces at ecs.soton.ac.uk>
> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] *On Behalf Of *John Salter
> *Sent:* 31 January 2017 10:24
> *To:* eprints-tech at ecs.soton.ac.uk <mailto:eprints-tech at ecs.soton.ac.uk>
> *Subject:* Re: [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> 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
>
>
>
> *From:*eprints-tech-bounces at ecs.soton.ac.uk
> <mailto:eprints-tech-bounces at ecs.soton.ac.uk>
> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] *On Behalf Of *Andrew Beeken
> *Sent:* 31 January 2017 09:55
> *To:* eprints-tech at ecs.soton.ac.uk <mailto:eprints-tech at ecs.soton.ac.uk>
> *Subject:* [EP-tech] Correct EPrints Export/Import syntax and issues
>
>
>
> 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
>
>
>
>
>
>
> *The University of Lincoln, located in the heart of the city of Lincoln,
> has established an international reputation based on high student
> satisfaction, excellent graduate employment and world-class research.*
>
>
> The information in this e-mail and any attachments may be confidential.
> If you have received this email in error please notify the sender
> immediately and remove it from your system. Do not disclose the contents
> to another person or take copies.
>
> Email is not secure and may contain viruses. The University of Lincoln
> makes every effort to ensure email is sent without viruses, but cannot
> guarantee this and recommends recipients take appropriate precautions.
>
> The University may monitor email traffic data and content in accordance
> with its policies and English law. Further information can be found at:
> http://www.lincoln.ac.uk/legal.
>
>
> 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.
>
>
>
> *** 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/
> *** EPrints developers Forum: http://forum.eprints.org/
>



More information about the Eprints-tech mailing list