refdb-users — List for RefDB users

Re: [Refdb-users] RefDB and Jurabib

[Doug du B. <dou...@gm...>]

On 4/16/07, Markus Hoenicka <mar...@mh...> wrote:

> Quoting doug <dou...@gm...>:
> > I think it took me about a month of Sunday afternoons to assemble
> RefDB-lite,
> > so I would really, really like to think that someone somewhere might
> actually
> > find a use for this thing (if it couldn't be rolled into the RefDB
> > distribution in some minor capacity?).


> On the long run we'd have to reorganize the XSLT code in a way to
> create TEI as well as DocBook output. I'm sure these output formats
> can share code to some degree. A different story is SGML which I still
> have to support (in order to generate word processor compatible
> output) - this will require an entirely new implementation in DSSSL.

As I recall, that was a route to RTF format no? Maybe now with
the MS word and OpenOffice.org XML formats there may be other
pure XSLT based avenues?

> If we were able to refactor refdb-lite to do at least what the current
> RefDB code does, I'd be happy to roll it into the RefDB distribution
> in more than just a minor capacity. We should probably take our time
> and extend the code along with the extended data model that is
> supposed to be included in post-1.0 releases of RefDB.
>
> It will probably take me as many Sunday afternoons to understand your
> code as it took you to write it. Would you be able to spend some more
> time in the future on this project?

It was written at a time when I had toooo much free time on my hands.
But I would be prepared to spend some more time  on it, and happy to try and
explain the inner workings if you were of a mind to adapt or recode to some
other style/purpose.

> One more thing. I noticed you had hacked a CGI script to retrieve
> references from RefDB on the fly. While I believe that it is always
> better to have the references as an XML file along with your document
> (only then you can validate it), RefDB 0.9.9 will have a SRU interface
> which allows retrieving datasets via an URL. refdb-lite could be
> changed to use the SRU interface for this purpose.

Basically the way it works was to suck all the references out of RefDB in RISX
format, then XSLT transform them to my arbitrary DocBook raw format
(about 5% of the code),
then format DocBook raw according to your citestylex specs (about 95%
of the code). It also works fine with a separate DocBook raw
bibliography file.  The XSLT to extract and organise the RISX could be
reused to make it a distinct two step process,
saving DocBook raw to a separate file and then applying formatting afterwards.
(though I recall that my DocBook raw intermediate format may have had some
shortcomings).

This also means that opportunities for code sharing with a TEI output option
may be quite limited ( I have never even looked at TEI to see if there are
similar raw bibliography structuring conventions).

cheers
Doug

Re: [Refdb-users] troubles with phpweb setup

[Cecile H. <cec...@tu...>]

Markus Hoenicka wrote:

> I suspect your problems are rooted in some change of the Apache
> configuration file syntax. Unless someone on this list can provide an
> apache2 configuration file that works with RefDB, I'd suggest to take
> this question to an Apache mailing list or forum. As the changes to
> httpd.conf required by the RefDB PHP interface are very limited,
> someone might be able to tell you in an instant how to do this with
> apache2. If you find an answer, please let the list know. I'd like to
> add this to the documentation.

What I did is
- make a symbolik link:
ln -s /usr/local/share/refdb/web /my_server_root/refdb

Add the following to the config file:

<VirtualHost XX.XX.XX.XX:80>
DocumentRoot /my_server_root
ServerName tem.atp.tuwien.ac.at
ScriptAlias /cgi-bin/ "/XXX/cgi-bin"
Alias /refdb/ "/usr/local/share/refdb/www/"
<Directory "/usr/local/share/refdb/www">
Options FollowSymLinks +ExecCGI
AllowOverride None
Order allow,deny
Allow from all
AddType application/x-httpd-php .php .phtml
</Directory>


It works, I just have to call
http://tem.atp.tuwien.ac.at/refdb/
*WITH* the trailing slash. Does not work without.

I am not sure this is the most "academic" way, but at least I get the 
pages... (somehow I feel the symbolic linkt should not be necessary...)

> Did you check the Apache log (usually /var/log/httpd-errors.log)?
> You might find additional clues in the error messages.

Mh, seems to be a php problem:

[Mon Apr 16 23:06:32 2007] [error] [client 195.230.58.82] PHP Notice: 
Undefined variable: passwd in /usr/local/share/refdb/www/login.php on 
line 6, referer: http://tem.atp.tuwien.ac.at/refdb/index.html

But :
miraculix 114> httpd2 -M
Loaded Modules:
.
.
.
  php5_module (shared)
Syntax OK

> Does php run ok on your box? Try "php -v".

miraculix 102> php5 -v
PHP 5.1.2 (cli) (built: May  2 2006 10:19:57)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies

So I would say php seems to run ?

Cécile

-- 
Dr. Cécile Hébert, Inst. f. Festkörperphysik
TU Wien, Wiedner Hauptstrasse  8-10 A-1040 WIEN
cec...@tu...   tel +43 1 58 801 138 15 fax - 138 99
http://tem.atp.tuwien.ac.at/leute/cecile.html
http://www.ncc.at/cecile/photos/index.html

[Refdb-users] ANN: refdb-0.9.9-pre1 available

[Markus H. <mar...@mh...>]

Hi,

I've integrated the refdb-sru branch into the main development
line. The new prerelease thus contains all modifications that were
announced previously for the refdb-sru branch, plus all bugfixes and
improvements developed since the merge. Not all of these changes are
related to the SRU support, so even users not interested in SRU will
benefit from this new prerelease.

Once again, if you're interested in the SRU interface, please read
this brief introduction:

http://refdb.sourceforge.net/sru.html

To install the new prerelease, please download the following files
(older versions of the Perl modules will not work with this prerelease):

http://refdb.sourceforge.net/pre/refdb-latest.tar.gz

http://refdb.sourceforge.net/pre/RefDB-perlmod-1.2.tar.gz

http://refdb.sourceforge.net/pre/RefDB-Client-1.17.tar.gz

http://refdb.sourceforge.net/pre/RefDB-SRU-0.6.tar.gz


The bugfixes and improvement are listed below. It is not strictly
necessary to upgrade your system or reference databases, but you
should consult the UPGRADING file for a possible problem with RIS
data.

regards,
Markus


Bugfixes:

- special characters are now properly converted to XML entities even
  in long texts with lots of these characters

- now purges "(", ")", and "?" from citation keys

- now checks the reference types before adding them to the
  database. Unknown types are changed to "GEN".

- a sanity check in the RIS import code prevents segfaults if risx
  data are accidentally fed to it.

- risx datasets which are accidentally added as RIS datasets no longer
  crash refdbd.

- a possible client/server hiccup caused by checkref reports of a
  particular size was fixed.

- the handling of the (entirely broken by design) issue, edition, and
  volume fields in a variety of reference types has been improved


Improvements

- the new refdbc:countref and refdbc:countnote commands are equivalent
  to the getref and getnote commands, respectively, except that they
  do not actually retrieve the reference or note data. Instead, they
  return the number of matching references and notes, respectively.

