I have a library with references of another book (a primary source) and analyzed on which pages (and hence how often) its sources were cited. I would like to print this data in a table.
Is it possible to use biblatex/biber to process additional fields (in this case citedonpages) to fill an additional column (and even count the comma separated entries)?
In the following MWE, I created the table manually. As the real library has many entries, an automated solution would be very helpful (in the example it would even detect multiple entries of the same pages - this would be nice but not necessary).
MWE:
\documentclass{scrbook}
\usepackage{tabularx,booktabs}
\usepackage[backend=biber,style=authortitle]{biblatex}
\begin{filecontents*}{Analysis.bib}
@Book{Miller1832a,
author = {John Miller},
title = {Elementary book},
year = {1832},
citedonpages = {67,67,68,97},
}
@InBook{Smith1744a,
author = {Daniel Smith},
booktitle = {Collection of important articles},
location = {Amsterdam},
title = {Noteworthy Article},
year = {1744},
citedonpages = {5, 23, 37, 79, 248, 249, 254},
}
\end{filecontents*}
%\addbibresource{Analysis.bib}
\begin{document}
\begin{refsection}[Analysis.bib]
\nocite{*}
\printbibliography[heading=none]
% is it possible to autogenerate this table using Analysis.bib and biber/biblatex?
\begin{tabularx}{0.95 \textwidth}{llccX}
\toprule
{\bfseries Author} & {\bfseries Title} & {\bfseries Year} & {\bfseries # Citations} & ... on pages \\midrule%\otoprule
Miller, John & Elementary book & 1832 & 4 & 67(2), 68, 97\
Smith, Daniel & Noteworthy articls & 1744 & 7 & 5, 23, 37, 79, 248, 249, 254 \
\bottomrule
\end{tabularx}
\end{refsection}
\end{document}
PS. useful source so far: \refsection{} environment from \nocite{*} for single bibdatasources with biblatex/biber


datatype=xsvsepis not a valid declaration which makes Biber choke quite badly.format=xsv,would be valid, but allformat=xsvfields also have a specialdatatype, which would not be applicable here, so I'd stick withdatatype=literal,. That keeps things easy and since we (probably) need to do post-processing on the LaTeX side anyway, it doesn't hurt not to let Biber do any pre-processing. – moewe Aug 01 '21 at 16:23