refdb-devel Mailing List for RefDB (Page 17)
Status: Beta
Brought to you by:
mhoenicka
Menu
▾
▴
refdb-devel — List for RefDB developers
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(14) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2003 |
Jan
|
Feb
(1) |
Mar
(5) |
Apr
(6) |
May
(6) |
Jun
(4) |
Jul
(11) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
(174) |
| 2004 |
Jan
(10) |
Feb
(2) |
Mar
|
Apr
|
May
(2) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
(2) |
Feb
(6) |
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(25) |
Oct
(18) |
Nov
(16) |
Dec
(19) |
| 2006 |
Jan
(6) |
Feb
|
Mar
|
Apr
(21) |
May
(9) |
Jun
(5) |
Jul
(51) |
Aug
(89) |
Sep
(42) |
Oct
(19) |
Nov
(47) |
Dec
(4) |
| 2007 |
Jan
(8) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(4) |
Aug
(4) |
Sep
(5) |
Oct
|
Nov
(7) |
Dec
(4) |
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
(14) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2009 |
Jan
|
Feb
(21) |
Mar
(8) |
Apr
(5) |
May
(6) |
Jun
(2) |
Jul
(5) |
Aug
|
Sep
(3) |
Oct
(14) |
Nov
|
Dec
|
| 2010 |
Jan
(18) |
Feb
(5) |
Mar
|
Apr
|
May
(4) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
|
Dec
|
|
From: Markus H. <mar...@mh...> - 2006-07-07 07:01:00
|
David Nebauer <dav...@sw...> was heard to say: > This would be a *very* nice feature to have. For what it's worth, > however, forcing the use of a single database per document would simply > bring LaTeX support in line with DocBook document support. > I didn't try lately, but the reverse might be true. Once upon a time the DocBook/TEI code also allowed using more than one database. I'll check. regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
|
From: David N. <dav...@sw...> - 2006-07-07 00:02:34
|
Hi Markus, > Upon checking the code I noticed that I had to disable support for > using more than one database for some reason. > I'll have to figure out something how I can make this work again. This would be a *very* nice feature to have. For what it's worth, however, forcing the use of a single database per document would simply bring LaTeX support in line with DocBook document support. Regards, David. |
|
From: David N. <dav...@sw...> - 2006-07-06 23:58:18
|
Hi Markus, > I'll set up a test case and see what happens. I recall it might be > necessary to specify a default database anyway (i.e. use the -d switch > of runbib) even if you specify a database in each citation. Does the > problem persist if you set a default database? Yes. I tried it with and without specifying a default database for 'runbib'. Regards, David. |
|
From: David N. <dav...@sw...> - 2006-07-06 23:55:35
|
Hi Markus, > > For those installing from source I think you need to include Term::Clui in perlmod. > > I prefer to guide the users to CPAN if the module is officially available. Fair enough. I'm always thinking of the newbie who knows nothing about Perl, CPAN, etc. -- but they've got to learn sometime... Regards, David. |
|
From: Markus H. <mar...@mh...> - 2006-07-06 22:42:45
|
Markus Hoenicka writes: > I'll set up a test case and see what happens. I recall it might be > necessary to specify a default database anyway (i.e. use the -d switch > of runbib) even if you specify a database in each citation. Does the > problem persist if you set a default database? > Upon checking the code I noticed that I had to disable support for using more than one database for some reason. It seems to be related to the fact that I wanted to use the citation key as reference without an ID prefix or something. However, this way I can't safely separate a database part from the citation key proper. I'll have to figure out something how I can make this work again. regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
|
From: Markus H. <mar...@mh...> - 2006-07-06 21:59:35
|
David Nebauer writes:
> When I specify no database in the document -- with all references from
> one database -- and specify that database as a runbib parameter, there
> is no problem. If, however, I use the second method of specifying
> '\cite{<database>-<reference>}' the process fails.
>
I'll set up a test case and see what happens. I recall it might be
necessary to specify a default database anyway (i.e. use the -d switch
of runbib) even if you specify a database in each citation. Does the
problem persist if you set a default database?
regards,
Markus
--
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de
|
|
From: Markus H. <mar...@mh...> - 2006-07-06 21:59:32
|
Hi David, David Nebauer writes: > For those installing from source I think you need to include Term::Clui > in perlmod. You can find a tarzip in > <http://refdb.sourceforge.net/sources>. > I prefer to guide the users to CPAN if the module is officially available. This way I don't need to keep track of newer versions, and I also avoid users trying to install an outdated version shipped with RefDB over a newer one already on their systems. I've added Term::Clui to the configure tests and improved the warning a little. The warning about missing Perl modules is now conditional, i.e. it will only be displayed if at least one of the modules is missing, and it clearly says so in this case. I hope this is sufficient to make the users aware of this issue. regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
|
From: Markus H. <mar...@mh...> - 2006-07-06 21:09:01
|
Hi David, David Nebauer writes: > Ah, I see why I couldn't find it in perlmod. The link on > 'download.html' claims to point to 'RefDB-perlmod-0.4.tar.gz' but > actually downloads 'RefDB-perlmod-0.3.tar.gz'. Version 0.3 does not > contain 'RefDB::Makestyle'. > My bad. I've fixed that link, and removed the comment about the Perlmod package being optional. No one should miss refdb-ms. regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
|
From: David N. <dav...@sw...> - 2006-07-06 17:58:14
|
Hi Markus, The Perl library RefDB::Makestyle has a dependency on another Perl library Term::Clui. Term::Clui isn't available as an official distribution so I've hand rolled an autotools distro and Debian package. I've added it as a package to the Debian refdb repositories. For those installing from source I think you need to include Term::Clui in perlmod. You can find a tarzip in <http://refdb.sourceforge.net/sources>. Regards, David. |
|
From: David N. <dav...@sw...> - 2006-07-06 13:25:55
|
Hi Markus,
> Rather than force Debian users to source the 'addons' repository to
> access package 'libperl-refdb-makestyle' I'll move the package into
> the refdb repositories ('release' and 'svn').
Since package 'libperl-refdb-makestyle' depends on a hand-rolled package
of mine 'libperl-term-clui' I've also had to include the latter in both
refdb repositories.
Regards,
David.
|
|
From: Markus H. <mar...@mh...> - 2006-07-06 12:08:41
|
David Nebauer <dav...@sw...> was heard to say: > Hi Markus, > > The utility script 'refdb-ms' which you have included in refdb source is > dependent on Perl library 'RefDB::Makestyle'. > > This library is not included with RefDB. The only way a user would > realise they need another Perl library is if they: > > 1. Tried to run refdb-ms and got an error message, > 2. Read the refdb-ms manpage, or > 3. Read the addons.html page and noted the dependency. > > I seem to recall raising this issue with you before but can't remember > what decision, if any, we reached. Is there any way to include > RefDB::Makestyle in the refdb source? All Perl modules that are required to run the Perl scripts shipped with RefDB are supplied as the Perlmod package. The reason is simply that the Perl idea about packaging and installing modules does not go well with an autotools-based project. However, I've included checks into configure which warn the user if one of the required modules is missing. Needless to say, after integrating refdb-ms into the sources I forgot to add an appropriate check for RefDB::Makestyle to configure.in. I'll fix this asap. There should probably also be a warning at the end of configure if some modules were missing. regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
|
From: <ste...@jo...> - 2006-06-30 10:21:48
|
Markus Hoenicka a =E9crit : > St=E9phane T=E9letch=E9a writes: > > According to Mandriva's policy (and following FHS + LSB), see below = the=20 > > list of files (it is long but please have a look at them to check if= i=20 > > have not missed one). >=20 > I couldn't see any obvious omissions from your list. I believe > everything is there. Yep, there was a duplication (www being packaged in=20 /usr/share/refdb-0.9.7/www and in /var/www/refdb/), and i fixed some=20 permissions. BTW, i think you should not have 755 permissions for AUTHORS, ChangeLog,=20 COPYING, INSTALL, NEWS, READM files. They should be 644 like the file=20 UPGRADING for instance. > > 3 - be able to use correctly the web interface (actually i can use i= t=20 > > but my attemps to insert a reference failed) >=20 > It was just reported on this list that editing references does not > work either. I'm afraid the PHP web interface is not yet working as it > should. It is at your discretion whether you want to package a broken > interface or drop it for the time being. Yes, this is also my conclusion, the phpweb is useless as it is. I=20 haven't been able to use it, even if the db was created correctly and=20 refdbc worked ... > > 4 - patch the marc2ris.pl since a new release is done (or you'll do = a=20 > > 0.9.7.1 ?) >=20 > I'd suggest to patch it until the next release is available. I don't > want to publish another release because of a 4-line fix in one of the > scripts. patch done. > > If anyone is willing to test the rpm, let me know, i think i'll go=20 > > through these steps and release the rpm file into Mandriva's mirror=20 > > (thus, it'll become an official package of the distribution, availab= le=20 > > for all). > >=20 >=20 > How are the chances to turn your Mandriva RPMs into packages for the > other major RPM-based distros (Fedora, SuSE)? Is there anyone on the > list using one of these distos who could lend St=E9phane a hand? I don't have such setup on my computer (or at least not yet ;-). Things can be a little different on those systems since the dependency=20 tree is somewhat different and naming conventions may differ. Other than=20 this the rpm should be installable (i need to removed some Mandriva=20 specific macros in case of a general rpm). That would require little work, but since i'm gaining experience in rpm=20 building, i think i'll be able to obtain it after having polished the=20 Mandriva rpm ;-) > regards, > Markus So far i've tested only refdb + pgsql and importing from examples, i'll=20 try to test other combinations. Cheers, St=E9phane --=20 St=E9phane T=E9letch=E9a, PhD. http://www.steletch.org Unit=E9 Math=E9matique Informatique et G=E9nome http://migale.jouy.inra.f= r/mig INRA, Domaine de Vilvert T=E9l : (33) 134 652 891 78352 Jouy-en-Josas cedex, France Fax : (33) 134 652 901 |
|
From: Markus H. <mar...@mh...> - 2006-06-29 20:39:37
|
St=E9phane T=E9letch=E9a writes: > According to Mandriva's policy (and following FHS + LSB), see below = the=20 > list of files (it is long but please have a look at them to check if= i=20 > have not missed one). I couldn't see any obvious omissions from your list. I believe everything is there. > 3 - be able to use correctly the web interface (actually i can use i= t=20 > but my attemps to insert a reference failed) It was just reported on this list that editing references does not work either. I'm afraid the PHP web interface is not yet working as it should. It is at your discretion whether you want to package a broken interface or drop it for the time being. > 4 - patch the marc2ris.pl since a new release is done (or you'll do = a=20 > 0.9.7.1 =3F) I'd suggest to patch it until the next release is available. I don't want to publish another release because of a 4-line fix in one of the scripts. > If anyone is willing to test the rpm, let me know, i think i'll go=20= > through these steps and release the rpm file into Mandriva's mirror=20= > (thus, it'll become an official package of the distribution, availab= le=20 > for all). >=20 How are the chances to turn your Mandriva RPMs into packages for the other major RPM-based distros (Fedora, SuSE)=3F Is there anyone on the list using one of these distos who could lend St=E9phane a hand=3F regards, Markus --=20 Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
|
From: <ste...@jo...> - 2006-06-29 10:33:07
|
I'm on the verge of releasing the rpm ;-) This mail is for information and some rfc. The rpm i have created produces two rpms: refdb : the server refdb-clients : refdbc, refdba, refbib According to Mandriva's policy (and following FHS + LSB), see below the=20 list of files (it is long but please have a look at them to check if i=20 have not missed one). The server is packaged as : /etc/refdb/ default configuration files /usr/bin/ binaries /usr/share/man man pages /usr/share/refdb data for refdb /usr/share/doc/refdb-0.9.7/ documentation /var/lib/refdb/db db directory for embedded database engine /var/www/refdb/ web interface (admin + client) /etc/httpd/conf/webapps.d/refdb.conf /etc/php.d/A53_refdb.ini those two are for the phpweb interface What is on my todo list ? 1 - checking everything works (already done for the server and basic=20 configuration files) 2 - provide an initscript FHS compliant (the configuration is different=20 on BSD/debian and Mandriva/RH/Suse) 3 - be able to use correctly the web interface (actually i can use it=20 but my attemps to insert a reference failed) 4 - patch the marc2ris.pl since a new release is done (or you'll do a=20 0.9.7.1 ?) 5 - try various database engine (so far, postgresql and mysql). 6 - take comments and incorporate them (if any) If anyone is willing to test the rpm, let me know, i think i'll go=20 through these steps and release the rpm file into Mandriva's mirror=20 (thus, it'll become an official package of the distribution, available=20 for all). I'm open to suggestions, comments :-) St=E9phane /etc/httpd/conf/webapps.d/refdb.conf /etc/php.d/A53_refdb.ini /etc/refdb/bib2riscgirc.example /etc/refdb/bib2risrc.example /etc/refdb/db2risrc.example /etc/refdb/marc2risrc.example /etc/refdb/med2riscgirc.example /etc/refdb/med2risrc.example /etc/refdb/refdbarc.example /etc/refdb/refdbcgirc.example /etc/refdb/refdbcrc.example /etc/refdb/refdbdrc.mysql.example /etc/refdb/refdbdrc.pgsql.example /etc/refdb/refdbdrc.sqlite.example /etc/refdb/refdbdrc.sqlite3.example /etc/refdb/refdbibrc.example /etc/refdb/refdbxmlrc.example /usr/bin/bib2ris /usr/bin/db2ris /usr/bin/eenc /usr/bin/en2ris /usr/bin/marc2ris /usr/bin/med2ris /usr/bin/refdb-backup /usr/bin/refdb-bug /usr/bin/refdb-init-pgsql.sh /usr/bin/refdb-init.sh /usr/bin/refdb-ms /usr/bin/refdb-restore /usr/bin/refdb_dos2unix /usr/bin/refdb_tex2mail /usr/bin/refdbctl /usr/bin/refdbd /usr/bin/refdbjade /usr/bin/refdbnd /usr/bin/refdbxml /usr/bin/refdbxp /usr/bin/runbib /usr/lib/debug /usr/lib/debug/usr /usr/lib/debug/usr/bin /usr/lib/debug/usr/bin/bib2ris.debug /usr/lib/debug/usr/bin/eenc.debug /usr/lib/debug/usr/bin/refdba.debug /usr/lib/debug/usr/bin/refdbc.debug /usr/lib/debug/usr/bin/refdbd.debug /usr/lib/debug/usr/bin/refdbib.debug /usr/lib/debug/usr/bin/refdbxp.debug /usr/share/doc/refdb-0.9.7 /usr/share/doc/refdb-0.9.7/AUTHORS /usr/share/doc/refdb-0.9.7/COPYING /usr/share/doc/refdb-0.9.7/ChangeLog /usr/share/doc/refdb-0.9.7/INSTALL /usr/share/doc/refdb-0.9.7/NEWS /usr/share/doc/refdb-0.9.7/README /usr/share/doc/refdb-0.9.7/README.urpmi /usr/share/doc/refdb-0.9.7/UPGRADING /usr/share/doc/refdb-0.9.7/citationlistx /usr/share/doc/refdb-0.9.7/citationlistx/dtdelem /usr/share/doc/refdb-0.9.7/citationlistx/dtdelem.html /usr/share/doc/refdb-0.9.7/citationlistx/dtdelem/citation.html /usr/share/doc/refdb-0.9.7/citationlistx/dtdelem/citationlist.html /usr/share/doc/refdb-0.9.7/citationlistx/dtdelem/xref.html /usr/share/doc/refdb-0.9.7/citationlistx/dtdent /usr/share/doc/refdb-0.9.7/citationlistx/dtdent.html /usr/share/doc/refdb-0.9.7/citationlistx/ele-desc /usr/share/doc/refdb-0.9.7/citationlistx/ele-desc/citation.html /usr/share/doc/refdb-0.9.7/citationlistx/ele-desc/citationlist.html /usr/share/doc/refdb-0.9.7/citationlistx/ele-desc/xref.html /usr/share/doc/refdb-0.9.7/citationlistx/elements /usr/share/doc/refdb-0.9.7/citationlistx/elements.html /usr/share/doc/refdb-0.9.7/citationlistx/elements/citation.html /usr/share/doc/refdb-0.9.7/citationlistx/elements/citationlist.html /usr/share/doc/refdb-0.9.7/citationlistx/elements/xref.html /usr/share/doc/refdb-0.9.7/citationlistx/entities /usr/share/doc/refdb-0.9.7/citationlistx/entities.html /usr/share/doc/refdb-0.9.7/citationlistx/index.html /usr/share/doc/refdb-0.9.7/citationlistx/notations /usr/share/doc/refdb-0.9.7/citationlistx/notations.html /usr/share/doc/refdb-0.9.7/citestylex /usr/share/doc/refdb-0.9.7/citestylex/dtdelem /usr/share/doc/refdb-0.9.7/citestylex/dtdelem.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/abbreviatefirst.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/abbreviatesubseq.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/abstract.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/address.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/aempty.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/apr.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/asame.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/aug.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/authorlist.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/authornames.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/authoronly.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/authorseps.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/bibliotitle.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/bibstyle.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/citestyle.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/citseparator.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/citstyle.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/dec.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/feb.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/firstsep.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/following.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/intextdef.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/issue.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/jan.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/journalname.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/jul.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/jun.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/link.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/mar.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/may.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/misc.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/months.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/namefirst.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/nameother.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/notes.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/nov.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/oct.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/pagerange.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/pages.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/preceeding.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/publisher.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/pubplace.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/pubtype.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/rangeseparator.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/refnumber.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/refstyle.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/secondsep.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/sep.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/separator.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/serial.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/singlepage.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/stylename.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/styleset.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/text.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/textmultiple.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/textsingle.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/threeseps.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/threesepseach.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/threesepslast.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/title.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/twoseps.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/userdef.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/volume.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/pubdate.html /usr/share/doc/refdb-0.9.7/citestylex/dtdelem/yearonly.html /usr/share/doc/refdb-0.9.7/citestylex/dtdent /usr/share/doc/refdb-0.9.7/citestylex/dtdent.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/abbreviatefirst.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/abbreviatesubseq.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/abstract.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/address.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/aempty.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/apr.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/asame.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/aug.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/authorlist.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/authornames.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/authoronly.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/authorseps.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/bibliotitle.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/bibstyle.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/citestyle.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/citseparator.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/citstyle.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/dec.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/feb.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/firstsep.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/following.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/intextdef.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/issue.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/jan.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/journalname.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/jul.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/jun.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/link.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/mar.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/may.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/misc.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/months.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/namefirst.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/nameother.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/notes.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/nov.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/oct.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/pagerange.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/pages.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/preceeding.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/pubdate.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/publisher.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/pubplace.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/pubtype.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/rangeseparator.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/refnumber.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/refstyle.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/secondsep.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/sep.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/separator.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/serial.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/singlepage.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/stylename.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/styleset.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/text.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/textmultiple.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/textsingle.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/threeseps.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/threesepseach.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/threesepslast.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/title.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/twoseps.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/userdef.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/volume.html /usr/share/doc/refdb-0.9.7/citestylex/ele-desc/yearonly.html /usr/share/doc/refdb-0.9.7/citestylex/elements /usr/share/doc/refdb-0.9.7/citestylex/elements.html /usr/share/doc/refdb-0.9.7/citestylex/elements/abbreviatefirst.html /usr/share/doc/refdb-0.9.7/citestylex/elements/abbreviatesubseq.html /usr/share/doc/refdb-0.9.7/citestylex/elements/abstract.html /usr/share/doc/refdb-0.9.7/citestylex/elements/address.html /usr/share/doc/refdb-0.9.7/citestylex/elements/aempty.html /usr/share/doc/refdb-0.9.7/citestylex/elements/apr.html /usr/share/doc/refdb-0.9.7/citestylex/elements/asame.html /usr/share/doc/refdb-0.9.7/citestylex/elements/aug.html /usr/share/doc/refdb-0.9.7/citestylex/elements/authorlist.html /usr/share/doc/refdb-0.9.7/citestylex/elements/authornames.html /usr/share/doc/refdb-0.9.7/citestylex/elements/authoronly.html /usr/share/doc/refdb-0.9.7/citestylex/elements/authorseps.html /usr/share/doc/refdb-0.9.7/citestylex/elements/bibliotitle.html /usr/share/doc/refdb-0.9.7/citestylex/elements/bibstyle.html /usr/share/doc/refdb-0.9.7/citestylex/elements/citestyle.html /usr/share/doc/refdb-0.9.7/citestylex/elements/citseparator.html /usr/share/doc/refdb-0.9.7/citestylex/elements/citstyle.html /usr/share/doc/refdb-0.9.7/citestylex/elements/dec.html /usr/share/doc/refdb-0.9.7/citestylex/elements/feb.html /usr/share/doc/refdb-0.9.7/citestylex/elements/firstsep.html /usr/share/doc/refdb-0.9.7/citestylex/elements/following.html /usr/share/doc/refdb-0.9.7/citestylex/elements/intextdef.html /usr/share/doc/refdb-0.9.7/citestylex/elements/issue.html /usr/share/doc/refdb-0.9.7/citestylex/elements/jan.html /usr/share/doc/refdb-0.9.7/citestylex/elements/journalname.html /usr/share/doc/refdb-0.9.7/citestylex/elements/jul.html /usr/share/doc/refdb-0.9.7/citestylex/elements/jun.html /usr/share/doc/refdb-0.9.7/citestylex/elements/link.html /usr/share/doc/refdb-0.9.7/citestylex/elements/mar.html /usr/share/doc/refdb-0.9.7/citestylex/elements/may.html /usr/share/doc/refdb-0.9.7/citestylex/elements/misc.html /usr/share/doc/refdb-0.9.7/citestylex/elements/months.html /usr/share/doc/refdb-0.9.7/citestylex/elements/namefirst.html /usr/share/doc/refdb-0.9.7/citestylex/elements/nameother.html /usr/share/doc/refdb-0.9.7/citestylex/elements/notes.html /usr/share/doc/refdb-0.9.7/citestylex/elements/nov.html /usr/share/doc/refdb-0.9.7/citestylex/elements/oct.html /usr/share/doc/refdb-0.9.7/citestylex/elements/pagerange.html /usr/share/doc/refdb-0.9.7/citestylex/elements/pages.html /usr/share/doc/refdb-0.9.7/citestylex/elements/preceeding.html /usr/share/doc/refdb-0.9.7/citestylex/elements/pubdate.html /usr/share/doc/refdb-0.9.7/citestylex/elements/publisher.html /usr/share/doc/refdb-0.9.7/citestylex/elements/pubplace.html /usr/share/doc/refdb-0.9.7/citestylex/elements/pubtype.html /usr/share/doc/refdb-0.9.7/citestylex/elements/rangeseparator.html /usr/share/doc/refdb-0.9.7/citestylex/elements/refnumber.html /usr/share/doc/refdb-0.9.7/citestylex/elements/refstyle.html /usr/share/doc/refdb-0.9.7/citestylex/elements/secondsep.html /usr/share/doc/refdb-0.9.7/citestylex/elements/sep.html /usr/share/doc/refdb-0.9.7/citestylex/elements/separator.html /usr/share/doc/refdb-0.9.7/citestylex/elements/serial.html /usr/share/doc/refdb-0.9.7/citestylex/elements/singlepage.html /usr/share/doc/refdb-0.9.7/citestylex/elements/stylename.html /usr/share/doc/refdb-0.9.7/citestylex/elements/styleset.html /usr/share/doc/refdb-0.9.7/citestylex/elements/text.html /usr/share/doc/refdb-0.9.7/citestylex/elements/textmultiple.html /usr/share/doc/refdb-0.9.7/citestylex/elements/textsingle.html /usr/share/doc/refdb-0.9.7/citestylex/elements/threeseps.html /usr/share/doc/refdb-0.9.7/citestylex/elements/threesepseach.html /usr/share/doc/refdb-0.9.7/citestylex/elements/threesepslast.html /usr/share/doc/refdb-0.9.7/citestylex/elements/title.html /usr/share/doc/refdb-0.9.7/citestylex/elements/twoseps.html /usr/share/doc/refdb-0.9.7/citestylex/elements/userdef.html /usr/share/doc/refdb-0.9.7/citestylex/elements/volume.html /usr/share/doc/refdb-0.9.7/citestylex/elements/yearonly.html /usr/share/doc/refdb-0.9.7/citestylex/entities /usr/share/doc/refdb-0.9.7/citestylex/entities.html /usr/share/doc/refdb-0.9.7/citestylex/index.html /usr/share/doc/refdb-0.9.7/citestylex/notations /usr/share/doc/refdb-0.9.7/citestylex/notations.html /usr/share/doc/refdb-0.9.7/index.html /usr/share/doc/refdb-0.9.7/manual.css /usr/share/doc/refdb-0.9.7/refdb-manual /usr/share/doc/refdb-0.9.7/refdb-manual.pdf /usr/share/doc/refdb-0.9.7/refdb-manual/ch01.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch01s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch01s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch01s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch01s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch01s06.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch02s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch02s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch02s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch02s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch03s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch04s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch04s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch04s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch04s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch04s06.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch04s07.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch04s08.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch04s09.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch05s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch05s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch05s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch05s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch05s06.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch05s07.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch05s08.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch05s09.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch06.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch06s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch06s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch06s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch06s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch07.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch07s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch07s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch07s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch07s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch07s06.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08s06.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08s07.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08s08.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08s09.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08s10.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch08s11.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch09.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch09s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch09s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch09s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch09s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch09s06.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch10.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch10s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch10s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch11.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch12.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch13.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch13s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch13s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch13s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch13s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch14.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch15.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch15s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch15s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch15s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch15s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch15s06.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch15s07.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch15s08.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch15s09.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch16.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch16s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch16s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch16s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch16s05.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch17.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch17s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch18.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch18s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch19.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch19s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch20.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch20s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch20s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch20s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch21.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch21s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch21s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/ch21s04.html /usr/share/doc/refdb-0.9.7/refdb-manual/co01.html /usr/share/doc/refdb-0.9.7/refdb-manual/index.html /usr/share/doc/refdb-0.9.7/refdb-manual/manual.css /usr/share/doc/refdb-0.9.7/refdb-manual/pr01.html /usr/share/doc/refdb-0.9.7/refdb-manual/pr01s02.html /usr/share/doc/refdb-0.9.7/refdb-manual/pr01s03.html /usr/share/doc/refdb-0.9.7/refdb-manual/pt01.html /usr/share/doc/refdb-0.9.7/refdb-manual/pt02.html /usr/share/doc/refdb-0.9.7/refdb-manual/pt03.html /usr/share/doc/refdb-0.9.7/refdb-manual/pt04.html /usr/share/doc/refdb-0.9.7/refdb-manual/pt05.html /usr/share/doc/refdb-0.9.7/refdb-manual/re01.html /usr/share/doc/refdb-0.9.7/refdb-manual/re02.html /usr/share/doc/refdb-0.9.7/refdb-manual/re03.html /usr/share/doc/refdb-0.9.7/refdb-manual/re04.html /usr/share/doc/refdb-0.9.7/refdb-manual/re05.html /usr/share/doc/refdb-0.9.7/refdb-manual/re06.html /usr/share/doc/refdb-0.9.7/refdb-manual/re07.html /usr/share/doc/refdb-0.9.7/refdb-manual/re08.html /usr/share/doc/refdb-0.9.7/refdb-manual/re09.html /usr/share/doc/refdb-0.9.7/refdb-manual/re10.html /usr/share/doc/refdb-0.9.7/refdb-manual/re11.html /usr/share/doc/refdb-0.9.7/refdb-manual/re12.html /usr/share/doc/refdb-0.9.7/refdb-manual/re13.html /usr/share/doc/refdb-0.9.7/refdb-manual/re14.html /usr/share/doc/refdb-0.9.7/refdb-manual/re15.html /usr/share/doc/refdb-0.9.7/refdb-manual/re16.html /usr/share/doc/refdb-0.9.7/refdb-manual/re17.html /usr/share/doc/refdb-0.9.7/refdb-manual/re18.html /usr/share/doc/refdb-0.9.7/refdb-manual/re19.html /usr/share/doc/refdb-0.9.7/refdb-manual/re20.html /usr/share/doc/refdb-0.9.7/refdb-manual/re21.html /usr/share/doc/refdb-0.9.7/refdb-manual/re22.html /usr/share/doc/refdb-0.9.7/refdb-manual/refdbmanualfig1.png /usr/share/doc/refdb-0.9.7/refdb-manual/refdbmanualfig2.png /usr/share/doc/refdb-0.9.7/refdb-manual/refdbmanualfig3.png /usr/share/doc/refdb-0.9.7/refdb-manual/refdbmanualfig4.png /usr/share/doc/refdb-0.9.7/risx /usr/share/doc/refdb-0.9.7/risx/dtdelem /usr/share/doc/refdb-0.9.7/risx/dtdelem.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/abstract.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/address.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/author.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/availability.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/city.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/contents.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/date.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/day.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/endpage.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/entry.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/firstname.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/issue.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/keyword.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/lastname.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/libinfo.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/link.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/middlename.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/misc.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/month.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/name.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/notes.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/otherinfo.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/part.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/pubdate.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/pubinfo.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/publication.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/publisher.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/reprint.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/ris.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/serial.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/set.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/startpage.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/suffix.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/title.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/userdef.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/volume.html /usr/share/doc/refdb-0.9.7/risx/dtdelem/year.html /usr/share/doc/refdb-0.9.7/risx/dtdent /usr/share/doc/refdb-0.9.7/risx/dtdent.html /usr/share/doc/refdb-0.9.7/risx/ele-desc /usr/share/doc/refdb-0.9.7/risx/ele-desc/abstract.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/address.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/author.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/availability.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/city.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/contents.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/date.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/day.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/endpage.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/entry.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/firstname.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/issue.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/keyword.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/lastname.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/libinfo.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/middlename.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/misc.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/month.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/name.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/notes.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/otherinfo.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/part.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/pubdate.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/pubinfo.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/publication.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/publisher.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/reprint.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/ris.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/serial.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/set.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/startpage.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/suffix.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/title.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/url.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/userdef.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/volume.html /usr/share/doc/refdb-0.9.7/risx/ele-desc/year.html /usr/share/doc/refdb-0.9.7/risx/elements /usr/share/doc/refdb-0.9.7/risx/elements.html /usr/share/doc/refdb-0.9.7/risx/elements/abstract.html /usr/share/doc/refdb-0.9.7/risx/elements/address.html /usr/share/doc/refdb-0.9.7/risx/elements/author.html /usr/share/doc/refdb-0.9.7/risx/elements/availability.html /usr/share/doc/refdb-0.9.7/risx/elements/city.html /usr/share/doc/refdb-0.9.7/risx/elements/contents.html /usr/share/doc/refdb-0.9.7/risx/elements/date.html /usr/share/doc/refdb-0.9.7/risx/elements/day.html /usr/share/doc/refdb-0.9.7/risx/elements/endpage.html /usr/share/doc/refdb-0.9.7/risx/elements/entry.html /usr/share/doc/refdb-0.9.7/risx/elements/firstname.html /usr/share/doc/refdb-0.9.7/risx/elements/issue.html /usr/share/doc/refdb-0.9.7/risx/elements/keyword.html /usr/share/doc/refdb-0.9.7/risx/elements/lastname.html /usr/share/doc/refdb-0.9.7/risx/elements/libinfo.html /usr/share/doc/refdb-0.9.7/risx/elements/link.html /usr/share/doc/refdb-0.9.7/risx/elements/middlename.html /usr/share/doc/refdb-0.9.7/risx/elements/misc.html /usr/share/doc/refdb-0.9.7/risx/elements/month.html /usr/share/doc/refdb-0.9.7/risx/elements/name.html /usr/share/doc/refdb-0.9.7/risx/elements/notes.html /usr/share/doc/refdb-0.9.7/risx/elements/otherinfo.html /usr/share/doc/refdb-0.9.7/risx/elements/part.html /usr/share/doc/refdb-0.9.7/risx/elements/pubdate.html /usr/share/doc/refdb-0.9.7/risx/elements/pubinfo.html /usr/share/doc/refdb-0.9.7/risx/elements/publication.html /usr/share/doc/refdb-0.9.7/risx/elements/publisher.html /usr/share/doc/refdb-0.9.7/risx/elements/reprint.html /usr/share/doc/refdb-0.9.7/risx/elements/ris.html /usr/share/doc/refdb-0.9.7/risx/elements/serial.html /usr/share/doc/refdb-0.9.7/risx/elements/set.html /usr/share/doc/refdb-0.9.7/risx/elements/startpage.html /usr/share/doc/refdb-0.9.7/risx/elements/suffix.html /usr/share/doc/refdb-0.9.7/risx/elements/title.html /usr/share/doc/refdb-0.9.7/risx/elements/url.html /usr/share/doc/refdb-0.9.7/risx/elements/userdef.html /usr/share/doc/refdb-0.9.7/risx/elements/volume.html /usr/share/doc/refdb-0.9.7/risx/elements/year.html /usr/share/doc/refdb-0.9.7/risx/entities /usr/share/doc/refdb-0.9.7/risx/entities.html /usr/share/doc/refdb-0.9.7/risx/index.html /usr/share/doc/refdb-0.9.7/risx/notations /usr/share/doc/refdb-0.9.7/risx/notations.html /usr/share/doc/refdb-0.9.7/xnote /usr/share/doc/refdb-0.9.7/xnote/dtdelem /usr/share/doc/refdb-0.9.7/xnote/dtdelem.html /usr/share/doc/refdb-0.9.7/xnote/dtdelem/content.html /usr/share/doc/refdb-0.9.7/xnote/dtdelem/keyword.html /usr/share/doc/refdb-0.9.7/xnote/dtdelem/link.html /usr/share/doc/refdb-0.9.7/xnote/dtdelem/title.html /usr/share/doc/refdb-0.9.7/xnote/dtdelem/ulink.html /usr/share/doc/refdb-0.9.7/xnote/dtdelem/xnote.html /usr/share/doc/refdb-0.9.7/xnote/dtdelem/xnoteset.html /usr/share/doc/refdb-0.9.7/xnote/dtdent /usr/share/doc/refdb-0.9.7/xnote/dtdent.html /usr/share/doc/refdb-0.9.7/xnote/ele-desc /usr/share/doc/refdb-0.9.7/xnote/ele-desc/content.html /usr/share/doc/refdb-0.9.7/xnote/ele-desc/keyword.html /usr/share/doc/refdb-0.9.7/xnote/ele-desc/link.html /usr/share/doc/refdb-0.9.7/xnote/ele-desc/title.html /usr/share/doc/refdb-0.9.7/xnote/ele-desc/ulink.html /usr/share/doc/refdb-0.9.7/xnote/ele-desc/xnote.html /usr/share/doc/refdb-0.9.7/xnote/ele-desc/xnoteset.html /usr/share/doc/refdb-0.9.7/xnote/elements /usr/share/doc/refdb-0.9.7/xnote/elements.html /usr/share/doc/refdb-0.9.7/xnote/elements/content.html /usr/share/doc/refdb-0.9.7/xnote/elements/keyword.html /usr/share/doc/refdb-0.9.7/xnote/elements/link.html /usr/share/doc/refdb-0.9.7/xnote/elements/title.html /usr/share/doc/refdb-0.9.7/xnote/elements/ulink.html /usr/share/doc/refdb-0.9.7/xnote/elements/xnote.html /usr/share/doc/refdb-0.9.7/xnote/elements/xnoteset.html /usr/share/doc/refdb-0.9.7/xnote/entities /usr/share/doc/refdb-0.9.7/xnote/entities.html /usr/share/doc/refdb-0.9.7/xnote/index.html /usr/share/doc/refdb-0.9.7/xnote/notations /usr/share/doc/refdb-0.9.7/xnote/notations.html /usr/share/man/man1/bib2ris.1.bz2 /usr/share/man/man1/db2ris.1.bz2 /usr/share/man/man1/eenc.1.bz2 /usr/share/man/man1/en2ris.1.bz2 /usr/share/man/man1/marc2ris.1.bz2 /usr/share/man/man1/med2ris.1.bz2 /usr/share/man/man1/refdb-backup.1.bz2 /usr/share/man/man1/refdb-init.sh.1.bz2 /usr/share/man/man1/refdb-ms.1.bz2 /usr/share/man/man1/refdb-restore.1.bz2 /usr/share/man/man1/refdb.sh.1.bz2 /usr/share/man/man1/refdba.1.bz2 /usr/share/man/man1/refdbc.1.bz2 /usr/share/man/man1/refdbctl.1.bz2 /usr/share/man/man1/refdbd.1.bz2 /usr/share/man/man1/refdbib.1.bz2 /usr/share/man/man1/refdbjade.1.bz2 /usr/share/man/man1/refdbnd.1.bz2 /usr/share/man/man1/refdbxml.1.bz2 /usr/share/man/man1/refdbxp.1.bz2 /usr/share/man/man1/runbib.1.bz2 /usr/share/man/man7/RefDB.7.bz2 /usr/share/man/man8/refdb.8.bz2 /usr/share/refdb /usr/share/refdb/css /usr/share/refdb/css/refdb.css /usr/share/refdb/db /usr/share/refdb/declarations /usr/share/refdb/declarations/docbook.dcl /usr/share/refdb/declarations/xml.dcl /usr/share/refdb/dsssl /usr/share/refdb/dsssl/bibdb2tei.dsl /usr/share/refdb/dsssl/catalog /usr/share/refdb/dsssl/citations.dsl /usr/share/refdb/dsssl/db2ris.dsl /usr/share/refdb/dsssl/html /usr/share/refdb/dsssl/html/docbook-refdb.dsl /usr/share/refdb/dsssl/lib /usr/share/refdb/dsssl/lib/refdblib.dsl /usr/share/refdb/dsssl/lib/refdbvar.dsl /usr/share/refdb/dsssl/makecss.dsl /usr/share/refdb/dsssl/print /usr/share/refdb/dsssl/print/docbook-refdb.dsl /usr/share/refdb/dtd /usr/share/refdb/dtd/catalog /usr/share/refdb/dtd/citationlistx.dtd /usr/share/refdb/dtd/citationlistx.rnc /usr/share/refdb/dtd/citationlistx.rng /usr/share/refdb/dtd/citestylex.dtd /usr/share/refdb/dtd/citestylex.rnc /usr/share/refdb/dtd/citestylex.rng /usr/share/refdb/dtd/risx.dtd /usr/share/refdb/dtd/risx.rnc /usr/share/refdb/dtd/risx.rng /usr/share/refdb/dtd/xnote.dtd /usr/share/refdb/dtd/xnote.rnc /usr/share/refdb/dtd/xnote.rng /usr/share/refdb/examples /usr/share/refdb/examples/Makefile.template /usr/share/refdb/examples/dbtest.sgml /usr/share/refdb/examples/dbtest.short.sgml /usr/share/refdb/examples/dbxtest.short.xml /usr/share/refdb/examples/dbxtest.xml /usr/share/refdb/examples/readme.examples /usr/share/refdb/examples/serif.bib /usr/share/refdb/examples/teitest.short.xml /usr/share/refdb/examples/teitest.xml /usr/share/refdb/examples/testrefs.ris /usr/share/refdb/examples/testrefs.usmarc /usr/share/refdb/examples/testrefs.xml /usr/share/refdb/examples/xnoteset.xml /usr/share/refdb/refdb.cat /usr/share/refdb/sql /usr/share/refdb/sql/empty.mysql.dump /usr/share/refdb/sql/empty.pgsql.dump.in /usr/share/refdb/sql/refdb-upgrade.sql /usr/share/refdb/sql/refdb.dump.mysql /usr/share/refdb/sql/refdb.dump.mysql41 /usr/share/refdb/sql/refdb.dump.pgsql /usr/share/refdb/sql/refdb.dump.sqlite /usr/share/refdb/styles /usr/share/refdb/styles/Eur.J.Pharmacol.xml /usr/share/refdb/styles/J.Biol.Chem.xml /usr/share/refdb/styles/bibtex-abbrev.xml /usr/share/refdb/styles/bibtex-full.xml /usr/share/refdb/styles/schemas.xml /usr/share/refdb/www /usr/share/refdb/www/admin.php /usr/share/refdb/www/include.php /usr/share/refdb/www/index.html /usr/share/refdb/www/login.php /usr/share/refdb/www/refdb-prl-del.php /usr/share/refdb/www/refdbadd.html /usr/share/refdb/www/refdbadd.php /usr/share/refdb/www/refdbadmin.php /usr/share/refdb/www/refdbdbquery.php /usr/share/refdb/www/refdbkajquery.html /usr/share/refdb/www/refdbkajsearch.php /usr/share/refdb/www/refdblogout.php /usr/share/refdb/www/refdbq.css /usr/share/refdb/www/refdbquery.html /usr/share/refdb/www/refdbsearch.php /usr/share/refdb/xsl /usr/share/refdb/xsl/bibdb2tei.xsl /usr/share/refdb/xsl/citations.xsl /usr/share/refdb/xsl/common-refdb /usr/share/refdb/xsl/common-refdb/refdbvar.xsl /usr/share/refdb/xsl/docbk-refdb-xsl /usr/share/refdb/xsl/docbk-refdb-xsl/docbk-fo /usr/share/refdb/xsl/docbk-refdb-xsl/docbk-fo/docbk-refdb-fo.xsl /usr/share/refdb/xsl/docbk-refdb-xsl/docbk-html /usr/share/refdb/xsl/docbk-refdb-xsl/docbk-html/docbk-refdb-html.xsl /usr/share/refdb/xsl/docbk-refdb-xsl/docbk-lib /usr/share/refdb/xsl/docbk-refdb-xsl/docbk-lib/docbk-refdblib.xsl /usr/share/refdb/xsl/docbk-refdb-xsl/docbk-xhtml /usr/share/refdb/xsl/docbk-refdb-xsl/docbk-xhtml/docbk-refdb-xhtml.xsl /usr/share/refdb/xsl/makecss.xsl /usr/share/refdb/xsl/tei-refdb-xsl /usr/share/refdb/xsl/tei-refdb-xsl/tei-fo /usr/share/refdb/xsl/tei-refdb-xsl/tei-fo/tei-refdb-fo.xsl /usr/share/refdb/xsl/tei-refdb-xsl/tei-html /usr/share/refdb/xsl/tei-refdb-xsl/tei-html/tei-refdb-html.xsl /usr/share/refdb/xsl/tei-refdb-xsl/tei-lib /usr/share/refdb/xsl/tei-refdb-xsl/tei-lib/tei-refdblib.xsl /var/lib/refdb/db /var/www/refdb/admin.php /var/www/refdb/include.php /var/www/refdb/index.html /var/www/refdb/login.php /var/www/refdb/refdb-prl-del.php /var/www/refdb/refdbadd.html /var/www/refdb/refdbadd.php /var/www/refdb/refdbadmin.php /var/www/refdb/refdbdbquery.php /var/www/refdb/refdbkajquery.html /var/www/refdb/refdbkajsearch.php /var/www/refdb/refdblogout.php /var/www/refdb/refdbq.css /var/www/refdb/refdbquery.html /var/www/refdb/refdbsearch.php --=20 St=E9phane T=E9letch=E9a, PhD. http://www.steletch.org Unit=E9 Math=E9matique Informatique et G=E9nome http://migale.jouy.inra.f= r/mig INRA, Domaine de Vilvert T=E9l : (33) 134 652 891 78352 Jouy-en-Josas cedex, France Fax : (33) 134 652 901 |
|
From: Markus H. <mar...@mh...> - 2006-06-28 19:29:18
|
Damien Jade Duff writes: > I am planning to make some improvements to my basic jEdit RefDB > interface and since maybe one day this might be useful to someone else, > I think I'm justified in seeing if anyone wants to comment before I get > up to my armpits in the technical details of java GUI building. If > you're interested in jEdit GUIs for RefDB, read on. > First of all, any attempts at a graphical interface to RefDB are greatly appreciated. I know that not everyone is fond enough of Emacs (or vim) to use the existing interfaces. > Incidentally, in order to create links directly between xnotes at > present I would have to create dummy references for these to point to. > Is this sensible, or am I trying to push the system too far? (i.e. as > well as keeping a bibliography I want to use the system to keep notes > and it seems nearly adapted to this in structure). Whaddya reckon? > You mean linking notes to notes? I'd have to check whether this could be supported natively. > The former has the advantage that it doesn't stretch jEdit's memory and > is has a reasonably straightforward partial-synchronisation strategy. > But it means that I need to impose more structure on my reference > database so that I can browse it in a local fashion. refdbc does provide > a facility for extracting the author list, keyword list, journal list, > etc though unfortunately there is no facility for an anadorned list of > citation keys or note keys (I could probably figure how to do this even > though c gives me a headache, but perhaps it could be included in the > next release...? Also, presumably titles are not indexed fields). I > _think_ refdb should be fast enough if I choose my methods of data > extraction right. > I could add functions that retrieve lists for citation keys, notes keys, and essentially any other field that you may be interested in. It will make the interface a bit clumsier though, as there will be a variety of fairly specialized commands that are of no interest to the regular command line user. One thing that I've always been pondering is server-side paging. I don't know whether you had something similar in mind, but I feel refdbd should be able to return the results of queries in chunks of an arbitrary size. This way, a graphical app could request e.g. the results 11-20 of a query without having to cache the remaining 5000 hits. This should be doable as long as SQL supports this (I think it does). regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
|
From: Damien J. D. <D.J...@cs...> - 2006-06-23 11:56:39
|
Hello all I am planning to make some improvements to my basic jEdit RefDB interface and since maybe one day this might be useful to someone else, I think I'm justified in seeing if anyone wants to comment before I get up to my armpits in the technical details of java GUI building. If you're interested in jEdit GUIs for RefDB, read on. At the moment all I have is a hacked-together jEdit dockable that allows me to add references and notes in bibtex, ris, risx, update them in ris or risx, delete them by id, get lists of them via a search field, etc. as well as dumping an risx template to the editing buffer. It calls refdbc directly and passes and retrieves info through the command-line, STDOUT, STDIN, STDERR, etc. However, I have a sizeable number of references (about 120) in the system now and my interface is too clunky. It takes a few seconds to pull back all the references from my local postgresql db, no matter the format, so I'd like to have a way of browsing the references in an easier, faster and more intelligent way. Also, linking references and notes is a bugger because I've got to remember the keys of each one, etc. Optimally I'd like to be able to jump to a reference and start entering notes on it, linking it to other references and notes, etc Essentially, I want to be browsing a visual structure of references and notes, like a tree (as with the BufferList plugin or something similar). Incidentally, in order to create links directly between xnotes at present I would have to create dummy references for these to point to. Is this sensible, or am I trying to push the system too far? (i.e. as well as keeping a bibliography I want to use the system to keep notes and it seems nearly adapted to this in structure). Whaddya reckon? Anyway, I think I have two ways forward - a tightly-coupled approach where I get small chunks of info back from refdbc only when I need it, and a loosely-coupled approach where I download a whole bunch of barely pre-filtered info from refdbc into jEdit memory space and make some effort to keep it synchronised. The former has the advantage that it doesn't stretch jEdit's memory and is has a reasonably straightforward partial-synchronisation strategy. But it means that I need to impose more structure on my reference database so that I can browse it in a local fashion. refdbc does provide a facility for extracting the author list, keyword list, journal list, etc though unfortunately there is no facility for an anadorned list of citation keys or note keys (I could probably figure how to do this even though c gives me a headache, but perhaps it could be included in the next release...? Also, presumably titles are not indexed fields). I _think_ refdb should be fast enough if I choose my methods of data extraction right. The latter has the advantage that I can do quick searches through the data locally without requiring too much structure in the database (e.g. title, keyword, author searches). Essentially I can do what I want with the data. But a lot of the data needs to be kept in jEdit memory space, and if I want to produce something that is scaleable to industrial operations it may not be perfect (should I care about this?), and it somewhat defeats the purpose of keeping them in a database since I could've just read it all in from a flat file. Ultimately, the former is an alluring option because it absolutely forces me to add some more structure to my DB, which I see happening by exploiting the xnotes facility and exploiting the keyword facility in a more disciplined way (e.g. rather than adding the keywords "genetic programming", and "example source", I add the keywords "entered for/example source", "subject/genetic programming"). But the latter is going to be faster to use. Any ideas would be welcome. However I do this part, the visible result will be a jEdit dockable that contains a tree of references and notes. Filtering is possible, as well as changing which tree model is displayed (e.g. by author last-name or title or keyword, or, best, by citation key, if we can change refdbc to dump an anadorned list of citation keys). Adding of links should be a case of selecting multiple items and clicking "Link" (probably a context-sensitive menu). Actual editing of entries is still done using the jEdit XML tool validating against the risx dtd, or via plaintext RIS or bibtex mode (though only for new entries). Note, also, I have no current plans to integrate any of this with docbook or latex because I don't use docbook and because the command-line latex tools are sufficient at present (though of course facilities for copying citation keys to the clipboard are easy enough to do). Anyway, I've rambled on enough. If you want some input into this project, or you just have some half-baked ideas, please post back to the list. If someone has already made a start on something I'd like to hear more about it. At my expected rate of progress, I don't anticipate having anything worth sharing for some time (maybe 6 months). Peace Damien |
|
From: Sandy R. <sa...@kr...> - 2006-05-23 15:16:09
|
Hi Markus,
On Tue, 23 May 2006 you wrote:
>> user's preferences could be stored there as PHP code and sucked in and
>> executed as necessary.
>>
>> Does this seem reasonable?
> This certainly would not hurt. Other interfaces might use such a field for
> similar purposes, whereas e.g. a command line interface would simply ignore
> this field. Implementing this would require two changes:
That sounds reasonable. For other interfaces to use it, best would be
to give it a generic format. Something like:
Key = Val
entries. In that case, it would be the responsibility of the user
interface to find the keys that it needs, parse them, and assign
default values to keys that it can't find. Storing this field as PHP
code would cause grief for other user interfaces. Some of the keys
would likely be user interface specific, but others could be
standardised. This would allow appropriate user prefs to be preserved
across change of user interface. A typical example, would be the
default RIS fields to display when entering a new entry.
Sandy
|
|
From: Markus H. <mar...@mh...> - 2006-05-23 14:58:15
|
Sandy Rutherford <sa...@kr...> was heard to say: > Hi St=E9phane & Markus, > > Giving this some initial thought, it strikes me that key to having a > nice user interface is to allow users to set db-dependent user > preferences. The RIS specification is too long to imagine having an > unconfigurable user interface, which is efficient. The obvious place > to store the preferences is in refdb itself. The table t_user could > have a third field, user_prefs, which is an alphanumeric string. The > user's preferences could be stored there as PHP code and sucked in and > executed as necessary. > > Does this seem reasonable? This certainly would not hurt. Other interfaces might use such a field for similar purposes, whereas e.g. a command line interface would simply ignore this field. Implementing this would require two changes: - add client functions which store and retrieve the preferences - change the management of the t_user table. Currently an entry in this table is created whenever a user stores or picks his first reference, and it is deleted as soon as the user's last reference is deleted or dropped. The entry would have to be created and deleted through the adduser/deleteuser commands. regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
|
From: Sandy R. <sa...@kr...> - 2006-05-23 14:39:36
|
Hi St=E9phane & Markus, Giving this some initial thought, it strikes me that key to having a nice user interface is to allow users to set db-dependent user preferences. The RIS specification is too long to imagine having an unconfigurable user interface, which is efficient. The obvious place to store the preferences is in refdb itself. The table t_user could have a third field, user_prefs, which is an alphanumeric string. The user's preferences could be stored there as PHP code and sucked in and executed as necessary. Does this seem reasonable? Sandy |
|
From: <ste...@jo...> - 2006-05-23 14:21:07
|
Sandy Rutherford a =E9crit : > Hi St=E9phane, >=20 > On Tue, 23 May 2006 you wrote: >=20 > > You can also have a look at refbase (http://refbase.sf.net) which ha= s=20 > > another web interface, just to not start from scratch. >=20 > How do refdb & refbase compare? I haven't run refbase, but from first > glance the database back-end, and certainly the documentation, for > refdb seem more solid. >=20 > Sandy >=20 refdb is far more complete (more sql server: sqlite, mysql, postgresql),=20 more input/output but more complex to implement. I was providing you the link to refbase since i'm packaging both (for=20 Mandriva Linux) for my own needs (soon, Mark, too much holidays on May=20 to just finish the job, but packaging is ok, i just want to the all=20 before putting on the servers). Refbase is web-based only (so there are pros and cons), it just another=20 implementation example (since it is gpl, you can take some code from it). Yours, St=E9phane --=20 St=E9phane T=E9letch=E9a, PhD. http://www.steletch.org Unit=E9 Math=E9matique Informatique et G=E9nome http://migale.jouy.inra.f= r/mig INRA, Domaine de Vilvert T=E9l : (33) 134 652 891 78352 Jouy-en-Josas cedex, France Fax : (33) 134 652 901 |
|
From: <ste...@jo...> - 2006-05-23 14:06:31
|
Markus Hoenicka a =E9crit : > Hi Sandy, >=20 > Sandy Rutherford <sa...@kr...> was heard to say: >=20 >=20 >>I have been looking for something to manage bibliographical databases >>for a project that I manage at IRMACS (http://www.irmacs.ca). refdb >>seems to do what I want, but it would help a lot if the web interface >>were better. >> >=20 >=20 > :-( Unfortunately I have to agree. The current version is a reimplement= ation of > the previous CGI version and barely makes use of the capabilities of PH= P. I > would like to see at least clickable author names and such, plus reason= able > forms to manually enter bibliographic data. >=20 >=20 >>I am willing to invest time and effort into the PHP interface, but >>obviously would like to coordinate with current development. Who is >>working on the PHP interface? >> >=20 >=20 > You're welcome to do so. The PHP version was contributed by Tom Bartolu= cci. I've > fiddled a bit with the code, mainly to make the installation more porta= ble. But > since then essentially no one has touched the code. The friction caused= by > coordination should be close to nil. >=20 > If you're serious about a web interface, feel free to start with comple= tely > fresh ideas. There is great stuff out there. Today I came across > http://www.openlaszlo.org/ which could turn your web browser into a End= Note > lookalike. Use whatever is likely to allow you to finish something with= the > least amount of effort. >=20 > regards, > Markus >=20 You can also have a look at refbase (http://refbase.sf.net) which has=20 another web interface, just to not start from scratch. St=E9phane --=20 St=E9phane T=E9letch=E9a, PhD. http://www.steletch.org Unit=E9 Math=E9matique Informatique et G=E9nome http://migale.jouy.inra.f= r/mig INRA, Domaine de Vilvert T=E9l : (33) 134 652 891 78352 Jouy-en-Josas cedex, France Fax : (33) 134 652 901 |
|
From: Sandy R. <sa...@kr...> - 2006-05-23 13:46:51
|
Hi St=E9phane, On Tue, 23 May 2006 you wrote: > You can also have a look at refbase (http://refbase.sf.net) which ha= s=20 > another web interface, just to not start from scratch. How do refdb & refbase compare? I haven't run refbase, but from first glance the database back-end, and certainly the documentation, for refdb seem more solid. Sandy > St=E9phane > --=20 > St=E9phane T=E9letch=E9a, PhD. http://www.steletch.= org > Unit=E9 Math=E9matique Informatique et G=E9nome http://migale.jouy.i= nra.fr/mig > INRA, Domaine de Vilvert T=E9l : (33) 134 652 891 > 78352 Jouy-en-Josas cedex, France Fax : (33) 134 652 901 |
|
From: Sandy R. <sa...@kr...> - 2006-05-23 13:26:22
|
Markus, On Tue, 23 May 2006 you wrote: > Hi Sandy, > Sandy Rutherford <sa...@kr...> was heard to say: >> I have been looking for something to manage bibliographical databases >> for a project that I manage at IRMACS (http://www.irmacs.ca). refdb >> seems to do what I want, but it would help a lot if the web interface >> were better. >> > :-( Unfortunately I have to agree. The current version is a reimplementation of > the previous CGI version and barely makes use of the capabilities of PHP. I > would like to see at least clickable author names and such, plus reasonable > forms to manually enter bibliographic data. Yes, a better form interface for entering data is number 1 on my list. >> I am willing to invest time and effort into the PHP interface, but >> obviously would like to coordinate with current development. Who is >> working on the PHP interface? >> > You're welcome to do so. The PHP version was contributed by Tom Bartolucci. I've > fiddled a bit with the code, mainly to make the installation more portable. But > since then essentially no one has touched the code. The friction caused by > coordination should be close to nil. I'll dive in then and keep you up to date with development. > If you're serious about a web interface, feel free to start with completely > fresh ideas. There is great stuff out there. Today I came across > http://www.openlaszlo.org/ which could turn your web browser into a EndNote > lookalike. Use whatever is likely to allow you to finish something with the > least amount of effort. I'll check into openlaszlo. I wasn't aware of it. Of course with all of these things, one needs to decide if the extra overhead is worth the gains. For us the big advantage of refdb is the ability to work with BiBTeX databases. In the mathematical sciences, TeX is the defacto standard for publishing. Sandy |
|
From: Markus H. <mar...@mh...> - 2006-05-23 12:51:04
|
Hi Sandy, Sandy Rutherford <sa...@kr...> was heard to say: > I have been looking for something to manage bibliographical databases > for a project that I manage at IRMACS (http://www.irmacs.ca). refdb > seems to do what I want, but it would help a lot if the web interface > were better. > :-( Unfortunately I have to agree. The current version is a reimplementation of the previous CGI version and barely makes use of the capabilities of PHP. I would like to see at least clickable author names and such, plus reasonable forms to manually enter bibliographic data. > I am willing to invest time and effort into the PHP interface, but > obviously would like to coordinate with current development. Who is > working on the PHP interface? > You're welcome to do so. The PHP version was contributed by Tom Bartolucci. I've fiddled a bit with the code, mainly to make the installation more portable. But since then essentially no one has touched the code. The friction caused by coordination should be close to nil. If you're serious about a web interface, feel free to start with completely fresh ideas. There is great stuff out there. Today I came across http://www.openlaszlo.org/ which could turn your web browser into a EndNote lookalike. Use whatever is likely to allow you to finish something with the least amount of effort. regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
|
From: Sandy R. <sa...@kr...> - 2006-05-23 11:13:02
|
From a newcomer... I have been looking for something to manage bibliographical databases for a project that I manage at IRMACS (http://www.irmacs.ca). refdb seems to do what I want, but it would help a lot if the web interface were better. I am willing to invest time and effort into the PHP interface, but obviously would like to coordinate with current development. Who is working on the PHP interface? Thanks, Sandy Rutherford |
6 messages has been excluded from this view by a project administrator.
