Dear Seb,

 

Thank you very much for the kind fixes!

 

I have tested the new REF2014 Bazaar package 1.0.1 and it works for our R4R-featured repository. I didn’t see any error when I installed the Bazaar package. Also I did a manual run “epadmin upgrade <archiveid>” and no errors popped up which double confirmed the database schema upgrading succeeded.

 

But there was an issue that I need to manually copy the content of the following two files into the file “/opt/eprints3/archives/<archive_id>/cfg/workflows/user/default.xml”.

 

·         /opt/eprints3/lib/workflows/user ref.xml

·         /opt/eprints3/lib/workflows/user uoa_champion.xml

 

Otherwise, I cannot see the REF section and UoA Champion section displaying in the User Profile. I am not sure whether it’s Bazaar related or 3.3.8 version related. Additionally our EPrints version was 3.2.6 before and it got upgraded to 3.3.7 last December and then further to the current version 3.3.8 this January. This is not a critical problem, but it did took me a while to notice.

 

Another small bug is that one phrase is missing in the file “/opt/eprints3/lib/lang/en/phrases/ref.xml”, therefore I added the following line into that file.

            <epp:phrase id="user:workflow:stage:ref:title">UoA Champion</epp:phrase>

 

I followed the User Guide Manual on EPrints website to perform several simple tests on the REF2014 plug-in and it seems working perfectly. Thanks again for the great help!

 

Best Wishes,

Jia

 

 

Dear Seb,

 

Thanks a lot for the quick update. I will give a try either this afternoon or tomorrow morning and let you know how it goes.

 

Best Wishes,

Jia

 

 

 

Package now updated (v.1.0.1) -  could you please let me know if that fixed your problem?

Thanks,
Seb.

On 06/03/12 11:41, Tian, Jia wrote:

Dear Seb,

 

Thanks  a lot for the update. I will take a try.

 

Best Wishes,

Jia

 

 

 

Jia,

I'll update the Bazaar package today. However, you should still be able to edit the local files (the ones in cfg.d/) even if the package comes from the Bazaar.

Seb.

On 05/03/12 17:28, Tian, Jia wrote:

Dear Seb,

 

Thanks a lot for the quick reply!

 

It might not be possible to comment the fields out if the installation is through BAZAAR. But I can try to download the TAR and install manually to see what happen.

 

Best Wishes,

Jia

 

 

 

Hi Jia,

Thanks for reporting this issue, I had overlooked the fact that people may have R4R installed.

If you can access your repository via SSH, simply edit the file /opt/eprints3/archives/<ARCHIVE_ID>/cfg/cfg.d/zz_ref.pl and comment the conflicting fields. Everything should then be ok.

I'll be issuing a bug fix tomorrow.

Seb.

On 05/03/12 17:17, Tian, Jia wrote:

Dear All,

 

I have seen there is a new version of REF2014 plug-in released last Thursday which can be installed via BAZAAR.

 

However, I got the same error when trying to install via BAZAAR. In the homepage of REF2014 plug-in, there says the REF2014 plug-in can be used parallel with R4R, but unfortunately it’s not true unless the duplicate fields get renamed. Could someone advice how to resolve the conflict?

 

Best Wishes,

Jia

 

 

 

Dear All,

 

Sorry to bother again. I was trying to install REF2014 plug-in on our demo server which runs 3.3.8. However, when I tried to upgrade the database schema. I got a system error complaining about a duplicate field “user.dob” as followed:

 

------------------------------------------------------------------

---------------- EPrints System Error ----------------------------

------------------------------------------------------------------

Duplicate field name encountered: user.dob

------------------------------------------------------------------

EPrints System Error inducing stack dump

 at /opt/eprints3/bin/../perl_lib/EPrints.pm line 143

        EPrints::abort('EPrints') called at /opt/eprints3/bin/../perl_lib/EPrints/DataSet.pm line 615

        EPrints::DataSet::register_field('EPrints::DataSet=HASH(0x9f2a208)', 'EPrints::MetaField::Date=HASH(0x9f2a978)', 0) called at /opt/eprints3/bin/../perl_lib/EPrints/DataSet.pm line 584

        EPrints::DataSet::process_field('EPrints::DataSet=HASH(0x9f2a208)', 'HASH(0x9da8c38)', 0) called at /opt/eprints3/bin/../perl_lib/EPrints/DataSet.pm line 507

        EPrints::DataSet::new('EPrints::DataSet', 'repository', 'EPrints::Repository=HASH(0x99d1ba4)', 'name', 'user', 'search', 'HASH(0x9da8920)', 'triggers', 'HASH(0x9da895c)', ...) called at /opt/eprints3/bin/../perl_lib/EPrints/Repository.pm line 1328

 

        EPrints::Repository::_load_datasets('EPrints::Repository=HASH(0x99d1ba4)') called at /opt/eprints3/bin/../perl_lib/EPrints/Repository.pm line 475

        EPrints::Repository::load_config('EPrints::Repository=HASH(0x99d1ba4)') called at /opt/eprints3/bin/../perl_lib/EPrints/Repository.pm line 153

        EPrints::Repository::new('EPrints::Repository', 'kuirdemo', 'noise', 1) called at /opt/eprints3/bin/../perl_lib/EPrints.pm line 491

        EPrints::repository('EPrints=HASH(0x99d1b80)', 'kuirdemo', 'noise', 1) called at ./epadmin line 367

        main::repository('kuirdemo') called at ./epadmin line 1792

        main::update_database_structure('kuirdemo') called at ./epadmin line 312

 

 

I have checked my database and indeed there exists a field “dob” in the “user” table already because of R4R plug-in.

 

After I compared the “zz_r4r.pl” file (R4R plug-in) and “zz_ref.pl” (REF2014 plug-in), I can see several duplicate fields defined (not only the “dob” field):

 

 

I wonder how I can resolve this issue while keeping the R4R plug-in which I found is useful. Shall I simply comment out the duplicate field definitions in the “zz_ref.pl” file and continue? If so, would it influence the using of REF2014 plug-in? Thank you so much for the kind help in advance!

 

Best Wishes,

Jia

 

 

Jia Tian

Systems Analyst, Infrastructure, Information Services

 

T   Internal: 62079

T   020 8417 2079

 

Kingston University London

Penrhyn Road, Kingston upon Thames KT1 2EE

www.kingston.ac.uk

 

Information in this email and any attachments are confi dential, and may not be copied or used by anyone other than the addressee, nor disclosed

to any third party without our permission. There is no intention to create any legally binding contract or other commitment through the use of this email.

Please consider the environment before printing this email.

 

This email has been scanned for all viruses by the MessageLabs Email
Security System.

This email has been scanned for all viruses by the MessageLabs Email
Security System.

This email has been scanned for all viruses by the MessageLabs Email
Security System.

*** 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/

 

This email has been scanned for all viruses by the MessageLabs Email
Security System.

*** 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/

 

This email has been scanned for all viruses by the MessageLabs Email
Security System.

*** 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/

 

This email has been scanned for all viruses by the MessageLabs Email
Security System.

This email has been scanned for all viruses by the MessageLabs Email
Security System.