Torsten Bronger | 1 May 2009 22:04
X-Face
Picon
Picon
Picon
Picon
Favicon
Gravatar

RISX vs. RIS

Hallöchen!

I'm now in the phase of choosing labels for the form field in my Web
front-end.  My plan is to use JavaScript to change the label names
according to the reference type.  For example, "publication title"
will be "journal name" for articles and "book title" for book
chapters.

The data model of my front-end is RISX.  Where can I get information
about how to interpret the RISX fields for the different types?
http://refdb.sourceforge.net/risx/index.html is of some help but it
is rather limited.  The most comprehensive tables can be found in
<http://www.referencemanager.com/support/docs/ReferenceManager11.pdf>,
pp 525 ff.  But this makes is necessary to map RISX to RIS.  Is
there information about this?

By the way, RIS seems to have four titles (primary, secondary,
series, periodical), whereas RISX has only three of them.  In case
of conferences, RIS uses all four (see page 527).  How is this
mapped to RISX?

Tschö,
Torsten.

--

-- 
Torsten Bronger, aquisgrana, europa vetus
                   Jabber ID: torsten.bronger <at> jabber.rwth-aachen.de

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
(Continue reading)

Torsten Bronger | 2 May 2009 20:16
X-Face
Picon
Picon
Picon
Picon
Favicon
Gravatar

Re: RISX vs. RIS

Hallöchen!

Torsten Bronger writes:

> [...]
>
> The data model of my front-end is RISX.  Where can I get
> information about how to interpret the RISX fields for the
> different types?  [...]  But this makes is necessary to map RISX
> to RIS.  Is there information about this?

I investigated further and now I'm slightly confused.  The RefDB
manual says that RISX should be prefered for communicating with the
database, and even that it should be used for backup dumps.
However, it can't hold all the data in the database.  For example,
if I store a book reference, there is a "volume" and an "edition"
field, however in RISX, only "volume" survives.  In other words, the
RISX dump is not lossless.  An RIS dump contains all fields, though.

Tschö,
Torsten.

--

-- 
Torsten Bronger, aquisgrana, europa vetus
                   Jabber ID: torsten.bronger <at> jabber.rwth-aachen.de

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
(Continue reading)

Markus Hoenicka | 4 May 2009 23:07
Picon

Re: Cannot add reference.

Wei-Wei Guo writes:
 > Do you mean patches for refdb-0.9.9-1.tar.gz? I can do that.
 > 

I've appended a simple patch for one of the source files to provide
additional debug output. Please apply the patch to the sources with a
command like:

patch < refdbdref.c.patch

from within the src subdirectory of the source tree. Then please
rebuild this directory and install it, or (whichever is easier for
you), run the server as a regular app from the src directory, like
this:

./refdbd -s [other options]

(kill it with Ctrl-c when done)

Then repeat your "add references" test from another xterm, and send
the refdbd log. Just ask if anything is unclear, I'll be happy to
help.

I've just tested this on a FreeBSD box using the current svn revision
and the sqlite3 driver. Things work ok for me.

regards,
Markus

(Continue reading)

Wei-Wei Guo | 5 May 2009 16:52
Picon

Re: Cannot add reference.

Markus Hoenicka 写道:
> Wei-Wei Guo writes:
>  > Do you mean patches for refdb-0.9.9-1.tar.gz? I can do that.
>  > 
> 
> I've appended a simple patch for one of the source files to provide
> additional debug output. Please apply the patch to the sources with a
> command like:
> 
> patch < refdbdref.c.patch
> 

The patch cannot be applied, so I open refdbdref.c and changed it by hand.

$ patch < refdbdref.c.patch
patching file refdbdref.c
Hunk #1 succeeded at 2114 (offset 1 line).
Hunk #2 FAILED at 2142.
1 out of 2 hunks FAILED -- saving rejects to file refdbdref.c.rej

> from within the src subdirectory of the source tree. Then please
> rebuild this directory and install it, or (whichever is easier for
> you), run the server as a regular app from the src directory, like
> this:
> 
> ./refdbd -s [other options]
> 

Cause I don't know how make install will affect the system consistence,
I just repack the refdb-0.9.9-1.tar.gz with the modified refdbdref.c and
(Continue reading)

Markus Hoenicka | 5 May 2009 22:31
Picon

Re: Cannot add reference.

Wei-Wei Guo writes:
 > Do you mean patches for refdb-0.9.9-1.tar.gz? I can do that.

Unfortunately I can't reply to the proper message as I didn't receive
your last reply in my inbox. I can see it in the list archives though.

I've checked your log output. I've designed another small patch to
drill a bit deeper. Please apply it in addition to the previous patch
and rebuild RefDB again. The procedure you used last time was
apparently successful.

BTW which type of processor do you use? Is it a non-x86, by any
chance?

regards,
Markus

Attachment (dbfncs.c.patch): application/octet-stream, 1220 bytes

--

-- 
Markus Hoenicka
markus.hoenicka <at> cats.de
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
(Continue reading)

Markus Hoenicka | 5 May 2009 22:47
Picon

RISX vs. RIS

Torsten Bronger writes:
 > The data model of my front-end is RISX.  Where can I get information
 > about how to interpret the RISX fields for the different types?
 > http://refdb.sourceforge.net/risx/index.html is of some help but it
 > is rather limited.  The most comprehensive tables can be found in
 > <http://www.referencemanager.com/support/docs/ReferenceManager11.pdf>,
 > pp 525 ff.  But this makes is necessary to map RISX to RIS.  Is
 > there information about this?
 > 

