EPrints Technical Mailing List Archive
Message: #06233
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Import problems!
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] Import problems!
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- Date: Wed, 1 Feb 2017 14:39:23 +0000
That’s interesting – I’ll have a check although this action is only being done on a subset of 4 or 5 records, all of which are fairly recent, so I would have hoped they’d have a status! The only
other alternative could possibly be missing status definitions etc? I shall take a look at bringing phrases over as well. From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of John Salter 'ne' means 'not equal' - when comparing strings ('!=' means not equal when comparing numbers). At a guess, something in your export doesn't have an eprint_status set (all EPrints should have this set). You may be able to find these in the database by trying something like: mysql> SELECT COUNT(*), eprint_status from eprint GROUP BY eprint_status; This should result in the eprint_status values of inbox, buffer, archive and deletion, with a count next to each. Any count for 'NULL' would show where the eprint_status is not set,
and therefore where the uninititalized string is on the import. Cheers, John From:
eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Andrew Beeken Cheers Adam, That seems to have sorted things out. However, I have another new and interesting error! Use of uninitialized value in string ne at /usr/share/eprints3/bin/../perl_lib/EPrints/DataSet.pm line 1090. The line in question is: if( $dataobj->get_value( "eprint_status" ) ne $self->{id} ) and the ne in that line is an operator if I’m not mistaken? So is this an issue with Perl running on the server? Andrew From:
eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Adam Field If you’ve added all your metadata fields to the new repositories configuration, you need to do: <eprints_root>/bin/epadmin update <repositoryid> This will update your database structure. From:
<eprints-tech-bounces@ecs.soton.ac.uk> on behalf of Andrew Beeken <anbeeken@lincoln.ac.uk> Hello all! Thanks for the pointers yesterday regarding import/export. I’m at a point where I now have exported data and am trying to import it. Initially I was getting errors relating to missing
metadata fields which I’d thought I’d corrected, however I am now finding errors relating to missing SQL tables: SQL ERROR (execute): SELECT `eprintid`,`pos`,`subjects_loc` FROM `eprint_subjects_loc` WHERE `eprintid` IN (25940) SQL ERROR (execute): Table 'lirolem.eprint_subjects_loc' doesn't exist DBD::mysql::st fetchrow_array failed: fetch() without execute() at /usr/share/eprints3/bin/../perl_lib/EPrints/Database.pm line 2674. DBD::mysql::st execute failed: Table 'lirolem.eprint_creators_browse_id' doesn't exist at /usr/share/eprints3/bin/../perl_lib/EPrints/Database.pm line 3211. SQL ERROR (execute): SELECT `eprintid`,`pos`,`creators_browse_id` FROM `eprint_creators_browse_id` WHERE `eprintid` IN (25940) SQL ERROR (execute): Table 'lirolem.eprint_creators_browse_id' doesn't exist DBD::mysql::st fetchrow_array failed: fetch() without execute() at /usr/share/eprints3/bin/../perl_lib/EPrints/Database.pm line 2674. Now, my question is, do I need to do something to rebuild the tables relating to the metadata in some way prior to an import? Or is there something else I’m missing here? Maybe not all the field
definitions? Andrew
|
- References:
- Re: [EP-tech] Import problems!
- From: Adam Field <Adam.Field@jisc.ac.uk>
- Re: [EP-tech] Import problems!
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- Re: [EP-tech] Import problems!
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] Import problems!
- Prev by Date: Re: [EP-tech] Import problems!
- Next by Date: [EP-tech] Import DOI Issue
- Previous by thread: Re: [EP-tech] Import problems!
- Next by thread: Re: [EP-tech] Import problems!
- Index(es):