punkish / zenodeo

`nodejs` interface to Zenodo/BLR community
https://zenodeo.org
Creative Commons Zero v1.0 Universal
6 stars 1 forks source link

Full citation #19

Open gsautter opened 5 years ago

gsautter commented 5 years ago

Full citation

(4) Adding a full citation might be possible, yes. But I wouldn't like it as much to add that kind of redundancy to the XMLs proper. You can have it from the JSON, however, as the backing TB stats readily provide a full reference string, just need to add it to the request.

If you don't want to add the full citation in the XML then that is fine. I will try to reconstruct it from the various bits of the XML, but I will be embedding the logic in Zenodeo so it will be only available to those who use Zenodeo. The citation won't be available to those who download the XML (for whatever reason).

Note that I am not messing around with JSON and TB stats now. I have enough on my plate with extracting data from the XML and making the web app from it. Injecting another parallel data source into the process makes no sense.

Originally posted by @punkish in https://github.com/punkish/zenodeo/issues/14#issuecomment-515292087

gsautter commented 5 years ago

The idea was to use the stats to get a list of recently updated treatments, so you don't have to mess around with that large dump all the time ... something akin to http://tb.plazi.org/GgServer/static/newToday.html , which is also based on the stats engine. Maybe something like this: http://tb.plazi.org/GgServer/srsStats/stats?outputFields=doc.uuid+doc.articleUuid+doc.doi+doc.uploadDate+doc.updateDate+bibDsp.refDsp&groupingFields=doc.uuid+doc.articleUuid+doc.doi+doc.uploadDate+doc.updateDate+bibDsp.refDsp&FP-doc.uploadDate=%222019-07-20%22-&format=JSON the example is JSON, but you can also get it as XML if that's easier for your code to handle.