I have a large bibliography generated by a reference manager program (Citavi, but it can be anything else). The urldate field of all references is formatted as urldate = {dd.mm.yyyy}, which is not correct for biblatex. However, I don't want to change this field every time I update my HUGE bibliography from the reference manager app.
In fact, I receive no errors but many warnings like one below.
Package biblatex Warning: Biber reported the following issues
(biblatex) with 'XYZ.2003':
(biblatex) - Datamodel: Entry 'XYZ.2003' (bibliographie.bib)
: Invalid format '18.11.2013' of date field 'urldate' - ignoring.
I don't want to have these warning, since for many bibliography entries this type of warning will dominate and it will be hard to see the relevant warnings.
I.e. these warnings need to be somehow suppressed
For comleteness (partially using the example Find unused bibkeys using biblatex),
\begin{filecontents*}{bibliograp.bib}
@BOOK{Ab_Steg,
author = "M. Abramowitz and I. A. Stegun",
title = {Handbook of mathematical functions},
publisher = "Dover publications",
year = "1965",
urldate = {15.10.2013},
language="English" }
\end{filecontents*}
\documentclass[11pt,onecolumn,twoside]{scrbook}
\usepackage[style=numeric-comp,
backend=biber,
date=short,
firstinits=true,
language=english]{biblatex}
\AtEveryBibitem{\clearlist{urldate}}
\AtEveryBibitem{\clearlist{abstract}}
\addbibresource[datatype=bibtex]{bibliograp.bib}
\begin{document}
hello world \cite{Ab_Steg}
\printbibliography
\end{document}
As it can be seen, \AtEveryBibitem{\clearlist{urldate}} doesn't prevent the warnings. I also expected that language=german (i.e. go away from the English date standard) in biblatex options could resolve the issue, but it also doesn't help.
AtEveryBibitem, I have found\AtEveryCitekeygood to know about, e.g. to suppress the issue from the cite and getAuthor (date)rather than the less desirableAuthor (date, issue), you would do\AtEveryCitekey{\clearfield{issue}}. – PatrickT Jul 09 '18 at 19:33\AtEveryBibitemor\AtEveryCitekey. Note thatissueis rarely the field you want, normally you are looking fornumber. It is a quirk ofbiblatex-apathat it shows theissuein the citation label, but apparently that is what the APA dictates. – moewe Jul 09 '18 at 20:30numberand an issueseason, e.g. Volume 1, Number 3, Fall 2018. I usually omit season, but if I do include it, the cite comes out asAuthor (2018, Spring).(I'll have to drop apa soon) I am usingissueto store the season because of these remarks in the manual ''This field [issue] is intended for journals whose individual issues are identified by a designation such as ‘Spring’ or ‘Summer’ rather than the month or a number.'' Also, see: https://tex.stackexchange.com/questions/396421/best-way-to-encode-season-spring-summer-fall-winter-in-bibtex – PatrickT Jul 10 '18 at 06:18issueis OK. You could think about usingdatewith2018-23instead, but I'm not sure whatbiblatex-apamakes of that. – moewe Jul 10 '18 at 06:36apa!! – PatrickT Jul 10 '18 at 13:20