EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #06940
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] RIOXX2 question
- To: "'eprints-tech@ecs.soton.ac.uk'" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] RIOXX2 question
- From: Andy Reid <Andy.REID@lshtm.ac.uk>
- Date: Tue, 7 Nov 2017 16:59:25 +0000
That sounds a lot trickier, because if it’s a document field, you could in principle have more than one document, so how will the code know which one to reference. I realise you may have a workflow that only
ever creates one document per eprint, but eprints doesn’t know that. At the simplest you might have an accepted manuscript and a Version of record attached to the same eprint. I suppose if the data structure for ‘stage’ had a numeric value or ordering attached,
you could walk through all the documents in the eprint, and return the stage with the maximum value, where e.g. Published > Accepted, which would sort of make sense in the context of RIOXX. Andy From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Andrew Beeken Figured this out and got the mapping working with our license data now! Thanks! I am having a problem with the mapping on version now, however – it looks like it wants to derive this from a value called “content”, however I want to derive this from a document field called “stage”. I’ve tried reconfiguring the function
to work in the same way as the license function, however this is throwing an error. Any thoughts on this? From:
eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Andrew Beeken Ah, so it’s passing our local value through a filter to make it compliant with RIOXX? That sounds like something that could come back to bite us if we’re just storing our local value. I’ll take a look into that further… From:
eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Andy Reid I think RIOXX has a controlled vocabulary for licenses, and ‘license_map’ is a lookup table to convert your local license captions into ones that RIOXX recognises. I guess you could extend the lookup table to
cover whatever values you are using. This is just from memory of looking at the RIOXX code a few weeks ago – feel free to shoot me down. Andy From:
eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Andrew Beeken Hey all, Currently configuring the RIOXX2 plugin and I hit an issue with the code that derives the license from the record. I’ve resolved it but I wanted to check to see if there was any problem with the way that I resolved it, as I’m not 100% sure
what the original code was trying to do. The problem seemed to come from these lines: my $license = $document->repository->config( "rioxx2", "license_map", $document->value( "license" ) ); return { undef } unless $license; Which was always returning undef. I tweaked it to: my $license = $document->value( "license" ); return { undef } unless $license; Which returns the actual license and gives me an entry in RIOXX, however – is the $document->repository->config… part of the original line doing something specific that the corrected version is not that could cause me problems further down
the line? Cheers! Andrew
|
- References:
- [EP-tech] RIOXX2 question
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- Re: [EP-tech] RIOXX2 question
- From: Andy Reid <Andy.REID@lshtm.ac.uk>
- Re: [EP-tech] RIOXX2 question
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- Re: [EP-tech] RIOXX2 question
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- [EP-tech] RIOXX2 question
- Prev by Date: Re: [EP-tech] How to submit on eprints bazaar
- Next by Date: [EP-tech] login redirection not working
- Previous by thread: Re: [EP-tech] RIOXX2 question
- Next by thread: [EP-tech] How to submit on eprints bazaar
- Index(es):