[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Testing REF CC with new Dates plugin version 1.0.5



Hi Andrew,
Yes, there's tweaking to be had :o)
*BUT* there's a slight problem which I alluded to here: http://www.eprints.org/tech.php/21379.html - regarding overwriting triggers.

You could copy the triggers in https://github.com/eprintsug/hefce_oa/blob/master/lib/cfg.d/hefce_oa_integration.pl
into a ~/archives/ARCHIVEID/cfg/cfg.d/...pl file - and tweak it to your hearts content (to pull data out of your custom fields).

The problem with this is that the out-the-box integration trigger (in lib/cfg.d/) will also be present and operational.
You *don't* really want to terminate the 'before commit' trigger early (as other things might be doing useful things) - so in this case you want to make sure your trigger runs *after* the default one - by setting it's priority.

Hope that makes sense!

Cheers,
John


-----Original Message-----
From: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Andrew Beeken
Sent: 03 March 2016 13:47
To: eprints-tech at ecs.soton.ac.uk
Subject: Re: [EP-tech] Testing REF CC with new Dates plugin version 1.0.5

Hi all,

We're actually not using the Dates plugin here as we've updated our workflow to capture the dates ourselves; with regards the Ref plugin, is it configurable to be pointed at any alternative fields or is it designed specifically to work in tandem with Dates?

Andrew

-----Original Message-----
From: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of John Salter
Sent: 01 March 2016 14:06
To: eprints-tech at ecs.soton.ac.uk
Subject: Re: [EP-tech] Testing REF CC with new Dates plugin version 1.0.5

>alerts
You can subscribe to the RSS feeds on the Bazaar - which will tell you when anything is added (this is what I use).

There's a slight difference between what RIOXX and REF should show for the date of publication - RIOXX uses it for the basis of a citation - so the 'real' publication date is most preferred.
REF needs it the other way round - published_online is preferred over published.

Will / Justin,
I'm looking into this this afternoon - will hopefully merge changes into GitHub and release new package.

Cheers,
John

-----Original Message-----
From: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Annette Moore
Sent: 01 March 2016 13:42
To: eprints-tech at ecs.soton.ac.uk
Subject: Re: [EP-tech] Testing REF CC with new Dates plugin version 1.0.5

Hi Will

Thanks for your reply.  Yes, that does shed some light on the issue.  Actually, I had just started to check the new Dates plugin with RIOXX and was wondering the sequence of events for  where REF CC is getting the Date of first online publication from, so your explanation is very helpful.  Is there a way of getting automatic alerts when a new version of a plugin is released?

Regards and thanks for your help,

Annette


Annette Moore
Technical Services Librarian

The Library
University of Sussex
Brighton
BN1 9QL

T:01273 877046
E:a.moore at sussex.ac.uk


-----Original Message-----
From: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of fyson r.w. (rwf1v07)
Sent: 01 March 2016 12:55
To: eprints-tech at ecs.soton.ac.uk
Subject: Re: [EP-tech] Testing REF CC with new Dates plugin version 1.0.5

Hi Annette,

The update of REF CC to version 1.0.5 adds in the functionality of getting the 'Date of first online publication' from the 'Published Online' from the Dates plugin. This means it will look for a 'Date of first online publication' first from the old eprint's date field (which the 'Dates' plugin supersedes), then it will look for a 'Published Online' option from the 'Dates' field, and then it will look for a RIOXX date of publication, with each one in this list overriding the last for 'Date of first online publication'.

However, the update of Dates to version 1.0.5 ensures that whilst 'Published Online' is sent to REF CC, the 'Published' value is sent to RIOXX. Whilst this is what required from the two plugins, because REF CC ultimately gets its date from RIOXX if its available (as described above), it is the 'Published' version of the date that REFF CC ends up using.

Therefore Dates v1.0.5 has essentially be designed to work with a version of REF CC which has not yet been released. Therefore I've rolled back the DatesDatesDates plugin to version 1.0.4 for now and will update it again once a new version of REF CC version has been released.

I hope this clears things up a bit!

Many thanks,

Will


Richard William Fyson
rwf1v07 at ecs.soton.ac.uk
EPrints Services
Bay 2, 3081, B32
University of Southampton
________________________________________
From: eprints-tech-bounces at ecs.soton.ac.uk [eprints-tech-bounces at ecs.soton.ac.uk] on behalf of Annette Moore [a.moore at sussex.ac.uk]
Sent: 01 March 2016 12:20
To: eprints-tech at ecs.soton.ac.uk
Subject: [EP-tech] Testing REF CC with new Dates plugin version 1.0.5

We are currently testing the REF CC (version 1.0.5) and Dates plugin (version 1.0.5) on our test ePrints server however, it seems like REF CC is taking the Published  date type rather than the Published Online as the 'Date of first online publication'  - if both dates are present in the record.  It only seems to use the Published Online date if that is there is not Published date.  I am fairly new to ePrints so would welcome any comments on this.  Is there further configuration required so that REF CC uses the value in the date type 'Published Online' as a default?

We recently updated the REF CC plugin to version 1.0.5 but not sure exactly what changes to expect with this update.  Any pointers on this?

Best wishes,

Annette

Annette Moore
Technical Services Librarian

The Library
University of Sussex
Brighton
BN1 9QL

T:01273 877046
E:a.moore at sussex.ac.uk
*** 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/

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

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://lincoln.ac.uk/legal.

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