Chapter 5. Constructing the "raw" Bibliography
Prev     Next

Chapter 5. Constructing the "raw" Bibliography

RefDB-lite requires an input source of biblioentry data in "raw" DocBook format. The organisation of DocBook bibliographies is incredibly flexible so in fact it is necessary to restrict the potential formats to a consistent though legal DocBook subset. Otherwise the source document would not validate. The raw bibliography format itself is a tentative proposal and open for negotiation. It should capture most of the potential of RISX (Hoenicka, 2005d) and ultimately, perhaps MODS (Library of Congress, 2004).

Each biblioentry must have an id attribute corresponding to the basename of a citation biblioref element. 

  <biblioentry role='JOUR' id='FoxCoef'>                   1
    <abbrev>FoxCoef</abbrev>

    <biblioset relation='JOUR'>                            2
      <titleabbrev role='SECONDARY'>Acta Cryst.</titleabbrev> 3
    </biblioset>

    <biblioset relation='SERIES' role='TERTIARY'>          4
      <titleabbrev role='TERTIARY'>A</titleabbrev>
    </biblioset>
    <bibliomisc role='USERDEF1'>A</bibliomisc>               5

    <biblioset relation='ARTICLE'>                         6
      <authorgroup role='PRIMARY'>                         7
        <author>
          <firstname>A</firstname>
          <othername role='mi'>G</othername>
          <surname>Fox</surname>
        </author>
        <author>
          <firstname>M</firstname>
          <othername role='mi'>A</othername>
          <surname>O'Keefe</surname>
        </author>
        <author>
          <firstname>M</firstname>
          <othername role='mi'>A</othername>
          <surname>Tabbernor</surname>
        </author>
      </authorgroup>
      <title role='PRIMARY'>Relativistic Hartree-Fock X-ray and electron atomic scattering factors
at high angles</title>
      <volumenum>45</volumenum>
      <pubdate role='PRIMARY'>1989</pubdate>           8
      <pagenums role='start'>786</pagenums>            9
      <pagenums role='end'>793</pagenums>
      <bibliosource class="uri">
        <ulink url='http://www.iucr.org/paper?hh0289'/>      10
      </bibliosource>
    </biblioset>

  </biblioentry>
1

The role must correspond to one of the RIS reference TY (type) entries: "ABST", "ADVS", "ART", "BILL", "BOOK", "CASE", "CHAP", "COMP", "CONF", "CTLG", "DATA", "ELEC", "GEN", "HEAR", "ICOMM", "INPR", "JFULL", "JOUR", "MAP", "MGZN", "MPCT", "MUSIC", "NEWS", "PAMP", "PAT", "PCOMM", "RPRT", "SER", "SLIDE", "SOUND", "STAT", "THES", "UNBILL", "UNPB" or "VIDEO"

2

The relation attribute should be something consistent to identify the class of data, in this instance a JOURnal title.

3

The titleabbrev is used to specify journal titles and should probably conform to the abbreviation styles of Chemical Abstracts(??). It should be uniformly preformatted as J.Irrep.Results. Use "." with no space to identify an abbreviated word or a space to indicate a complete word.

4

The SERIES titleabbrev does not exist in RIS, so it is obsolete here because there is no way to specify how to use it in the CITESTYLE file when it is needed.

5

Instead the SERIES titleabbrev is stashed here and accessed as USERDEF1 in PUBTYPE styles.

6

This contains reference specific details, rather than general info.

7

Article authors are PRIMARY authors. Book editors are SECONDARY authors. Series editors are TERTIARY editors.

8

What is a SECONDARY date? Submitted, accepted?

9

Split on role just to be pedantic.

10

A ulink element could be obtained from a RefDB bibliographic database, but an olink could exist in a documents static internal bibliography.

If the "raw" data exists in an external database, then the internal document bibliography could be comprised of "empty" biblioentry tags, one to match each citation basename used within the document. However, this is not strictly necessary, and is probably superfluous. 

<bibliography> <title>Bibliography</title>
 <biblioentry id="Smith00"/>
 <biblioentry id="Walsh99"/>
 <biblioentry id="Stayton05"/>
</bibliography>

In this case the associated "raw" data must be accessible through the bibliography.collection variable or the RefDB CGI (web) interface.

Prev     Next
Chapter 4. XSLT Document Processing  Home  Chapter 6. Possible Customisations