EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #05031
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: Possible importing BibTeX bug in monograph
- To: eprints-tech@ecs.soton.ac.uk
- Subject: [EP-tech] Re: Possible importing BibTeX bug in monograph
- From: George Mamalakis <mamalos@eng.auth.gr>
- Date: Thu, 29 Oct 2015 16:01:21 +0200
Hi all,I was wrong! I thought the import was fine in my previous snapshot, but it wasn't. I installed EPrints 3.3.14 on a clean debian (Jessie), and imported the aforementioned BibTeX file, and I had the same problem again:
$ ./bin/import --verbose --user admin testpamak1 archive BibTeX /tmp/bibtex.bib
Starting EPrints Repository. Connecting to DB ... done.Use of uninitialized value in subroutine entry at /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Id.pm line 50.
...Undefined phrase: eprint_fieldopt_monograph_type_technicalreport (en) at line 126 in /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Set.pm Undefined phrase: eprint_fieldopt_monograph_type_technicalreport (en) at line 126 in /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Set.pm
Number of records imported: 1 1 Ending EPrints Repository.You can see near the end of the warning messages that eprint_fieldopt_monograph_type_technicalreport (en) is an undefined phrase, and if I see the eprint's details, "Monograph Type" is not filled with a value (it should be "Technical Report").
Thomas (Lauke), I didn't read your initial email thoroughly (it was tooo early in the morning when I read it:)), and as I now re-read it you said that the phrase warning was raised to you too. This means that the "Monograph Type" field was not imported to you either, so if you check your import, you must see it's empty.
If you confirm this (or anybody else), I'll file a bug report to EPrints src.
Thanks all again! On 27/10/2015 04:13 μμ, George Mamalakis wrote:
Hi everybody! I checked my BibTeX file on a previous snapshot of my development machine and it was imported just fine. Thomas Lauke informed me of achieving the same results in one of his installations as well. I've also found the file that caused the first warnings (about $mesg being re-declared), removed it from my configuration, without any effect. So I'll start by removing one-by-one each config file I've changed in order to find out which is causing the problem and will try to resolve it. Thanks all for your help again! On 26/10/2015 04:17 μμ, George Mamalakis wrote:Adam, As I mentioned in my previous email, I checked the exact code you suggested and it's fine (hey, don't get me wrong, I know you're having a hard time answering all our questions in such a limited time:) ). That's why I'm curious wrt the reason I'm getting this error. If you take a closer look into my script's output (the warnings), maybe they tell you more then they tell me about resolving this issue :). Moreover, it would be enlightening if someone tried importing the sample bibtex entry of my previous email in their installation and see if it imports it correctly (using the command line to see if they get the same warnings). Thanks for helping! On 26/10/2015 01:22 μμ, Field A.N. wrote:Check you BibTex import plugin. See https://github.com/eprints/eprints/blob/3.3/perl_lib/EPrints/Plugin/Import/BibTeX.pm#L343 -- Adam Field Business Relationship Manager and Community Lead EPrints Services +44 (0)23 8059 8814 On 23 Oct 2015, at 16:30, George Mamalakis wrote:Hi everybody, When importing a @TECHREPORT from a BibTeX file in EPrints 3.3.14 -like the one I've included for PoC in the end of this email- an eprint is created that has the value technicalreport in its monograph_type variable, which is wrong (it should have been "technical_report"). As you can see from my export, some warnings are returned, some of which referring to undefined phrases in (el), so I'm not sure if it's something related to my custom multilingual configuration causing it; but if so, I have no idea how it is possible, since I'm using EPrints vanilla import utility. More specifically, that's what I get: $ ./bin/import --verbose --user admin testpamak1 inbox BibTeX /tmp/my_bibtex.txt "my" variable $mesg masks earlier declaration in same scope at (eval 153) line 114, <DATA> line 751. Possible attempt to put comments in qw() list at (eval 158) line 18, <DATA> line 751. defined(@array) is deprecated at /usr/share/eprints3/lib/plugins/EPrints/Plugin/Screen/BulkAction/Remove.pm line 46. (Maybe you should just omit the defined()?) Starting EPrints Repository. Connecting to DB ... done. Use of uninitialized value in subroutine entry at /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Id.pm line 50. Use of uninitialized value in subroutine entry at /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Id.pm line 50. Use of uninitialized value in subroutine entry at /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Id.pm line 50. Use of uninitialized value in subroutine entry at /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Id.pm line 50. Use of uninitialized value in subroutine entry at /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Id.pm line 50. Use of uninitialized value in subroutine entry at /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Id.pm line 50. Use of uninitialized value in subroutine entry at /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Id.pm line 50. Use of uninitialized value in subroutine entry at /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Id.pm line 50. Undefined phrase: eprint_fieldopt_monograph_type_technicalreport (el) at line 126 in /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Set.pm Undefined phrase: eprint_fieldopt_monograph_type_technicalreport (el) at line 126 in /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Set.pm Undefined phrase: eprint_fieldopt_monograph_type_technicalreport (el) at line 126 in /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Set.pm Undefined phrase: eprint_fieldopt_monograph_type_technicalreport (el) at line 126 in /usr/share/eprints3/bin/../perl_lib/EPrints/MetaField/Set.pm Number of records imported: 1 13229 Ending EPrints Repository. Can anyone confirm the problem in their repositories as well? If so, I suppose we should file a bug report in EPrints github. Ah, and grepping my repostitory for technicalreport returns nothing, so it's probably created dynamically from BibTeX.pm...? However, looking at my BibTex.pm's code (lines 340-344), the line adding this code seems fine (it sets a technical_report). Could this problem be related to the masking warning I get when running my import command? (and by the way, how can I find which file causes this message?) My /tmp/my_bibtex.txt content is: @TECHREPORT{RePEc:rim:rimwps:15-19, title = {The Day-of-the-Week Effect is Weak: Evidence from the European Real Estate Sector}, author = {Bampinas, Georgios and Fountas, Stilianos and Panagiotidis, Theodore}, year = {2015}, institution = {The Rimini Centre for Economic Analysis}, type = {Working Paper Series}, abstract = {The day-of-the-week effect for the securitized real estate indices is investigated by employing daily data at the global, European and country level for the period 1990 to 2010. We test for daily seasonality in 12 countries using both full sample and rolling-regression techniques. While the evidence for the former is in line with the literature, the results for the latter cast severe doubts concerning the existence of any persistent day-of-the-week effects. Once we allow our sample to vary over time, the average proportion of significant coefficients per day ranges between 15% and 24%. We show that higher average Friday returns evident in previous literature, remain significant in 21% of the rolling samples. We conclude that daily seasonality in the European Real Estate sector is subject to the data mining and sample selection bias criticism.}, url = {http://EconPapers.repec.org/RePEc:rim:rimwps:15-19} } Thanks all in advance! George -- George Mamalakis IT and Security Officer, Electrical and Computer Engineer (Aristotle Univ. of Thessaloniki), PhD (Aristotle Univ. of Thessaloniki), MSc (Imperial College of London) School of Electrical and Computer Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 *** 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/*** 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/
-- George Mamalakis IT and Security Officer, Electrical and Computer Engineer (Aristotle Univ. of Thessaloniki), PhD (Aristotle Univ. of Thessaloniki), MSc (Imperial College of London) School of Electrical and Computer Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379
- References:
- [EP-tech] Server information request
- From: "Alan.Stiles" <alan.stiles@open.ac.uk>
- [EP-tech] Re: Server information request
- From: Ian Stuart <Ian.Stuart@ed.ac.uk>
- [EP-tech] Re: Server information request
- From: "Alan.Stiles" <alan.stiles@open.ac.uk>
- [EP-tech] Possible importing BibTeX bug in monograph
- From: George Mamalakis <mamalos@eng.auth.gr>
- [EP-tech] Re: Possible importing BibTeX bug in monograph
- From: "Field A.N." <af05v@ecs.soton.ac.uk>
- [EP-tech] Re: Possible importing BibTeX bug in monograph
- From: George Mamalakis <mamalos@eng.auth.gr>
- [EP-tech] Re: Possible importing BibTeX bug in monograph
- From: George Mamalakis <mamalos@eng.auth.gr>
- [EP-tech] Server information request
- Prev by Date: [EP-tech] Re: User Login failure after upgrading from Eprints 3.3.3 to 3.3.14
- Next by Date: [EP-tech] Re: User Login failure after upgrading from Eprints 3.3.3 to 3.3.14
- Previous by thread: [EP-tech] Re: Possible importing BibTeX bug in monograph
- Next by thread: [EP-tech] Antwort: Server information request
- Index(es):