EPrints Technical Mailing List Archive

Message: #00750


< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: MePrints


A place to start looking is the "get_user_owned_eprints" method where you can define who owns an eprint. There is an example in the x_meprints.pl file which might be a good starting point. I seem to remember we sort of stopped supporting the IRStats plugin because it was too hard to install IRStats to test the widget :-P. We did have a few plugins for Seb's stats package. If you need help i dont mind get back to looking at the IRStats widget.

Patrick

On Mon, Jun 18, 2012 at 1:51 PM, Centro de Documentación <cendocu@gmail.com> wrote:
Hi Seb,

Thank you for your reply and assistance,

Cheers,

Cristian

On Fri, Jun 15, 2012 at 12:50 PM, Sebastien Francois
<sf2@ecs.soton.ac.uk> wrote:
>
>
> On 15/06/12 16:42, Centro de Documentación wrote:
>> Hi guys,
>>
>> Can someone help me with this request. I sent it, some time ago.
>>
>> ---------- Forwarded message ----------
>> Date: Thu, May 31, 2012 at 11:00 AM
>>
>> Hello,
>>
>> I have a repository running both MePrints (1.4.2) and IRStats (1.0.3).
>> However, if I include the IRStats widget in MePrints, it doesn't show
>> anything. The widget screen is empty. I'm sure that some of the items
>> were downloaded.
>>
> I believe this may work if you have set up "userid" as as set in IRStats.
>
>> Other questions about MePrints:
>>
>> Is it possible to match user_id with creators_id/editors_id to create
>> a meprints profile?
> No, MePrints is there specifically for the "user" dataset.
>
>> Something like user_id ->  creators_id/editors_id ->  view top ten items
>> / view downloads
>
>> I mean, what happens with coauthors papers or delegated
>> archive/mediated deposit? (one eprints user, multiple creators)
>> In many cases, users/depositers are very different from creators?
> The context in which MePrints was written is different than that of a
> standard publication repository so there was no consideration on
> co-authoring.
>
> You might be able to change this however by looking through the source
> code. Sorry I can't help you more on that one.
>
> Seb.
>
>
>