- the query language supports additional relational operators: <=
  (less than or equal), >= (larger than or equal), <> (not like).

- there is a new backend for MODS output, an XML format maintained by
  the Library of Congress.

- the XML output (risx, mods, xnote) now supports namespaces.

- the -n switch of getbib is no longer supported (it was hardly ever
  used anyway). refdbd now sends a stylespec no matter what.

- the getnote/countnote commands now also support query strings of
  unlimited length, just like the getref/countref commands.

- the adduser/deleteuser commands now support two classes of users:
  read-only users and read/write-users. The former is a simple way to
  generate a database account for users accessing your databases through
  SRU or via the web interface without permitting write access to
  your databases for everyone.

- the new CGI script refdbsru provides an optional SRU (Search and
  Retrieve via URL) interface to your databases.

- the checkref command can now be limited to check individual fields
  or combinations of fields.

- improved import of tagged Pubmed data (med2ris)

- digital object identifiers (DOI) are now harvested from Pubmed data
  and are stored properly. DOIs are presented as links (via
  dx.doi.org) by the (x)html backend.



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

[Refdb-users] troubles with phpweb setup

[Markus H. <mar...@mh...>]

Hi C=E9cile,

Cecile Hebert writes:
 > I am using apache2 and webmin as an administration interface, and I =
have=20
 > the feeling the example apache configuration example does not look l=
ke=20
 > the config files I have. I was not able to bring the link from=20
 > /usr/local/share/refdb/www/ to /refdb/ to work, neither by using a=20=

 > symbolic link (even with +FollowSimLinkoption) nor by making the lin=
k in=20
 > the config file.
 >=20
 > So I tryed to  hard copy the www directory to the  root directory of=
 my=20
 > web server. This works somehow, I can see the pages, fill the forms,=
 ask=20
 > for references and get no errors messages... but no references at al=
l.=20
 > And I see nothing happening in the window where refdbd should give l=
ogs.
 >=20
 >=20
 > Does phpweb needs refdb working as a daemon=3F=3F
 > Can someone tell me how to set up apache2 properly=3F
 > Does someone knows where the error can come from=3F
 >=20

I don't run apache2 over here. I've checked the installation
instructions again with my Apache 1.3 installation on FreeBSD. All I
needed to do is to follow the instructions in phpweb/INSTALL, using
the OS-specific tweaks as usual:

- I had to rebuild php5 as it was configured without mod=5Fphp5 support=

- then I had to build a matching php5-session package
- the changes for httpd.conf were already in place, so everything
  worked from that point on.

I suspect your problems are rooted in some change of the Apache
configuration file syntax. Unless someone on this list can provide an
apache2 configuration file that works with RefDB, I'd suggest to take
this question to an Apache mailing list or forum. As the changes to
httpd.conf required by the RefDB PHP interface are very limited,
someone might be able to tell you in an instant how to do this with
apache2. If you find an answer, please let the list know. I'd like to
add this to the documentation.

Did you check the Apache log (usually /var/log/httpd-errors.log)=3F
You might find additional clues in the error messages.

Does php run ok on your box=3F Try "php -v".

Finally, refdbd does not have to run as a daemon. The PHP interface
calls only the clients, which then access refdbd. The clients don't
care whether refdbd runs as a standalone process or as a daemon. If
you configure the clients appropriately, you could even run refdbd on
a different box without breaking the PHP interface.

regards,
Markus

--=20
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] troubles with phpweb setup

[Cecile H. <cec...@tu...>]

Dear all,

I am trying to set up pwpweb  under suse linux 10.1, without much 
success :-(

refdfworks fine, still in the "debug" mode (refdbd -s -e 0 -l 7), I can 
connect thru refdba and refdbc, manage users and references...

I am using apache2 and webmin as an administration interface, and I have 
the feeling the example apache configuration example does not look lke 
the config files I have. I was not able to bring the link from 
/usr/local/share/refdb/www/ to /refdb/ to work, neither by using a 
symbolic link (even with +FollowSimLinkoption) nor by making the link in 
the config file.

So I tryed to  hard copy the www directory to the  root directory of my 
web server. This works somehow, I can see the pages, fill the forms, ask 
for references and get no errors messages... but no references at all. 
And I see nothing happening in the window where refdbd should give logs.


Does phpweb needs refdb working as a daemon??
Can someone tell me how to set up apache2 properly?
Does someone knows where the error can come from?

Thank you for any help!
  Cécile


-- 
Dr. Cécile Hébert, Inst. f. Festkörperphysik
TU Wien, Wiedner Hauptstrasse  8-10 A-1040 WIEN
cec...@tu...   tel +43 1 58 801 138 15 fax - 138 99
http://tem.atp.tuwien.ac.at/leute/cecile.html
http://www.ncc.at/cecile/photos/index.html

Re: [Refdb-users] Doubt about interfece with Refdb

[Markus H. <mar...@mh...>]

Quoting Daniel O'Donnell <dan...@ul...>:

> We won't have it done for this week. Too many other engagements. It is
> annoying to be so close but not done, but there you have it.
>

I understand. I'll go ahead with 0.9.9-pre1. We can do another  
prerelease as soon as you have your code ready.

regards,
Markus


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

Re: [Refdb-users] RefDB and Jurabib

[Markus H. <mar...@mh...>]

Hi Doug,

Quoting doug <dou...@gm...>:

> I think it took me about a month of Sunday afternoons to assemble RefDB-li=
te,
> so I would really, really like to think that someone somewhere might actua=
lly
> find a use for this thing (if it couldn't be rolled into the RefDB
> distribution in some minor capacity?).
>

Thanks a lot for bringing this up again. I was admittedly not able to =20
run some serious tests in the past to evaluate the code, but I'm sure =20
this is a starting point for the raw bibliography formatting I was =20
talking about. As for Jeremy's formatting requirements, he will =20
probably not only have to fiddle with the XSLT, but also with RefDB's =20
data model to include the additional fields which are not covered at =20
the moment.

On the long run we'd have to reorganize the XSLT code in a way to =20
create TEI as well as DocBook output. I'm sure these output formats =20
can share code to some degree. A different story is SGML which I still =20
have to support (in order to generate word processor compatible =20
output) - this will require an entirely new implementation in DSSSL.

If we were able to refactor refdb-lite to do at least what the current =20
RefDB code does, I'd be happy to roll it into the RefDB distribution =20
in more than just a minor capacity. We should probably take our time =20
and extend the code along with the extended data model that is =20
supposed to be included in post-1.0 releases of RefDB.

It will probably take me as many Sunday afternoons to understand your =20
code as it took you to write it. Would you be able to spend some more =20
time in the future on this project?

One more thing. I noticed you had hacked a CGI script to retrieve =20
references from RefDB on the fly. While I believe that it is always =20
better to have the references as an XML file along with your document =20
(only then you can validate it), RefDB 0.9.9 will have a SRU interface =20
which allows retrieving datasets via an URL. refdb-lite could be =20
changed to use the SRU interface for this purpose.

regards,
Markus


--=20
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-users] Doubt about interfece with Refdb

