EPrints Technical Mailing List Archive
Message: #04765
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Re: cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- From: "Alan.Stiles" <alan.stiles@open.ac.uk>
- Date: Thu, 24 Sep 2015 11:05:04 +0000
At the risk of treading on Adam’s toes… If you try one of the exports on the search results page it gives you the detail you are after (plus a load of stuff you aren’t) e.g. the url below is for the JSON export of that search:
which includes the lines
[
{ "view_date": 2015, "eprintid": 2287468, "date": 2015, … So you could use one of the existing exporter URLs and take the information you want, or possibly write an exporter to just return
the eprintid in an appropriate format? (I believe there are some excellent videos on how to do that sort of thing on the eprints wiki…) Cheers, Alan From: eprints-tech-bounces@ecs.soton.ac.uk
[mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Andy Reid Thanks Adam, The situation is that our publications are initially imported to a local Publications database, which has an API to generate EPXML,
which is then pulled into eprints by a fiendish Harvester maintained by Rory over at ULCC, where the repository is hosted. The record structure in eprints includes a custom field - lshtm_pub_id - recording the recordID of the source record in the publications
database, but because the synchronisation is pulled from the eprints end, the DB never gets to find out what the resulting eprint ID is. In order to link through from the pubsDB to eprints, we have a link that searches on the lshtm_pub_id , e.g. http://www.lshtm.ac.uk/publications/list.php?filter=list&value=(26205126)
the link to ResearchOnline gives something like this (I've stripped out the PMID search elements below for clarity) - I'm not sure that all those parameters are necessary, but it works: What I'm after is just to use that search in a programmatic context, so that it just returns the matching eprint ID(s), rather than
the whole page. I'm sure it's simple when you know how, but the inline documentation of the cgi script is...
terse, to put it politely - Even a one line #Usage:.. example would probably make all the difference. Best Regards Andy >>> "Field A.N." <af05v@ecs.soton.ac.uk> 24 September
2015 10:53 >>>
|
- Follow-Ups:
- [EP-tech] Re: cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- From: "Field A.N." <af05v@ecs.soton.ac.uk>
- [EP-tech] Re: cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- References:
- [EP-tech] cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- From: "Andy Reid" <Andy.Reid@lshtm.ac.uk>
- [EP-tech] Re: cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- From: "Field A.N." <af05v@ecs.soton.ac.uk>
- [EP-tech] Re: cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- From: "Andy Reid" <Andy.Reid@lshtm.ac.uk>
- [EP-tech] cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- Prev by Date: [EP-tech] Re: cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- Next by Date: [EP-tech] Re: cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- Previous by thread: [EP-tech] Re: cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- Next by thread: [EP-tech] Re: cgi/search?myfield=foobar&action=export&format=xml (or whatever the syntax...)
- Index(es):