<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/refdb/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/refdb/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/refdb/feature-requests/</id><updated>2010-05-11T19:26:53Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>"addword" - make new reserved words available</title><link href="https://sourceforge.net/p/refdb/feature-requests/46/" rel="alternate"/><published>2010-05-11T19:26:53Z</published><updated>2010-05-11T19:26:53Z</updated><author><name>akusmin</name><uri>https://sourceforge.net/u/akusmin/</uri></author><id>https://sourceforge.net05724bda4cff9c62c57b55a1a71eeb65176cda46</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello!&lt;br /&gt;
I had to add some reserved words using the addword command. &lt;br /&gt;
The problem: after I added  new reserved words (e.g. Solid, State, and Ionics), even after I used the "updateref" commando,&lt;br /&gt;
the latex  bibliography is still created with "Solid.State.Ionics" as journal abbreviation.&lt;br /&gt;
The only solution I found so far is to delete the database and recreate it. &lt;/p&gt;
&lt;p&gt;Request/Question Could you add / Is there any simpler way to take into account new reserved words? &lt;br /&gt;
If there is already such way, could add this information to the manual?&lt;/p&gt;
&lt;p&gt;Thank you!&lt;/p&gt;
&lt;p&gt;P.S.&lt;br /&gt;
please consider adding the following words into the default list (some of them may be in this list of the development version I guess)&lt;/p&gt;
&lt;p&gt;MACROMOLECULES&lt;br /&gt;
MATTER&lt;br /&gt;
SOLID&lt;br /&gt;
STATE&lt;br /&gt;
IONICS&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Get IDs fast</title><link href="https://sourceforge.net/p/refdb/feature-requests/45/" rel="alternate"/><published>2009-10-03T14:36:37Z</published><updated>2009-10-03T14:36:37Z</updated><author><name>Torsten Bronger</name><uri>https://sourceforge.net/u/bronger/</uri></author><id>https://sourceforge.netaed8eaabcb29dbf94bb94908309fed2213436dce</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, it takes 40ms per reference to get the ID of a found reference:&lt;/p&gt;
&lt;p&gt;$ time refdbc -u refdb -w Sonne -d biblio -C getref -s ID -t ris ":ID:&amp;gt;0" &amp;gt; /dev/null&lt;br /&gt;
999:96 retrieved:0 failed&lt;/p&gt;
&lt;p&gt;real    0m4.026s&lt;br /&gt;
user    0m0.000s&lt;br /&gt;
sys     0m0.004s&lt;/p&gt;
&lt;p&gt;This is problematic for a web frontend because even if you work with aggressive caching, you have to know at least the IDs of found references.&lt;/p&gt;
&lt;p&gt;Therefore, I request to optimise the ID-only request.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>addref should return the IDs</title><link href="https://sourceforge.net/p/refdb/feature-requests/44/" rel="alternate"/><published>2009-06-12T10:54:11Z</published><updated>2009-06-12T10:54:11Z</updated><author><name>Torsten Bronger</name><uri>https://sourceforge.net/u/bronger/</uri></author><id>https://sourceforge.net52c61e9e6ae9470e9693e042f83666f5158e03b9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;addref returns the citation key in the result summary.  However, some places of RefDB (at least deleteref and getref with RIS-ID-only output) work with IDs only.  Therefore, please add the IDs in the result summary, too.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>enigma encryption optional</title><link href="https://sourceforge.net/p/refdb/feature-requests/43/" rel="alternate"/><published>2009-04-28T17:42:25Z</published><updated>2009-04-28T17:42:25Z</updated><author><name>Torsten Bronger</name><uri>https://sourceforge.net/u/bronger/</uri></author><id>https://sourceforge.net92a420c2dbe017c2bc714d5a84e13d19f5ee3f1e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Please make encryption of the password optional.&lt;/p&gt;
&lt;p&gt;Rationale: Often (if not mostly), RefDB is connected from localhost only, therefore, there is no transmission over an unstrusted network.  Since the algorithm is non-standard, you have to implement it for every client implementation.  Unless of course you use eenc which is an unnecessary dependency for your client package.  If it wasn't for the sake of compatibility, I'd even request to remove it entirely:  Tunneling through ssh or using openssl is the way to go, and easy enough.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add citations as citekey</title><link href="https://sourceforge.net/p/refdb/feature-requests/42/" rel="alternate"/><published>2007-11-29T16:04:31Z</published><updated>2007-11-29T16:04:31Z</updated><author><name>Markus Hoenicka</name><uri>https://sourceforge.net/u/mhoenicka/</uri></author><id>https://sourceforge.net5b4d0dc540855fbfb0a24c394f8a989f6fb5093d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Add new commands and menu entries which allow to insert "raw" citations, i.e. just the citation key as a string, into documents not specifically supported by refdb-mode.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>auto-save feature</title><link href="https://sourceforge.net/p/refdb/feature-requests/41/" rel="alternate"/><published>2007-11-22T17:43:15Z</published><updated>2007-11-22T17:43:15Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.nete988ef6e7d15341b7332c15acdc4b45637491db5</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would also be very handy to have an auto-save feature that would back up your entries every couple of minutes so that you would never lose the work you've done on an entry.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>show all references feature</title><link href="https://sourceforge.net/p/refdb/feature-requests/40/" rel="alternate"/><published>2007-11-22T17:41:50Z</published><updated>2007-11-22T17:41:50Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net083f4c9a4e996b52f6829d8f57b38fc8d4d1ebba</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be very useful to have a 'show all references' feature to be able to look at the full list of references in your bibliography.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>config file for runbib</title><link href="https://sourceforge.net/p/refdb/feature-requests/39/" rel="alternate"/><published>2007-08-06T07:17:50Z</published><updated>2007-08-06T07:17:50Z</updated><author><name>Markus Hoenicka</name><uri>https://sourceforge.net/u/mhoenicka/</uri></author><id>https://sourceforge.net520cd429752041cb9e5a3a6fe08d6d830906cb83</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Add a config file for runbib to permanently set command line arguments for jade etc.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Please improve bibliography sorting</title><link href="https://sourceforge.net/p/refdb/feature-requests/38/" rel="alternate"/><published>2007-04-24T14:21:08Z</published><updated>2007-04-24T14:21:08Z</updated><author><name>Jeremy Malcolm</name><uri>https://sourceforge.net/u/qirtaiba/</uri></author><id>https://sourceforge.netc5f369142f636feda602b51843688983c64a94cf</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;As discussed on the mailing list, please improve sorting of the bibliography so that a-z and A-Z are contiguous, and preferably so that if there is no primary author, it will sort on the secondary author instead.&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Database name configuration</title><link href="https://sourceforge.net/p/refdb/feature-requests/37/" rel="alternate"/><published>2006-11-27T15:18:31Z</published><updated>2006-11-27T15:18:31Z</updated><author><name>steletch</name><uri>https://sourceforge.net/u/steletch/</uri></author><id>https://sourceforge.net586439175c667c366c2d4147b834899c855af5d8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Actually, it is possible to adjust the database name via passing the name to the configure script:&lt;/p&gt;
&lt;p&gt;./configure --with-main-db=&amp;lt;name&amp;gt;&lt;/p&gt;
&lt;p&gt;That's quite a improvement, but it'll be nice to be fully independant of the building process, especially while a user will get the refdb package in a pre-built form (be it a rpm, deb, binary, ...).&lt;/p&gt;
&lt;p&gt;Could the database name be configurable please ?&lt;/p&gt;
&lt;p&gt;I could imagine a situation where you have two different databases or only one. In this situation, one could easily use both variable names:&lt;/p&gt;
&lt;p&gt;styles-db-name=&amp;lt;db1&amp;gt; (default refdb)&lt;br /&gt;
references-db-name=&amp;lt;db2&amp;gt; (default ?)&lt;/p&gt;
&lt;p&gt;When you have only one db available, then db1==db2&lt;/p&gt;
&lt;p&gt;Thanks for the job :-)&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>