[Daniel O'D. <dan...@ul...>]

We won't have it done for this week. Too many other engagements. It is
annoying to be so close but not done, but there you have it.

-dan

On Sat, 2007-04-14 at 23:34 +0200, Markus Hoenicka wrote:
> Daniel O'Donnell writes:
>  > Domink Reusser and I have a completely rewritten PHP interface that we
>  > are just trying to finish before it gets published. You're welcome to
>  > take a look at that.
>  > 
> 
> Do you have an estimate how long it is going to take? I've got my SRU
> stuff in a state that would allow a prerelease next week. Just let me
> know if you want the PHP interface included, or if you prefer to
> take your time.
> 
> regards,
> Markus
> 
-- 
Daniel Paul O'Donnell, PhD
Department Chair and Associate Professor of English
Director, Digital Medievalist Project http://www.digitalmedievalist.org/
Chair, Text Encoding Initiative http://www.tei-c.org/

Department of English
University of Lethbridge
Lethbridge AB T1K 3M4
Vox +1 403 329-2377
Fax +1 403 382-7191
Email: dan...@ul...
WWW: http://people.uleth.ca/~daniel.odonnell/

Re: [Refdb-users] RefDB and Jurabib

[doug <dou...@gm...>]

On Sunday 15 April 2007 10:17, Markus Hoenicka wrote:
> Jeremy Malcolm writes:
>  > Sorry, you're right and I should have been more exact.  I just meant
>  > that this explains why I need to move to Jurabib and drop DocBook
>  > (despite preferring SGML/XML to TeX), as the former supports all the
>  > features that I mentioned needing in that post - even down to enclosing
>  > the year in parentheses for journals that use a volume number, and
>  > square brackets for those that don't.
>  >
>  > I agree that this kind of thing is too obscure to expect RefDB to
>  > support, or at least should be a lower priority to implement.  Since TeX
>  > will always be a more fine-grained tool for formatting, I think it is
>  > better to use it for that for now, and RefDB just as a reference
>  > database.  Do you agree, or is it worth trying to duplicate some of
>  > Jurabib's obscure formatting features?
>
> Well, it is probably not worth attempting this with RefDB's current
> bibliography code. On the long run it may be prudent to move to raw
> instead of cooked bibliography output and externalize the formatting
> of the citations and the bibliographies entirely to the publication
> step, along the lines of what citeproc does. However, this will 
> require a complete rewrite of the DSSSL and XSLT stylesheets, and this
> is not likely to happen on a rainy Sunday afternoon.

I am sure I have mentioned this before, probably more than once (sorry), 
but such a thing already exists, in some limited capacity (for DocBook 
at any rate).

I called it RefDB-lite and the xslt (1.1?) sources are languishing here:
http://ugo.crl.nitech.ac.jp/~ddb/CIF/skunkworks/xsl/refdb-lite-0.0.0.5a.tgz 
and the documentation is here:
http://ugo.crl.nitech.ac.jp/~ddb/CIF/skunkworks/xsl/refdb-lite/doc/refdb-lite/
and also in a couple of different forms in the examples directory:
http://ugo.crl.nitech.ac.jp/~ddb/CIF/skunkworks/xsl/refdb-lite/examples/

You would probably need to customize the XSLT template that identifies the 
citations, since I adopted the newer DocBook <biblioref> element, rather than 
<xref>. 

And Jeremy would likely need to customize the 
http://ugo.crl.nitech.ac.jp/~ddb/CIF/skunkworks/xsl/refdb-lite/xsl/docbook/common/journalname.xsl
template - to add parenthesis.


I think it took me about a month of Sunday afternoons to assemble RefDB-lite, 
so I would really, really like to think that someone somewhere might actually 
find a use for this thing (if it couldn't be rolled into the RefDB 
distribution in some minor capacity?). 

thank you.
Doug

Re: [Refdb-users] RefDB and Jurabib

[Markus H. <mar...@mh...>]

Hi Jeremy,

Jeremy Malcolm writes:
 > I'm resending this message because this didn't appear in the last 
 > archives after two days so I guess it got lost along the way.  Sorry if, 
 > despite that, it is in fact a duplicate.
 > 

I'm afraid it was a duplicate but don't worry about that. The list
archives are not a good way to check whether your mail went through
because they often lag behind a week or more.

 > It does not store them.  Amonst the unusual ones that Jurabib needs are
 > booktitle, edition, howpublished, institution, language, school, series,
 > type, urldate, volumetitle, dissyear, howcited, shorttitle, shortauthor,
 > ssedition, titleaddon, booktitleaddon, editortype, sortkey, annote,
 > gender, translator, updated, totalpages, founder, archive, and a number
 > of others, most of which are documented at
 > http://jurabib.homelinux.org/jurabib/docs/english/jbendoc.html, but
 > others only in the source code.

Apparently there is no comprehensive (or comprehensible?) list of
fields which Jurabib actually uses. I've found a few fields mentioned
in that documentation, but even in those case it is not always clear
to me what information they are supposed to carry.

 > 
 > Admittedly, not all of these are equally important, and some can use
 > other existing fields; for example urldate can probably use a secondary
 > pubdate, edition can sometimes use volume (but what if there is a volume
 > *and* an edition?), and some of the others might be able to use the
 > spare fields (refdb_user1-user5 and refdb_misc1-misc3) in the refdb
 > database table.
 > 

The following mapping seems to make sense to me:

booktitle: BT

edition (book, chapter, and a few others): VL (the SVN version treats
this internally like an issue, as that is used only for periodical
publications)

institution (thesis, conference and the like): PB

school (thesis): PB

urldate: Y2

dissyear (thesis?): PY

annote: N1

The following fields whose semantics I believe to understand are
currently not supported: language, howcited

The following "fields" seem to depend on the citation style and should
as such not be stored in the database, but created from other fields
(I'm not sure though): shorttitle, shortauthor

All other fields are unclear to me and would require a formal
definition of their purpose.

 > But this doesn't really scale too well, so perhaps rather than patching
 > the code for every new field that anyone wants, there could be an
 > interface in RefDB for users to add an arbitrary number of new fields,
 > and optionally to define how these are mapped to RIS fields (though I
 > realise that RIS isn't extensible like BibTeX is).  I am probably
 > overlooking some valid reason why that isn't possible.

I've been thinking about moving to a richer data model for quite some
time. I've tried MODS a while ago but this turned out to be far too
complex (and far too flabby) to solve the problems of RIS. I've
started defining a new format called rbib
(http://refdb.sourceforge.net/rbib.html) which is still open for
modifications. You're welcome to suggest additions here.

Basically RefDB could povide a mechanism to add arbitrary properties
(implemented as key/value pairs in a separate table) to references. It
is simply a question of how we're supposed get them into and out of
the database without defining these properties in the data
formats. BibTeX is easy to extend because it does not make any
assumptions about the relationship of the fields. Other, more
structured formats like risx or rbib are harder to extend.

 > Sorry, you're right and I should have been more exact.  I just meant
 > that this explains why I need to move to Jurabib and drop DocBook
 > (despite preferring SGML/XML to TeX), as the former supports all the
 > features that I mentioned needing in that post - even down to enclosing
 > the year in parentheses for journals that use a volume number, and
 > square brackets for those that don't.
 > 
 > I agree that this kind of thing is too obscure to expect RefDB to
 > support, or at least should be a lower priority to implement.  Since TeX
 > will always be a more fine-grained tool for formatting, I think it is
 > better to use it for that for now, and RefDB just as a reference
 > database.  Do you agree, or is it worth trying to duplicate some of
 > Jurabib's obscure formatting features?
 > 

Well, it is probably not worth attempting this with RefDB's current
bibliography code. On the long run it may be prudent to move to raw
instead of cooked bibliography output and externalize the formatting
of the citations and the bibliographies entirely to the publication
step, along the lines of what citeproc does. However, this will
require a complete rewrite of the DSSSL and XSLT stylesheets, and this
is not likely to happen on a rainy Sunday afternoon. XSLT is said to
be a complete programming language and should be able to do anything
that TeX can. DSSSL (or rather, the only DSSSL engine that we have)
may be more limited and may suffer from a few restrictions though. In
any case, I guess it would require the commitment of one or more
persons who know XSLT/DSSSL and who are familiar with the citation and
bibliography requirements of legal studies and of scientific
manuscripts in the humanities.

regards,
Markus

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

Re: [Refdb-users] Doubt about interfece with Refdb

[Markus H. <mar...@mh...>]

Daniel O'Donnell writes:
 > Domink Reusser and I have a completely rewritten PHP interface that we
 > are just trying to finish before it gets published. You're welcome to
 > take a look at that.
 > 

Do you have an estimate how long it is going to take? I've got my SRU
stuff in a state that would allow a prerelease next week. Just let me
know if you want the PHP interface included, or if you prefer to
take your time.

regards,
Markus

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

Re: [Refdb-users] RefDB and Jurabib

[Jeremy M. <Je...@Ma...>]

I'm resending this message because this didn't appear in the last 
archives after two days so I guess it got lost along the way.  Sorry if, 
despite that, it is in fact a duplicate.

Marcus Hoenicka wrote:
> > Does anyone think it would be a good idea, and if so how feasible
> > would it be, to integrate support for the additional BibTeX fields
> > used by Jurabib into RefDB?
>
> What additional fields do you precisely need? Right now I'm not
> exactly sure whether RefDB does not *store* these values at all, or
> whether it does not *export* them properly to bibtex.

It does not store them.  Amonst the unusual ones that Jurabib needs are
booktitle, edition, howpublished, institution, language, school, series,
type, urldate, volumetitle, dissyear, howcited, shorttitle, shortauthor,
ssedition, titleaddon, booktitleaddon, editortype, sortkey, annote,
gender, translator, updated, totalpages, founder, archive, and a number
of others, most of which are documented at
http://jurabib.homelinux.org/jurabib/docs/english/jbendoc.html, but
others only in the source code.

Admittedly, not all of these are equally important, and some can use
other existing fields; for example urldate can probably use a secondary
pubdate, edition can sometimes use volume (but what if there is a volume
*and* an edition?), and some of the others might be able to use the
spare fields (refdb_user1-user5 and refdb_misc1-misc3) in the refdb
database table.

But this doesn't really scale too well, so perhaps rather than patching
the code for every new field that anyone wants, there could be an
interface in RefDB for users to add an arbitrary number of new fields,
and optionally to define how these are mapped to RIS fields (though I
realise that RIS isn't extensible like BibTeX is).  I am probably
overlooking some valid reason why that isn't possible.

> > [0] Basically it's as simple as having footnotes that include all
> > the same information as the bibliography entries.
...snip...
> I believe the problem is quite different now from what it was back
> then. If you cut out DocBook from your workflow, all that remains for
> RefDB to do is to export the available data properly as bibtex. There
> is essentially no formatting involved, except maybe providing the full
> or abbreviated names of journals.

Sorry, you're right and I should have been more exact.  I just meant
that this explains why I need to move to Jurabib and drop DocBook
(despite preferring SGML/XML to TeX), as the former supports all the
features that I mentioned needing in that post - even down to enclosing
the year in parentheses for journals that use a volume number, and
square brackets for those that don't.

I agree that this kind of thing is too obscure to expect RefDB to
support, or at least should be a lower priority to implement.  Since TeX
will always be a more fine-grained tool for formatting, I think it is
better to use it for that for now, and RefDB just as a reference
database.  Do you agree, or is it worth trying to duplicate some of
Jurabib's obscure formatting features?

> I'll be happy to extend RefDB's
> capabilities if you can list exactly how the bibtex output needs to
> change. I'd greatly appreciate if you could send some example data how
> that output ought to look like.

Here is an example of a BibTeX entry from the documentation:

@BOOK{broxbgb,
   author      = {Hans Brox},
   title       = {Allgemeiner Teil des B{\"u}rgerlichen Gesetzbuches},
   shorttitle  = {BGB~AT},
   year        = 1996,
   language    = {german},
   address     = {K{\"o}ln, Berlin, Bonn, M{\"u}nchen},
   edition     = 20,
   annote      = {This is a senseless test for testing the annote
field.\par If
                  you are reading this text now, note that you can switch
                  off the output of this field by removing the
\texttt{annote} op
tion
                  \begin{itemize}\item You are able to use lists inside
the annot
e field\end{itemize}}
}

-- 
Jeremy Malcolm LLB (Hons) B Com
Internet and Open Source lawyer, IT consultant, actor
host -t NAPTR 1.0.8.0.3.1.2.9.8.1.6.e164.org|awk -F! '{print $3}'

Re: [Refdb-users] Doubt about interfece with Refdb

[Daniel O'D. <dan...@ul...>]

Domink Reusser and I have a completely rewritten PHP interface that we
are just trying to finish before it gets published. You're welcome to
take a look at that.

If you mean: how do I find out about the Refdb API, then basically you
just use the manual.

-dan

On Fri, 2007-04-13 at 13:08 +0200, Verónica Orgaz wrote:
> Hi!
>  
>   I'm a computer science student and I'm making the degree final work.
> I must make a web page that contains a publications part. The
> publications are in a data base in RefDB, and I would like to add an
> interface PHP to my web page to be able to consult this DB.
>  
>   Therefore, I've the following question: Is the interfece code
> published somewhere?
>  
> VOC 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________ Refdb-users mailing list Ref...@li... https://lists.sourceforge.net/lists/listinfo/refdb-users
-- 
Daniel Paul O'Donnell, PhD
Department Chair and Associate Professor of English
Director, Digital Medievalist Project http://www.digitalmedievalist.org/
Chair, Text Encoding Initiative http://www.tei-c.org/

Department of English
University of Lethbridge
Lethbridge AB T1K 3M4
Vox +1 403 329-2377
Fax +1 403 382-7191
Email: dan...@ul...
WWW: http://people.uleth.ca/~daniel.odonnell/

[Refdb-users] Doubt about interfece with Refdb

[<ver...@gm...>]

*

Hi!

  I'm a computer science student and I'm making the degree final work. I
must make a web page that contains a publications part. The publications are
in a data base in RefDB, and I would like to add an interface PHP to my web
page to be able to consult this DB.

**  Therefore, I've the following question: Is the interfece code published
somewhere?*
**
***VOC** *

Re: [Refdb-users] RefDB and Jurabib

[Jeremy M. <Je...@Ma...>]

Marcus Hoenicka wrote:
 > > Does anyone think it would be a good idea, and if so how feasible
 > > would it be, to integrate support for the additional BibTeX fields
 > > used by Jurabib into RefDB?
 >
 > What additional fields do you precisely need? Right now I'm not
 > exactly sure whether RefDB does not *store* these values at all, or
 > whether it does not *export* them properly to bibtex.

It does not store them.  Amonst the unusual ones that Jurabib needs are 
booktitle, edition, howpublished, institution, language, school, series, 
type, urldate, volumetitle, dissyear, howcited, shorttitle, shortauthor, 
ssedition, titleaddon, booktitleaddon, editortype, sortkey, annote, 
gender, translator, updated, totalpages, founder, archive, and a number 
of others, most of which are documented at 
http://jurabib.homelinux.org/jurabib/docs/english/jbendoc.html, but 
others only in the source code.

Admittedly, not all of these are equally important, and some can use 
other existing fields; for example urldate can probably use a secondary 
pubdate, edition can sometimes use volume (but what if there is a volume 
*and* an edition?), and some of the others might be able to use the 
spare fields (refdb_user1-user5 and refdb_misc1-misc3) in the refdb 
database table.

But this doesn't really scale too well, so perhaps rather than patching 
the code for every new field that anyone wants, there could be an 
interface in RefDB for users to add an arbitrary number of new fields, 
and optionally to define how these are mapped to RIS fields (though I 
realise that RIS isn't extensible like BibTeX is).  I am probably 
overlooking some valid reason why that isn't possible.

 > > [0] Basically it's as simple as having footnotes that include all
 > > the same information as the bibliography entries.
...snip...
 > I believe the problem is quite different now from what it was back
 > then. If you cut out DocBook from your workflow, all that remains for
 > RefDB to do is to export the available data properly as bibtex. There
 > is essentially no formatting involved, except maybe providing the full
 > or abbreviated names of journals.

Sorry, you're right and I should have been more exact.  I just meant 
that this explains why I need to move to Jurabib and drop DocBook 
(despite preferring SGML/XML to TeX), as the former supports all the 
features that I mentioned needing in that post - even down to enclosing 
the year in parentheses for journals that use a volume number, and 
square brackets for those that don't.

I agree that this kind of thing is too obscure to expect RefDB to 
support, or at least should be a lower priority to implement.  Since TeX 
will always be a more fine-grained tool for formatting, I think it is 
better to use it for that for now, and RefDB just as a reference 
database.  Do you agree, or is it worth trying to duplicate some of 
Jurabib's obscure formatting features?

 > I'll be happy to extend RefDB's
 > capabilities if you can list exactly how the bibtex output needs to
 > change. I'd greatly appreciate if you could send some example data how
 > that output ought to look like.

Here is an example of a BibTeX entry from the documentation:

@BOOK{broxbgb,
   author      = {Hans Brox},
   title       = {Allgemeiner Teil des B{\"u}rgerlichen Gesetzbuches},
   shorttitle  = {BGB~AT},
   year        = 1996,
   language    = {german},
   address     = {K{\"o}ln, Berlin, Bonn, M{\"u}nchen},
   edition     = 20,
   annote      = {This is a senseless test for testing the annote 
field.\par If
                  you are reading this text now, note that you can switch
                  off the output of this field by removing the 
\texttt{annote} op
tion
                  \begin{itemize}\item You are able to use lists inside 
the annot
e field\end{itemize}}
}

-- 
Jeremy Malcolm LLB (Hons) B Com
Internet and Open Source lawyer, IT consultant, actor
host -t NAPTR 1.0.8.0.3.1.2.9.8.1.6.e164.org|awk -F! '{print $3}'

Re: [Refdb-users] RefDB and Jurabib

[Markus H. <mar...@mh...>]

Hi Jeremy,

Quoting Jeremy Malcolm <Je...@Ma...>:

> Does anyone think it would be a good idea, and if so how feasible would
> it be, to integrate support for the additional BibTeX fields used by
> Jurabib into RefDB?
>

What additional fields do you precisely need? Right now I'm not =20
exactly sure whether RefDB does not *store* these values at all, or =20
whether it does not *export* them properly to bibtex.

>
> [0] Basically it's as simple as having footnotes that include all
>      the same information as the bibliography entries.  See the thread
>      at
> http://sf.net/mailarchive/message.php?msg_id=3Dd2a04bd25ec20800d04f2548214=
b0fbe%40Malcolm.id.au
>

I believe the problem is quite different now from what it was back =20
then. If you cut out DocBook from your workflow, all that remains for =20
RefDB to do is to export the available data properly as bibtex. There =20
is essentially no formatting involved, except maybe providing the full =20
or abbreviated names of journals. I'll be happy to extend RefDB's =20
capabilities if you can list exactly how the bibtex output needs to =20
change. I'd greatly appreciate if you could send some example data how =20
that output ought to look like.

regards,
Markus

--=20
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] RefDB and Jurabib

[Jeremy M. <Je...@Ma...>]

Does anyone think it would be a good idea, and if so how feasible would 
it be, to integrate support for the additional BibTeX fields used by 
Jurabib into RefDB?

Jurabib (http://www.jurabib.org) is widely used in law and the 
humanities for writing citations that ordinary BibTeX, and RefDB for 
that matter, don't support.[0]  It is supported by recent versions of 
LyX and has an Emacs mode.  Sadly, its next release will be its last, 
but it is already pretty feature-complete.

Although it's too late for my current PhD thesis, I'm looking to moving 
from my current document workflow (LyX + BibTeX + RefDB -> DocBook -> 
formats) to include Jurabib (LyX + BibTeX + Jurabib + RefDB? -> formats) 
so that I can have proper formatting of my references.  However, I would 
be sad to cut RefDB out of the equation (I am already resigned to 
cutting out DocBook).

[0] Basically it's as simple as having footnotes that include all
     the same information as the bibliography entries.  See the thread
     at 
http://sf.net/mailarchive/message.php?msg_id=d2a04bd25ec20800d04f2548214b0fbe%40Malcolm.id.au

-- 
Jeremy Malcolm LLB (Hons) B Com
Internet and Open Source lawyer, IT consultant, actor
host -t NAPTR 1.0.8.0.3.1.2.9.8.1.6.e164.org|awk -F! '{print $3}'

[Refdb-users] ANN: New prerelease with SRU support

[Markus H. <mar...@mh...>]

Hi,

in an attempt to make RefDB more compliant with emerging standards
from the Library of Congress, especially SRU and MODS, I've extended
RefDB quite a bit. As the changes are more substantial than between
the usual prereleases, there is a separate document which explains
some background, the installation, and the basics of the usage:

http://refdb.sourceforge.net/sru.html

In brief, SRU is a method to query or browse library catalogs or
reference databases by sending specially crafted URLs. These URLs
strictly follow the HTTP conventions. You can simply type them into a
web browser, or use some piece of software that assembles and sends
the URLs. RefDB implements the SRU service as a CGI script which you
can install in your web server. The script acts as a proxy server and
retrieves the bibliographic data from your RefDB application
server. The results are formatted as a XML document as explained in
the SRU spec and sent back to the browser. The default format of
bibliographic data in SRU is MODS which refdbd is now able to
generate.

It is important to note that SRU is not meant to replace a graphical
web interface (expecially not the PHP based one that some members of
this list are busy developing). Instead, it is a means to retrieve
XML-based information from your RefDB databases via a standardized
protocol which can be used both from web browsers and from
bibliographic software.

The full list of changes is appended below. I'd greatly appreciate if
you could spend some time testing this new prerelease. As the changes
to implement SRU support are fairly complex, I'm sure that I'll have
to iron out a bunch of wrinkles before SRU support can appear in a
regular release. I'd also appreciate if you could test the new MODS
export (which of course is also available in getref - use the -t mods
switch) with your own reference data. I've found quite a few cases
where I disagree with how bibutils
(http://www.scripps.edu/~cdputnam/software/bibutils/) handle the
RIS->MODS conversion, so I'd be interested to hear whether the RefDB
MODS backend or whether bibutils should be changed.

regards,
Markus

Changes in 0.9.8-sru1

- the new refdbc:countref and refdbc:countnote commands are equivalent
  to the getref and getnote commands, respectively, except that they
  do not actually retrieve the reference or note data. Instead, they
  return the number of matching references and notes, respectively.

- the query language supports additional relational operators: <=
  (less than or equal), >= (larger than or equal), <> (not like).

- there is a new backend for MODS output, an XML format maintained by
  the Library of Congress.

- the XML output (risx, mods, xnote) now supports namespaces.

- the -n switch of getbib is no longer supported (it was hardly ever
  used anyway). refdbd now sends a stylespec no matter what.

- the getnote/countnote commands now also support query strings of
  unlimited length, just like the getref/countref commands.

- the adduser/deleteuser commands now support two classes of users:
  read-only users and read/write-users. The former is a simple way to
  generate a database account for users accessing your databases through
  SRU or via the web interface without permitting write access to
  your databases for everyone.

- the new CGI script refdbsru provides an optional SRU (Search and
  Retrieve via URL) interface to your databases.


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

Re: [Refdb-users] Upgrade failure

[Markus H. <mar...@mh...>]

Hi Bruce,

Bruce Hayward writes:
 > Markus,
 > Installed the replacement for refdb-init you sent, had to do "make" in 
 > usr/ports/textproc/refdb/ to generate the sub-directories and then did 
 > "make install" in /usr/ports/textproc/refdb/work/refdb-0.9.8/scripts/.
 > Refdb-init seems to work fine with sqlite3 and I created a database 
 > called refs and put some references into it but it isn't in 
 > /usr/local/share/refdb/db/ which is empty.
 > In fact refs doesn't appear anywhere in  /usr/local/etc/refdb/ or 
 > /usr/local/share/refdb/

That's another thing that changed between 0.9.6 and 0.9.8. I've moved
the default location of sqlite/sqlite3 databases to
/usr/local/var/lib/refdb/db in order to comply with the structure
suggested by the FHS (http://www.pathname.com/fhs/). The
/usr/local/share/refdb/db directory is no longer used these days.

regards,
Markus

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

Re: [Refdb-users] RefDB web page..

[Markus H. <mar...@mh...>]

Quoting =C4=8Eo=C4=8Fo <do...@gm...>:

> The second one was my problem. The libdbi-mysql was not installed. But
> refdbd exist without any message. I thin this is the basic message
> wchich should be printed and not only after manual execution with some
> -l and -L options.
>

The freedom to choose from several database backends is the horror of =20
all packagers. The Debian package system cannot realize that you =20
intend to use the MySQL driver, so it won't complain about unmet =20
dependencies.

I'll see whether refdbd can spit out more useful error messages when =20
run from the refdb-init script. In normal operation refdbd runs as a =20
daemon, so everything it sends to stderr is usually lost. But the =20
maintenance mode could very well send the information to stderr by =20
default.

> Create refdb as reference database
> 209:refdb
> 999:0 created:1 failed
>

The reference database should not be called "refdb". This is the only =20
name which is reserved for internal use (RefDB needs one system =20
database for styles and the journal word list). Just pick any other =20
name. I guess it wouldn't hurt to add some words along these lines to =20
the refdb-init script.

regards,
Markus

--=20
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-users] RefDB web page..

[<do...@gm...>]

TWFya3VzLAoKdGhlcmUgd2VyZSAyIHByb2JsZW1zLgpGaXJzdCBvZiBjb3Vyc2UgdGhlIGluY29y
ZWN0IHBhdGhzIGlzIHJlZmRiLWluaXQuIFRoaXMgaXMgZGViaWFuIHBhY2thZ2UgcHJvYmVtLgoK
VGhlIHNlY29uZCBvbmUgd2FzIG15IHByb2JsZW0uIFRoZSBsaWJkYmktbXlzcWwgd2FzIG5vdCBp
bnN0YWxsZWQuIEJ1dApyZWZkYmQgZXhpc3Qgd2l0aG91dCBhbnkgbWVzc2FnZS4gSSB0aGluIHRo
aXMgaXMgdGhlIGJhc2ljIG1lc3NhZ2UKd2NoaWNoIHNob3VsZCBiZSBwcmludGVkIGFuZCBub3Qg
b25seSBhZnRlciBtYW51YWwgZXhlY3V0aW9uIHdpdGggc29tZQotbCBhbmQgLUwgb3B0aW9ucy4K
CkZpeGluZyB0aGlzIHRoZSByZWZkYi1pbml0IGZpbmlzaGVkLiBFeGNlcHQ6Cgo9PT0KQ3JlYXRl
IHJlZmRiIGFzIHJlZmVyZW5jZSBkYXRhYmFzZQoyMDk6cmVmZGIKOTk5OjAgY3JlYXRlZDoxIGZh
aWxlZAoKPT09CkdyYW50IHJlZmRiIGFjY2VzcyB0byB0aGUgcmVmZXJlbmNlIGRhdGFiYXNlIHJl
ZmRiCjIzNgoyMzc6cmVmZGJAbG9jYWxob3N0OnJlZmRiCjk5OToxIGFkZGVkOjAgZmFpbGVkCgo9
PT0KCgpzbywgc3RpbGwgaW52ZXN0aWdhdGluZyB3aGF0IHdlbnQgd3JvbmcuCgpKb3plZgoKCk9u
IDMvMjIvMDcsIE1hcmt1cyBIb2VuaWNrYSA8bWFya3VzLmhvZW5pY2thQG1ob2VuaWNrYS5kZT4g
d3JvdGU6Cj4gGyQsMSAuGyhCbxskLDEgLxsoQm8gd3JpdGVzOgo+ICA+IEhpIE1hcmt1cywKPiAg
PiBleHBsYW5hdGlvbiBpcyBzaW1wbGUuIFRoZSBzY3JpcHQgaXMgbG9va2lnbiBmb3IgdGhlIGZp
bGUgaW4KPiAgPiAvZXRjL3JlZmRiLyBkaXJlY3RvcnksIGJ1dCBmaWxlIGl0c2VsZiBpcyBsb2Nh
dGVkIGluCj4gID4gL3Vzci9zaGFyZS9yZWZkYi9ldGMvLgo+ICA+IFRoZSBzYW1lIHByb2JsZW0g
aXMgd2l0aCByZWZkYmFyYy5leGFtcGxlIGFuZCB2ZXJ5IGxpa2VseSB3aXRoIHNvbWUKPiAgPiBt
b3JlIGZpbGVzLiBTbyBzY3JpcHQgZG9lcyBub3QgbWF0Y2ggdGhlIGRhdGEgc3RydWN0dXJlLgo+
ICA+Cj4KPiByZWZkYi1pbml0IGlzIGNyZWF0ZWQgYXQgYnVpbGQgdGltZSBmcm9tIHJlZmRiLWlu
aXQuaW4uIFRoZSBNYWtlZmlsZQo+IHBlcmZvcm1zIGEgY291cGxlIG9mIHN0cmluZyBzdWJzdGl0
dXRpb25zLCBvbmUgb2YgdGhlbSBzZXRzIHRoZSBwcmVmaXgKPiBvZiB0aGUgc3lzdGVtIGNvbmZp
Z3VyYXRpb24gZGlyZWN0b3J5IGFwcHJvcHJpYXRlbHkuIExvb2tzIGxpa2UgdGhpcwo+IHdlbnQg
YXdyeSBzb21laG93IHdoZW4gdGhlIERlYmlhbiBwYWNrYWdlcyB3ZXJlIGJ1aWx0IChjYW4gYW55
b25lCj4gY29uZmlybSB0aGlzPykuIFlvdSd2ZSBnb3QgdHdvIG9wdGlvbnMgdGhlbjoKPgo+IC0g
cHJvY2VlZCB3aXRoIGEgbWFudWFsIHNldHVwIGFzIGRlc2NyaWJlZCBpbiB0aGUgaGFuZGJvb2sg
KGl0IGlzIG5vdAo+IHRoYXQgaGFyZCBhZnRlciBhbGwpCj4KPiAtIGJ1aWxkIFJlZkRCIGZyb20g
dGhlIHNvdXJjZXMgaW5zdGVhZCBvZiB1c2luZyB0aGUgcGFja2FnZQo+Cj4gVW5mb3J0dW5hdGVs
eSBJIGNhbid0IGRvIG11Y2ggYWJvdXQgYnJva2VuIERlYmlhbiBwYWNrYWdlcy4gT3VyCj4gcGFj
a2FnZSBtYWludGFpbmVyIHNlZW1zIHRvIGJlIG9uIGEgaGlhdHVzLCBhbmQgSSBkb24ndCBydW4g
RGViaWFuCj4gbXlzZWxmLgo+Cj4gID4gRmFpbGVkIHRvIGluc3RhbGwgb3IgdXBncmFkZSBtYWlu
IGRhdGFiYXNlCj4gID4KPgo+IFRoaXMgaXMgbW9zdCBsaWtlbHkgYSBjb25zZXF1ZW5jZSBvZiB0
aGUgbWlzc2luZyBjb25maWd1cmF0aW9uCj4gZmlsZS4gcmVmZGJkIGlzIHRoZW4gZm9yY2VkIHRv
IHVzZSBpdHMgZGVmYXVsdHMsIGFwcGFyZW50bHkgd2l0aG91dAo+IHN1Y2Nlc3MuIFRoaXMgcHJv
YmxlbSBzaG91bGQgZ28gYXdheSBhcyBzb29uIGFzIHlvdSBoYXZlIHN1aXRhYmxlCj4gY29uZmln
IGZpbGVzIGluIHBsYWNlLgo+Cj4gcmVnYXJkcywKPiBNYXJrdXMKPgo+IC0tCj4gTWFya3VzIEhv
ZW5pY2thCj4gbWFya3VzLmhvZW5pY2thQGNhdHMuZGUKPiAoU3BhbS1wcm90ZWN0ZWQgZW1haWw6
IHJlcGxhY2UgdGhlIHF1YWRydXBlZHMgd2l0aCAibWhvZW5pY2thIikKPiBodHRwOi8vd3d3Lm1o
b2VuaWNrYS5kZQo+Cj4K

Re: [Refdb-users] Upgrade failure

[Markus H. <mar...@mh...>]

Quoting Bruce Hayward <b.h...@le...>:


> So I have deleted both /usr/local/share/refdb/db/refdb and refs and
> attempted to use refdb-init while root. Below is output, it complains
> about lack of refdb.dump.sqlite
>

Thanks for the debug information. I'm afraid the refdb-init script =20
still contains a few bugs. It should not check for dump files (this is =20
now handled by refdbd), and the refdbd example config files were =20
inappropriately named in the script. I've fixed these bugs in SVN. =20
I've also attached the script template below for your convenience. =20
Please put the file into the scripts directory of the sources (on =20
FreeBSD, this is something like =20
/usr/ports/textproc/refdb/work/refdb-0.9.8/scripts) and run make && =20
make install in that directory. This should replace the installed =20
version of refdb-init.

Please let me know whether you get further with that version of the script.

regards,
Markus

--=20
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-users] =?iso-8859-1?q?could_not_open_main_database=3A_MySQ?= =?iso-8859-1?q?L-Password=09Issue?=

[Dominik R. <dre...@un...>]

> refdbd does not perform any specific checks. It simply passes the
> authentication information to libdbi, which in turn passes them to the
> requested driver. The driver uses (in your case) the libmysqlclient
> library provided by the MySQL database engine. I can only imagine that
> your libdbi driver is linked against an older version of the
> libmysqlclient library than what the database server expects.
> Rebuilding libdbi-drivers with the latest libmysqlclient library
> should fix this.

@David: Could it be that the debian libdbi-packages need to be updated to 
resolve this issue? I'm using:
libdbi-perl    1.53-1         Perl5 database interface by Tim Bunce
libdbi0        0.8.1-3        Database Independent Abstraction Layer for C


>
> I'm a bit puzzled that only one user runs into this problem. Do the
> other users have OLD_PASSWORDs by default, e.g. because their accounts
> are older?

Yes, the other accounts are just older.

regards,
Dominik 

>
> regards,
> Markus

-- 
Dominik Reusser

Re: [Refdb-users] Upgrade failure

[Bruce H. <b.h...@le...>]

Markus,
> Hi Bruce,
> 
> are you sure you have to? I've just checked the UPGRADING file, and it  
> reports no changes in the reference database schema since 0.9.6. I'd  
> expect that you can continue to access your databases. Are there  
> specific error messages that make you think so? Or did you  
> accidentally hose the databases?

Fear I was confused between my database (refs) and the main database
/usr/local/share/refdb/db/refdb yesterday. After "refdbd -a" didn't seem 
to go well I deleted my refs database and created a new one from a 
single .ris file.

refdbc:  selectdb refs
main database version is not supported

So I have deleted both /usr/local/share/refdb/db/refdb and refs and 
attempted to use refdb-init while root. Below is output, it complains 
about lack of refdb.dump.sqlite

mme-pc2132# refdb-init


This script will help you to set up a fresh RefDB installation.
WARNING: It is not yet designed to upgrade an existing installation.
In this case you'll have to backup your data before running this script
and to restore them after performing this installation.

I'll first ask a couple of questions and try to collect some information
from your system. If all checks are ok, you'll be asked for confirmation
before any changes are committed. Up to that point you can terminate this
script anytime by pressing Ctrl-c


===
Checking for the status of the application server control script.
You need to have the permissions to run this script in order to set up
RefDB with all the bells and whistles. If this test fails, you are most
likely not running as root.
refdbctl seems to be executable.

===
Please select the database engine you want to use.
Available are: mysql pgsql sqlite sqlite3

sqlite3

refdb.dump.sqlite is not readable or missing

refdbd-init.sh failed.
refdb-init is finished.

mme-pc2132# ll /usr/local/etc/refdb/
total 100
-r--r--r--  1 root  wheel   2.6K 11 Aug  2005 bib2riscgirc
-r--r--r--  1 root  wheel   2.6K 19 Mar 14:34 bib2riscgirc.example
-r--r--r--  1 root  wheel   2.6K 11 Aug  2005 bib2risrc
-r--r--r--  1 root  wheel   2.6K 19 Mar 14:34 bib2risrc.example
-r--r--r--  1 root  wheel   1.0K 11 Aug  2005 db2risrc
-r--r--r--  1 root  wheel   1.0K 19 Mar 14:34 db2risrc.example
-r--r--r--  1 root  wheel   1.6K 11 Aug  2005 marc2risrc
-r--r--r--  1 root  wheel   1.6K 19 Mar 14:34 marc2risrc.example
-r--r--r--  1 root  wheel   1.5K 11 Aug  2005 med2riscgirc
-r--r--r--  1 root  wheel   1.5K 19 Mar 14:34 med2riscgirc.example
-r--r--r--  1 root  wheel   1.7K 11 Aug  2005 med2risrc
-r--r--r--  1 root  wheel   1.9K 19 Mar 14:34 med2risrc.example
-r--r--r--  1 root  wheel   1.6K 11 Aug  2005 nmed2riscgirc
-r--r--r--  1 root  wheel   1.5K 11 Aug  2005 nmed2risrc
-r--r--r--  1 root  wheel   1.8K 11 Aug  2005 refdbarc
-r--r--r--  1 root  wheel   1.8K 19 Mar 14:34 refdbarc.example
-r--r--r--  1 root  wheel   2.3K 11 Aug  2005 refdbcgirc
-r--r--r--  1 root  wheel   2.3K 19 Mar 14:34 refdbcgirc.example
-r--r--r--  1 root  wheel   2.7K 11 Aug  2005 refdbcrc
-r--r--r--  1 root  wheel   2.8K 19 Mar 14:34 refdbcrc.example
-rw-r-----  1 root  wheel   3.3K 11 Aug  2005 refdbdrc
-r--r--r--  1 root  wheel   4.2K 19 Mar 14:34 refdbdrc.mysql.example
-r--r--r--  1 root  wheel   4.2K 19 Mar 14:34 refdbdrc.pgsql.example
-r--r--r--  1 root  wheel   4.2K 19 Mar 14:34 refdbdrc.sqlite.example
-r--r--r--  1 root  wheel   4.2K 19 Mar 14:34 refdbdrc.sqlite3.example
-r--r--r--  1 root  wheel   2.7K 11 Aug  2005 refdbibrc
-r--r--r--  1 root  wheel   2.9K 19 Mar 14:34 refdbibrc.example
-r--r--r--  1 root  wheel   3.6K 11 Aug  2005 refdbxmlrc
-r--r--r--  1 root  wheel   3.6K 19 Mar 14:34 refdbxmlrc.example

mme-pc2132# ls /usr/local/share/refdb/
css          declarations dtd          refdb.cat    styles       xsl
db           dsssl        examples     sql          www

mme-pc2132# ls /usr/local/share/refdb/sql/
empty.2.dump.mysql41 empty.2.dump.sqlite3 refdb.2.dump.mysql41 
refdb.2.dump.sqlite
empty.2.dump.pgsql   refdb.2.dump.mysql   refdb.2.dump.pgsql

mme-pc2132# ll /usr/local/share/refdb/sql/
total 156
-r--r--r--  1 root  wheel    10K 19 Mar 14:34 empty.2.dump.mysql41
-r--r--r--  1 root  wheel    26K 19 Mar 14:34 empty.2.dump.pgsql
-r--r--r--  1 root  wheel   3.8K 19 Mar 14:34 empty.2.dump.sqlite3
-r--r--r--  1 root  wheel    31K 19 Mar 14:34 refdb.2.dump.mysql
-r--r--r--  1 root  wheel    20K 19 Mar 14:34 refdb.2.dump.mysql41
-r--r--r--  1 root  wheel    28K 19 Mar 14:34 refdb.2.dump.pgsql
-r--r--r--  1 root  wheel    28K 19 Mar 14:34 refdb.2.dump.sqlite

Re: [Refdb-users] RefDB web page..

[Markus H. <mar...@mh...>]

$,1 .(Bo$,1 /(Bo writes:
 > Hi Markus,
 > explanation is simple. The script is lookign for the file in
 > /etc/refdb/ directory, but file itself is located in
 > /usr/share/refdb/etc/.
 > The same problem is with refdbarc.example and very likely with some
 > more files. So script does not match the data structure.
 > 

refdb-init is created at build time from refdb-init.in. The Makefile
performs a couple of string substitutions, one of them sets the prefix
of the system configuration directory appropriately. Looks like this
went awry somehow when the Debian packages were built (can anyone
confirm this?). You've got two options then:

- proceed with a manual setup as described in the handbook (it is not
that hard after all)

- build RefDB from the sources instead of using the package

Unfortunately I can't do much about broken Debian packages. Our
package maintainer seems to be on a hiatus, and I don't run Debian
myself.
 
 > Failed to install or upgrade main database
 > 

This is most likely a consequence of the missing configuration
file. refdbd is then forced to use its defaults, apparently without
success. This problem should go away as soon as you have suitable
config files in place.

regards,
Markus

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