EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #08350
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Eprints-tech Digest, Vol 145, Issue 14
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] Eprints-tech Digest, Vol 145, Issue 14
- From: Michael Eadie <Michael.Eadie@glasgow.ac.uk>
- Date: Thu, 22 Oct 2020 07:43:56 +0000
CAUTION: This email originated from outside of the University of Southampton. Do not click links or open attachments unless you recognise the sender and know the content is safe.
Hi Lindsay Thanks for this that’s really useful – I had a look at that UKCorr thread from the archive and the consensus seems to be to count gold as in-scope. I also can’t find anything gin the guidance that says gold should be out of scope. I wonder if the refcc plugin should have its compliant / outofscope tests updated? So add the check for hoa_gold into the sub for ‘run_test_Compliant’ to show gold as compliant, and remove that check from ‘OUT_OF_SCOPE_reason’ Not sure if that’s the most efficient way or this would have knock on effects elsewhere. Or indeed if others are convinced this should be done!
Regards Mick From: eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk>
On Behalf Of Lindsay Wood via Eprints-tech CAUTION:
This email originated from outside of the University of Southampton. Do not click links or open attachments unless you recognise the sender and know the content is safe. Hi Mick, Just quickly, I recognise this conundrum, it came up briefly on UKCoRR not so long ago. REF guidance I am sure used phrase 'Out Of Scope'/not in scope for Gold at one point, but when I looked for it, it had changed. If you exclude Gold
you could swing percentages alot for a bioscience UoA, which is helped by having access to that funding stream. I think the ISSN logic may be an optional flag? I'm calculating like the latter and using additional external logic/cross referencing. I think the
plugin needs a refresh against current policy and validation (which is changing nationally). REF CC and REF Support plugin don't always seem to match. The exports need to match current policy specification, also it exports compliance for output REF types other
than C & D (journal article & conference contributions). Different repositories seem to be on varying versions, bug fixes and customisations. Best, Linds On Wed, 21 Oct 2020 at 12:00, <eprints-tech-request@ecs.soton.ac.uk> wrote:
-- Mr Lindsay Wood e-Repositories Manager, University of Warwick |
- Follow-Ups:
- Re: [EP-tech] Eprints-tech Digest, Vol 145, Issue 14
- From: Michael Eadie <Michael.Eadie@glasgow.ac.uk>
- Re: [EP-tech] Eprints-tech Digest, Vol 145, Issue 14
- References:
- Re: [EP-tech] Eprints-tech Digest, Vol 145, Issue 14
- From: Lindsay Wood <lindsaywood.work@googlemail.com>
- Re: [EP-tech] Eprints-tech Digest, Vol 145, Issue 14
- From: Michael Eadie <Michael.Eadie@glasgow.ac.uk>
- Re: [EP-tech] Eprints-tech Digest, Vol 145, Issue 14
- Prev by Date: Re: [EP-tech] Eprints-tech Digest, Vol 145, Issue 14
- Next by Date: [EP-tech] New Gold Support Issue : IRStats
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):