On 7/27/2016 11:09 PM, Martina Gödel wrote:
> For each article (bookSection) we are creating a single
> biblStruct-element (<biblStruct type="bookSection">). While <analytic>
> stores the title information for the article, <monogr> stores the
> information for the superordinate book. If more than one article is part
> of the same book, the information in <monogr> will be doubled for each
> article (bookSection). We are looking for a way to avoid this redundant
> storage of information. The monographic level information should be
> maintained only in one place.
> How are other projects dealing with this? Are there any best practice
> solutions you could point us too?
I also maintain a large bibliography of several thousand entries using
<biblStruct>. But considering that the data is merely text files and
does not require any significant amount of memory, it does not concern
me at all that <monogr> information might be repeated elsewhere in the
document. After all, what is the most amount of articles that will be
contained in a volume? 15? 20?
Since my bibliography is quite active as a source for other projects, I
am regularly pulling individual <biblStruct> entries out and including
them in smaller bibliographies--in which case I certainly would like to
have the full <monogr> information intact, so I would not want to
abbreviate it in any way.
A. Charles Muller
Graduate School of Humanities and Sociology
Faculty of Letters
University of Tokyo
7-3-1 Hongō, Bunkyō-ku
Tokyo 113-8654, Japan
Office Phone: 03-5841-3735
Web Site: Resources for East Asian Language and Thought