Re: About the AV and L1 fields

"Markus Hoenicka" <[email protected]> Fri, 6 Mar 2009 01:09:24 +0100
Newsgroups gmane.text.refdb.general
Message-ID <[email protected]>
Torsten Bronger writes:
 > 
 > But is L2 a personal or a global field?  According to the manual,
 > they "hold information which is stored for each user separately".
 > 
 > The RISX DTD has <link> tags in both the pubinfo (global) and the
 > libinfo (personal) elements.
 > 

The sources say that L1 through L4 elements from risx pubinfo elements
are imported without being attached to a particular user. In contrast,
L1 through L4 elements from libinfo elements are owned by the
corresponding user. When you retrieve risx data, you'll get back both
types, i.e. the "global" pubinfo links and the personal libinfo
links. A global paper copy cannot be defined at this time, except by
abusing L2.

 > This sounds neat, however, it would not help me because I need three
 > things: a global link to a file, a local link to a file, and a
 > real-world place of an offprint.  It is so complicated because some
 > collegues need personal copies of PDFs in order to write notes in
 > the PDF file.  (Weird.)
 > 

If I understand correctly, all this information could be stored using
risx. It is just that AV is not a global field per se, but if you
employ some mechanism to set this only once you'd get
close. Otherwise, as I've mentioned previously, you'd get the first
available AV entry which may or may not be useful.

 > Currently, I use the extension fields like this:
 > 
 > U1: globally set relevance, from "*" to "*****"
 > U2: global notes, in Markdown syntax
 > U3: relative path to the PDF on the central server
 > U4: locations of printed copies
 > M1: comma-separated list of Django group IDs to which this reference
 >     belongs

What are these group IDs used for? Is that similar to Unix groups?

 > M2: "1" for "institute publication", "0" for "not".
 > 

In general, it is not recommended to store user-defined information in
RIS M1 through M3 fields. RIS uses an arcane mechanism to map
information in these fields to reference type specific data (e.g. area
for maps, ostype for computer programs, doi for various types). You'll
lose information if you write your own stuff to these fields. If you
use global and personal links as intended, you'd free U3 and U4 for
the information you'd like to store in M1 and M2.

regards,
Markus

-- 
Markus Hoenicka
[email protected]
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H