The mapping is not documented at this time except in the source
code. The tricky thing to understand is that RIS uses weird rules to
assign authors and titles to the A1-A3 and T1-T3 fields, whereas risx
attempts to use a much saner analytical=1, monographic=2, series=3
approach. The other risx elements map to RIS fields according to the
RefMan table in a fairly straightforward fashion.

I guess you're asking for an even larger table which shows the mapping
between real world items, RIS fields, and risx elements. I realize
that this information is helpful, but I won't be able to cough it up
in a matter of days.

 > By the way, RIS seems to have four titles (primary, secondary,
 > series, periodical), whereas RISX has only three of them.  In case
 > of conferences, RIS uses all four (see page 527).  How is this
 > mapped to RISX?
 > 

risx currently does not handle four titles, as I was not able to
figure out the difference between "series title" and "proceedings
(Continue reading)

Markus Hoenicka | 5 May 2009 22:49
Picon

Re: RISX vs. RIS

Torsten Bronger writes:
 > I investigated further and now I'm slightly confused.  The RefDB
 > manual says that RISX should be prefered for communicating with the
 > database, and even that it should be used for backup dumps.
 > However, it can't hold all the data in the database.  For example,
 > if I store a book reference, there is a "volume" and an "edition"
 > field, however in RISX, only "volume" survives.  In other words, the
 > RISX dump is not lossless.  An RIS dump contains all fields, though.
 > 

If a risx dump does not contain all data, the risx backend must be
considered broken. Could you please send some test data which help me
reproduce the problem?

thanks
Markus

--

-- 
Markus Hoenicka
markus.hoenicka <at> cats.de
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
(Continue reading)

Torsten Bronger | 6 May 2009 01:26
X-Face
Picon
Picon
Picon
Picon
Favicon
Gravatar

Re: RISX vs. RIS

Hallöchen!

Markus Hoenicka writes:

> [...]
>
> The mapping is not documented at this time except in the source
> code. The tricky thing to understand is that RIS uses weird rules
> to assign authors and titles to the A1-A3 and T1-T3 fields,
> whereas risx attempts to use a much saner analytical=1,
> monographic=2, series=3 approach. The other risx elements map to
> RIS fields according to the RefMan table in a fairly
> straightforward fashion.

I think I can cope with RISX' semantics quite well now.  I just want
to grey out some fields sometimes and rename them (e.g. "article
title" -- "journal title" for journal articles).  I think this helps
my collegues a lot because analytical vs. monographic must be learnt
by them first.  For this renaming, the tables in the RIS
specification were helpful.

What's missing is "edition" in RISX.  One can use the "otherinfo"
for the publishing date but this doesn't survive in BibTeX output.
If you use "edition" with RIS however, RefDB creates an "edition"
field for BibTeX.

Additionally, the explanation of "city" should be expanded to
"publication place" and not just the name of a town.  In case of
patents, for example, it's the name of a country.  (The tag name may
stay, however.)
(Continue reading)

Wei-Wei Guo | 6 May 2009 01:50
Picon

Re: Cannot add reference.

Markus Hoenicka 写道:
> I've checked your log output. I've designed another small patch to
> drill a bit deeper. Please apply it in addition to the previous patch
> and rebuild RefDB again. The procedure you used last time was
> apparently successful.
> 

I attached the newly produced refdbd.log with the same procedure.

> BTW which type of processor do you use? Is it a non-x86, by any
> chance?
> 

My processor is Intel Pentium 4.

Best wishes,
Wei-Wei
7:pid=2825:Tue May 05 22:56:16 2009:dbi_driver_dir went to:
7:pid=2825:Tue May 05 22:56:16 2009:
7:pid=2825:Tue May 05 22:56:16 2009:dbi is up using default driver dir
6:pid=2825:Tue May 05 22:56:16 2009:Available libdbi database drivers:
6:pid=2825:Tue May 05 22:56:16 2009:sqlite3
6:pid=2825:Tue May 05 22:56:16 2009:Requested libdbi driver found
6:pid=2825:Tue May 05 22:56:16 2009:Database directory:
6:pid=2825:Tue May 05 22:56:16 2009:/home/wwguo/studio/science/biblio
6:pid=2825:Tue May 05 22:56:16 2009:application server started
6:pid=2825:Tue May 05 22:56:16 2009:share extended notes by default
7:pid=2825:Tue May 05 22:56:16 2009:use /tmp/refdbd_fifo2825 as fifo
(Continue reading)

Markus Hoenicka | 6 May 2009 09:49
Picon

Re: Cannot add reference.

Quoting Wei-Wei Guo <wwguocn <at> gmail.com>:

> Markus Hoenicka 写道:
>> I've checked your log output. I've designed another small patch to
>> drill a bit deeper. Please apply it in addition to the previous patch
>> and rebuild RefDB again. The procedure you used last time was
>> apparently successful.
>>
>
> I attached the newly produced refdbd.log with the same procedure.

Thanks for repeating the test. Unfortunately I can't find the  
additional log output from the latest patch. There should be couple of  
lines starting with either "uint:" or "ulonglong:" providing  
additional clues. Could you please retry patching the sources with  
dbfncs.c.patch?

thanks
Markus

--

-- 
Markus Hoenicka
markus.hoenicka <at> cats.de
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
(Continue reading)


Gmane