EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #03395

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

[EP-tech] Re: Extracting authors

Another thought on this as I’ve been doing some digging. Part of my
external application theory is using the advanced search JSON output of
EPrints to bring search result information into my scripts (php) - the
Admin search provides a user search which we can use to get a JSON output
of all users, however this is not publicly accessible. Is there a way of
brining this into the public advanced search or perhaps being able to pass
some kind of authentication token in with my JSON call so that I can
scrape the user information from the advanced search?

On 15/08/2014 11:48, "Andrew Beeken" <anbeeken@lincoln.ac.uk> wrote:

>Okay, I think this is really going to be the correct approach however
>using straight up creators like that exposes too much. I¹m only interested
>in recording the details for our users, most likely user ID (for searching
>purposes) and their name (for easy identification). Pretty much what you
>get from http://eprints.lincoln.ac.uk/view/creators/ - would this be easy
>to expose on the OAI endpoint? Is there also an easy way to harvest from
>here?
>
>On 07/08/2014 09:25, "Ian Stuart" <Ian.Stuart@ed.ac.uk> wrote:
>
>>On 06/08/14 15:47, Andrew Beeken wrote:
>>> Hello all!
>>>
>>> I¹m currently looking at building applications that sit to the side
>>> of Eprints but tap into the data it stores. What I¹m hoping to be
>>> able to get, possibly via an OAI scrape, is a list of all of the
>>> authors stored in the system so that I can create a lookup table in
>>> my app ­ is this straightforward?
>>
>>As an OAI-PMH set, yes.... very easy
>>
>>$oai->{sets} = [
>>   ......
>>   { id=>"creators", allow_null=>0, fields=>"creators_name"},
>>   ......
>>];
>>
>>
>>As a cgi call, or in code, is slightly more complicated.
>>
>>My initial thought would be to create a script that goes through the
>>dataset and builds a "list of hashes": where the author details are
>>stored in a hash, and one of those key/value pairs is a list of
>>eprintids for the records they are listed as authors. Store this
>>data-object on disk, and your API can call that to do whatever
>>calculations you need.
>>
>>Depending on the size and activity of your Repository, you can build the
>>"list-of-hashes" hourly, daily, or whatever.
>>
>>--
>>
>>Ian Stuart.
>>Developer: ORI, RJ-Broker, and OpenDepot.org
>>Bibliographics and Multimedia Service Delivery team,
>>EDINA,
>>The University of Edinburgh.
>>
>>http://edina.ac.uk/
>>
>>This email was sent via the University of Edinburgh.
>>
>>The University of Edinburgh is a charitable body, registered in
>>Scotland, with registration number SC005336.
>>
>>
>>*** 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://www.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/