[Refdb-devel] [ refdb-Bugs-2945806 ] RISX of a conference entry should use "periodical name"

[SourceForge.net <no...@so...>]

Bugs item #2945806, was opened at 2010-02-04 09:48
Message generated for change (Comment added) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=2945806&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Torsten Bronger (bronger)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: RISX of a conference entry should use "periodical name"

Initial Comment:
Currently the T2 field is used as publication title in RISX exports of CONF entries.  According to Refman specs, this is the conference name, however, the proceedings title seems to be more appropriate which is in the JO/JF field.

----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-02-11 01:30

Message:
I've changed the risx DTD to include a conftitle element. I've also changed
the refdbd sources to properly import and export this element.

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-02-10 00:50

Message:
Your analysis is correct. I've checked in a patch for backend.c which lets
the risx backend export the conference proceedings title rather than the
conference title. As you correctly point out, the conference title is lost
in the output at the moment. I think the proper way to fix this is to add a
"conftitle" element to the pubinfo element in the risx DTD.

----------------------------------------------------------------------

Comment By: Torsten Bronger (bronger)
Date: 2010-02-05 08:45

Message:
Unfortunately, it is even more complicated than in my first post.

Conferences have four titles: Article title, proceedings title, conference
name, and series title.  However, RISX has only three levels.  The question
is how to fill the title field in the second level, i.e. the publication
title.  Note that CONF is the only citation type with four titles, which is
probably the reason why this hasn't been a big deal so far.

Currently, RefDB takes the conference name for the pubtitle, i.e. the T2
field of the RIS dataset.  This is not bad, but: Any JO/JF field is not
exported to RISX, although it would contain the proceedings title, which is
certainly important, too.

I don't know exactly how to solve this.  A possible remedy can be to
export whatever is filled in JF/T2, with JF having higher priority, and to
document that RISX can't export both the conference name and the
proceedings title at the same time.  This is very compatible with current's
bahaviour and should do what people expect in almost any case.

You asked for an example.  The following RIS dataset:

TY  - CONF
ID  - Bronger2010
AU  - Bronger,T.
TI  - My Article's Title
JO  - Sup.Conf.Proc.
RP  - NOT IN FILE
T2  - Super Conference
PY  - 2010///
ER  - 

is exported to RISX as:

<ris>
  <entry type="CONF" id="4" citekey="Bronger2010">
    <part>
      <title type="full">My Article's Title</title>
      <author role="author">
        <lastname>Bronger</lastname>
        <firstname>T</firstname>
      </author>
    </part>
    <publication>
      <title type="full">Super Conference</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>2010</year></date>
        </pubdate>
      </pubinfo>
    </publication>
    <libinfo user="refdb">
      <reprint status="NOTINFILE"/>
    </libinfo>
  </entry>
</ris>

Thus, the proceedings title is lost.


----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-02-05 00:54

Message:
I seem to be a bit dense here. Could you please provide an example RIS
input file, along with the current risx output and the risx output that
you'd prefer? I'll be happy to look into this.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=2945806&group_id=26091