inspire
inspire copied to clipboard
inspirehep
BibFormat: add techreport as bibtex entry
This recognizes 980__a:techreport and sets entry_type accordingly. Currently INSPIRE doesn't have any records marked as techreports, so this is just for code completeness.
Signed-off-by: Thorsten Schwander [email protected]
I am not sure that's the way to go, as in the schema possible document types have been standardized here and here.
I think we should rather decide whether 980__a:report == @techreport, and adapt the bibtex format accordingly. I don't have strong opinions on this, nor did anyone on standup apparently.
fine with me if it ever comes to that, by it didn't sound like "report" was considered equivalent to "techreport". so this patch simply ensures that the code is clear about where in the code/when/how a techreport entry_type would be selected without actually changing anything for existing data.
as it is, nowhere in the code would entry_type techreport be assigned and so the conditional switches on techreport are somewhat misleading
Currently, the large majority of our Reports are TDRs. But we also have records like
Status Report of the DPHEP Collaboration: A Global Effort for Sustainable Data Preservation in High Energy Physicshttps://inspirehep.net/record/1408514 DPHEPhttps://inspirehep.net/search?p=collaboration:%27DPHEP%27&ln=en Collaboration (Silvia Ameriohttps://inspirehep.net/author/profile/Amerio%2C%20Silvia?recid=1408514&ln=en (INFN, Paduahttps://inspirehep.net/search?cc=Institutions&p=institution:%22INFN%2C%20Padua%22&ln=en) et al.https://inspirehep.net/record/1408514). Feb 17, 2015. 60 pp. DPHEP-2015-001 DOI: 10.5281/zenodo.46158http://dx.doi.org/10.5281/zenodo.46158 e-Print: arXiv:1512.02019http://arxiv.org/abs/arXiv:1512.02019 [hep-ex] | PDFhttp://arxiv.org/pdf/1512.02019.pdf
Handbook of LHC Higgs Cross Sections: 3. Higgs Propertieshttps://inspirehep.net/record/1241571 LHC Higgs Cross Section Working Grouphttps://inspirehep.net/search?p=collaboration:%27LHC%20Higgs%20Cross%20Section%20Working%20Group%27&ln=en (S Heinemeyerhttps://inspirehep.net/author/profile/Heinemeyer%2C%20S?recid=1241571&ln=en (ed.) (Cantabria Inst. of Phys.https://inspirehep.net/search?cc=Institutions&p=institution:%22Cantabria%20Inst.%20of%20Phys.%22&ln=en) et al.https://inspirehep.net/record/1241571). Jul 4, 2013. 404 pp. CERN-2013-004, FERMILAB-CONF-13-667-T DOI: 10.5170/CERN-2013-004http://dx.doi.org/10.5170/CERN-2013-004 e-Print: arXiv:1307.1347http://arxiv.org/abs/arXiv:1307.1347 [hep-ph] | PDFhttp://arxiv.org/pdf/1307.1347.pdf
Simon van der Meer and his legacy to CERN and particle acceleratorshttps://inspirehep.net/record/1207977 Vinod Chohanhttps://inspirehep.net/author/profile/Chohan%2C%20Vinod?recid=1207977&ln=en (CERNhttps://inspirehep.net/search?cc=Institutions&p=institution:%22CERN%22&ln=en). Dec 2012. 26 pp. CERN-2012-008 DOI: 10.5170/CERN-2012-008http://dx.doi.org/10.5170/CERN-2012-008 e-Print: arXiv:1212.4320http://arxiv.org/abs/arXiv:1212.4320 [physics.hist-ph] | PDFhttp://arxiv.org/pdf/1212.4320.pdf
Particle Physics 2011: Highlights and annual reporthttps://inspirehep.net/record/1123958 Manfred Fleischerhttps://inspirehep.net/author/profile/Fleischer%2C%20Manfred?recid=1123958&ln=en (ed.), Matthias Kasemannhttps://inspirehep.net/author/profile/Kasemann%2C%20Matthias?recid=1123958&ln=en (ed.) (DESYhttps://inspirehep.net/search?cc=Institutions&p=institution:%22DESY%22&ln=en). Jun 2012. 134 pp.
Since we have introduced Reports not so long ago and it was comparatively easy to tag TDRs whereas other reports are more difficult to tag. So the current ratio is not really representative. But we could of course go for a more restrictive definition of Reports if we hfind consensus for this.
- Annette
On 25 Jan 2017, at 18:17, Micha Moskovic <[email protected]mailto:[email protected]> wrote:
I am not sure that's the way to go, as in the schema possible document types have been standardized herehttps://github.com/inspirehep/inspire-schemas/blob/master/inspire_schemas/records/hep.json#L323 and herehttps://github.com/inspirehep/inspire-schemas/blob/master/inspire_schemas/records/hep.json#L683. I think we should rather decide whether 980__a:report == @techreport, and adapt the bibtex format accordingly. I don't have strong opinions on this, nor did anyone on standup apparently.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/inspirehep/inspire/pull/266#issuecomment-275171001, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AM1-O5xj9Xc3LJUfBWMqBfkRc_3ipTXQks5rV4OlgaJpZM4LtvEL.
