On 27 September 2011 23:17, funky dev <[email protected]> wrote: > Hi, > > I've been looking at the jabref code a little with the intention to make the > following modifications: > > - Implement Inpsire support (as opposed to spires). > - Include more fields from Inspire such as abstract and number of citations > by switching to an XML format for the data (right now spires returns bibtex > embedded in some HTML). > - Maybe track citations as well. > > Previously I used Spires.app and would like to try to mimic all its > functionality in jabref. > > So I have a few questions in this direction. First, is someone already > working on adding inspire support? Second, does anyone have any resource > regarding inspire's support of MARCXML or OAI2 or any other standard? The > Inspire website seems very light on API documentation. Finally, is there a > resource to help one get started with the code base?
I'm not aware of anyone else working on Inspire support. If you mean getting started with the JabRef code base, there's unfortunately not that much to find, but I'd be happy to help out if you have questions. > I've got a working hack to add inspire support to JabRef (as an additional > plugin rather than a modification of the spires one). I basically just > re-used the spires code and pointed it at inspire...very little modification > was needed as both spires and inspire outputs bibtex embedded in an html > file. > There was some functionality I could not test because I'm not sure if its > been disabled in JabRef. In particular there seems to be an openSpires > action that I didn't bother to port over because I'm not sure it works for > spires in the current version (it seems to be disabled). It would be nice > to hear from someone who knows this code to see if these functions are still > supported. If I remember correctly, the openSpires action was for either completing an entry based on Spires data, or for opening a Spires link, and the action didn't quite fit into the JabRef interface, so it was disabled. If the action can be integrated in a way that makes sense, I don't think there's any problem with it otherwise. > But the bigger issue is that I'd like to access inspire via MARCXML or > endref or some other XML format that returns additional fields like the > abstract because I'd like to store them as well. This is a bit more > involved and I'm not sure what the most efficient way to do it is. JabRef > does not seem to have a Filter for any relevant inspire output format > besides bibtex and endref. While the later contains the abstract it doesn't > include the eprint number which is a worse omission. > As spires looks like its about to go the way of the dinosaurs I'd be happy > to provide this inspire patch to the main tree or to anyone who just wants > to patch their own version. You may have to make a new filter for it - there are a couple of XML filters already (e.g. Medline) that might be useful as a starting point. If you have a plugin that's ready to use, we can publish it on the JabRef web page. If the code belongs in the main tree, we should consider adding it - if you want to, you could send me a patch to have a look at. Morten ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Jabref-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jabref-users
