You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(14) |
Dec
(23) |
2005 |
Jan
(8) |
Feb
(11) |
Mar
(8) |
Apr
(4) |
May
(16) |
Jun
(13) |
Jul
(12) |
Aug
(14) |
Sep
(11) |
Oct
(11) |
Nov
(15) |
Dec
(7) |
2006 |
Jan
(16) |
Feb
(35) |
Mar
(26) |
Apr
(7) |
May
(10) |
Jun
(9) |
Jul
(10) |
Aug
(3) |
Sep
(13) |
Oct
(7) |
Nov
(18) |
Dec
(2) |
2007 |
Jan
(1) |
Feb
(11) |
Mar
|
Apr
(10) |
May
|
Jun
(2) |
Jul
(1) |
Aug
(56) |
Sep
(32) |
Oct
(27) |
Nov
(78) |
Dec
(23) |
2008 |
Jan
(12) |
Feb
(21) |
Mar
(29) |
Apr
(9) |
May
(12) |
Jun
(14) |
Jul
(13) |
Aug
(13) |
Sep
(19) |
Oct
(27) |
Nov
(19) |
Dec
(8) |
2009 |
Jan
(10) |
Feb
(32) |
Mar
(24) |
Apr
(10) |
May
(35) |
Jun
(29) |
Jul
(42) |
Aug
(51) |
Sep
(21) |
Oct
(40) |
Nov
(53) |
Dec
(37) |
2010 |
Jan
(22) |
Feb
(54) |
Mar
(51) |
Apr
(28) |
May
(21) |
Jun
(10) |
Jul
(16) |
Aug
(15) |
Sep
(16) |
Oct
(12) |
Nov
(16) |
Dec
(29) |
2011 |
Jan
(16) |
Feb
(28) |
Mar
(18) |
Apr
(32) |
May
(31) |
Jun
(28) |
Jul
(52) |
Aug
(51) |
Sep
(29) |
Oct
(38) |
Nov
(27) |
Dec
(22) |
2012 |
Jan
(18) |
Feb
(29) |
Mar
(50) |
Apr
(43) |
May
(28) |
Jun
(34) |
Jul
(26) |
Aug
(11) |
Sep
(27) |
Oct
(33) |
Nov
(101) |
Dec
(17) |
2013 |
Jan
(22) |
Feb
(57) |
Mar
(29) |
Apr
(22) |
May
(15) |
Jun
(17) |
Jul
(14) |
Aug
(13) |
Sep
(33) |
Oct
(25) |
Nov
(13) |
Dec
(12) |
2014 |
Jan
(19) |
Feb
(6) |
Mar
(24) |
Apr
(30) |
May
(43) |
Jun
(22) |
Jul
(15) |
Aug
(19) |
Sep
(27) |
Oct
(10) |
Nov
(17) |
Dec
(6) |
2015 |
Jan
(18) |
Feb
(6) |
Mar
(20) |
Apr
(9) |
May
(15) |
Jun
(17) |
Jul
(6) |
Aug
(16) |
Sep
(16) |
Oct
(14) |
Nov
(50) |
Dec
(42) |
2016 |
Jan
(60) |
Feb
(45) |
Mar
(12) |
Apr
(56) |
May
(18) |
Jun
(16) |
Jul
(1) |
Aug
(4) |
Sep
|
Oct
(3) |
Nov
(3) |
Dec
|
2017 |
Jan
|
Feb
(3) |
Mar
|
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
(9) |
Oct
(10) |
Nov
|
Dec
|
2020 |
Jan
|
Feb
(8) |
Mar
(8) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
From: Oliver K. <kop...@gm...> - 2016-08-26 13:16:14
|
Dear Ebo, The mailinglist is closing down and we recommend to use http://discourse.jabref.org/ Regarding your concrete point, I did not find any issue at https://github.com/jabref/jabref/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20shorttile Could you please file an issue at https://github.com/JabRef/jabref/issues so that we can keep track? Reason for that: We have so many issues to solve and try to prioritize them. When an issue is not filed at https://github.com/JabRef/jabref/issues, it does not get into our prioritization queue and the likely hood that it is solved is very low - unfortunately. Cheers, Oliver 2016-07-25 19:37 GMT+02:00 EBo <eb...@us...>: > I thought I would see if the short-title bug had been fixed in version > 3.5 or the 3.6 snapshot. Unfortunately it appears to still be broken. > > My bibkey generator is "[auth][year:(unk)][shorttitle:abbr:upper]" it > worked as expected up through JabRef-2.10b2, but was broken after the > final release. > > > For the example: > > Abarbanel, H. D.; Rulkov, N. F. & Sushchik, M. M. Generalized > synchronization of chaos: The auxiliary system approach Physical Review > E, APS, 1996, 53, 4528 > > The documentation "shorttitle" should use the first three words of the > title, and generates a bibkey of: > > Abarbanel1996Generalizedsynchronizationchaos > > Further adding "abbr" should abbreviate the first three words, but > gives > > Abarbanel1996G > > which implies that "abbr" is abbreviating the concatenated string > "Generalizedsynchronizationchaos". If I run "[auth][year:(unk)][abbr]" > it returns: > > Abarbanel1996 > > which imples that "abbr" is broken. I would have expected > > Abarbanel1996GsocTasa > > or something similar (since there is a ':' in the name, but I filter > that out). > > Hope this helps, but for now I will continue to recode all my keys by > hand to keep consistency. If anyone can fix this, that would be great. > > Thanks and best regards, > > EBo -- > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity planning > reports.http://sdm.link/zohodev2dev > _______________________________________________ > Jabref-users mailing list > Jab...@li... > https://lists.sourceforge.net/lists/listinfo/jabref-users |
From: Oliver K. <kop...@gm...> - 2016-08-26 13:11:22
|
Dear Haines, meta comment: We moved to http://discourse.jabref.org/ for discussions. The grouping issue you describe is https://github.com/JabRef/jabref/issues/1495, isn't it? The issue on github is https://github.com/JabRef/jabref/issues/1495 - and I just saw that you reported it. We are working on a fix. Since we have to earn our money at other projects, the fix won't be as fast as in commercial projects. Sorry for the delay and any inconvenience caused! Cheers, Oliver 2016-08-26 14:18 GMT+02:00 Haines Brown <ha...@hi...>: > JabRef 3.6 is now out. I don't find sufficient information about the > differences in new versions, what is added, what is fixed. > > In particular, JabRef version 3.1 or 3.2 (I think) introduced what was > for me a disastrous change in how groups are attached to database > entries. In particular, my database of about 13.000 entries was set up > under the old system which allowed duplication of group names. > Here is a fictional example: > > fishing > ..saltwater -> article on sport fishing > swimming > ..saltwater -> article on beaches > corrosion > ..saltwater -> article on automobile maintenance > > Where I to use the new system that came in with JabRef 3.1, the group > linkage information would be corrupted and with it the organization of > all my data. Saltwater would conflate articles on fishing, swimming and > corrosion. > > There was discussion of this issue that suggested the problem could be > fixed so that links from entries could differentiate among groups having > the same name. Was a change incorporated into the new JabRef that would > solve the problem? > > Haines Brown > > ------------------------------------------------------------------------------ > _______________________________________________ > Jabref-users mailing list > Jab...@li... > https://lists.sourceforge.net/lists/listinfo/jabref-users |
From: Haines B. <ha...@hi...> - 2016-08-26 12:43:32
|
JabRef 3.6 is now out. I don't find sufficient information about the differences in new versions, what is added, what is fixed. In particular, JabRef version 3.1 or 3.2 (I think) introduced what was for me a disastrous change in how groups are attached to database entries. In particular, my database of about 13.000 entries was set up under the old system which allowed duplication of group names. Here is a fictional example: fishing ..saltwater -> article on sport fishing swimming ..saltwater -> article on beaches corrosion ..saltwater -> article on automobile maintenance Where I to use the new system that came in with JabRef 3.1, the group linkage information would be corrupted and with it the organization of all my data. Saltwater would conflate articles on fishing, swimming and corrosion. There was discussion of this issue that suggested the problem could be fixed so that links from entries could differentiate among groups having the same name. Was a change incorporated into the new JabRef that would solve the problem? Haines Brown |
From: EBo <eb...@us...> - 2016-07-25 18:10:11
|
I thought I would see if the short-title bug had been fixed in version 3.5 or the 3.6 snapshot. Unfortunately it appears to still be broken. My bibkey generator is "[auth][year:(unk)][shorttitle:abbr:upper]" it worked as expected up through JabRef-2.10b2, but was broken after the final release. For the example: Abarbanel, H. D.; Rulkov, N. F. & Sushchik, M. M. Generalized synchronization of chaos: The auxiliary system approach Physical Review E, APS, 1996, 53, 4528 The documentation "shorttitle" should use the first three words of the title, and generates a bibkey of: Abarbanel1996Generalizedsynchronizationchaos Further adding "abbr" should abbreviate the first three words, but gives Abarbanel1996G which implies that "abbr" is abbreviating the concatenated string "Generalizedsynchronizationchaos". If I run "[auth][year:(unk)][abbr]" it returns: Abarbanel1996 which imples that "abbr" is broken. I would have expected Abarbanel1996GsocTasa or something similar (since there is a ':' in the name, but I filter that out). Hope this helps, but for now I will continue to recode all my keys by hand to keep consistency. If anyone can fix this, that would be great. Thanks and best regards, EBo -- |
From: Matthias G. <mat...@un...> - 2016-06-27 07:46:49
|
Dear mailing list users, we, the development team of JabRef just opened a new discussion and support platform for JabRef. You can find it by now in the top navigation bar on JabRef.org or directly here: http://discourse.jabref.org The main reasons for introducing this forum are: - Foster the communication between the large user base and the developers of JabRef, creation of an active "JabRef community" - Provide an easier to use, searchable, more modern way to give feedback and request help - Provide a better place for feature and enhancement discussions by a dedicated category for such topics: http://discourse.jabref.org/c/features - Reduce the number of created issues at the GitHub tracker - only real bugs and work-in-progress feature requests should be handled there During the last years we started to move away from sourceforge.net (for various reasons): The source code and issues are now managed at GitHub, downloads are handled by FossHub and we are using our own domain JabRef.org for hosting the website - only this mailing list is still organized at sourceforge.net. With the new forum we now provide an easy to use platform to ask questions (and hopefully to get answers) from the JabRef community. Thus, we decided to officially discontinue the support on the mailing list. We'll leave the list open for some time - but the official communication channels for the future will be the GitHub issue tracker (for bugs - see: https://github.com/JabRef/jabref/issues ) and the new discourse forum (for all other questions, feature requests and feedback). We are aware that a lot of you guys on the mailing list like this way of communication, with the ability to sort, search and work offline in the mail client of your choice. The good news is: Even the new forum is generally web-based, it is still possible to use it just like a mailinglist - with even some more advanced filtering mechanisms. If you are interested in the usage of the new forum in the so called "mailing-list mode" just check out the guide we created for you: http://discourse.jabref.org/t/quick-start-guide-for-former-mailing-list-users/31 We hope you will follow us to the new forum and contribute there with your valuable knowledge with has already helped lots of users here in the list! If you have any trouble with signing up or configuring the forum just contact me! Kind regards Matthias - in the name of the JabRef developers -- Matthias Geiger Lehrstuhl für Praktische Informatik Distributed Systems Group (DSG) Fakultät für Wirtschaftsinformatik und Angewandte Informatik Otto-Friedrich-Universität Bamberg An der Weberei 5 96047 Bamberg Raum: WE5/03.091 Tel.: +49 951 863-2810 |
From: Haines B. <ha...@hi...> - 2016-06-13 09:01:03
|
On Sun, Jun 12, 2016 at 04:31:54PM +0200, Tob...@gm... wrote: > Dear Haines, > > I'm sorry for the problems you have with the way Jabref handles groups > in the new version. Let me explain what happened: Previously, the > group membership was stored at the end of the file in one of these > Jabref comments. This behaviour had some disadvantages, so we changed > it. Now Jabref rembers the group information in the bibtex entry > itself (BibEntry). So your entries now have a groups field (have a > look at the bibtex source), where the names of the static groups are > saved. Because only the names of the groups are stored in this new > field, JabRef can no longer differentiate between groups with the same > name. This might be a bit inconvienent, but you can fix it easily by > giving the groups different names and then manually correcting the > assignments. > > I hope this helps for now. If you still experience problems, please > post them on github. https://github.com/JabRef/jabref/issues Best, > Tobias I did as you suggested by submitting a problem to GitHub. However, I also would like to expand on my point here because people should be alerted to the fact that the shift from placing groups in a database jabref-meta: groupstree to a groups (BibEntry) section in particular entries undoubtedly brought with it a significant loss of information for many others besides myself. They may not yet be aware of it yet. The groups tree was designed to be hierarchical, and surely there are many besides myself who use the same group names at different places in a database's tree. I fail to see why this information was simply destroyed quietly without offering a way to avoid it. For example, suppose a hierarchy of groups like this where the group "a" appears twice: 1 A a 2 B a 3 C d The hierarchy Could have been preserved by distinguishing a comma-separated and semi-colon separated list. For example, Groups = {1,A,a; 3,C,d}, Would select the first instance of "a" in the tree and not the second. My loss of information was so extensive I had to revert to JabRef 2.10 and recover the group trees from a recent backup. Haines Brown |
From: <jos...@ch...> - 2016-06-13 05:30:12
|
That means in the new version of JabRef all groups are dynamic? All the best Josef > > Tob...@gm... hat am 12. Juni 2016 um 16:31 geschrieben: > > > Dear Haines, > > I'm sorry for the problems you have with the way Jabref handles groups in > the new version. Let me explain what happened: > Previously, the group membership was stored at the end of the file in one > of these Jabref comments. This behaviour had some disadvantages, so we changed > it. Now Jabref rembers the group information in the bibtex entry itself > (BibEntry). So your entries now have a groups field (have a look at the bibtex > source), where the names of the static groups are saved. > Because only the names of the groups are stored in this new field, JabRef > can no longer differentiate between groups with the same name. This might be a > bit inconvienent, but you can fix it easily by giving the groups different > names and then manually correcting the assignments. > > I hope this helps for now. If you still experience problems, please post > them on github. https://github.com/JabRef/jabref/issues > Best, Tobias > > |
From: Haines B. <ha...@hi...> - 2016-06-12 17:23:49
|
On Sun, Jun 12, 2016 at 04:31:54PM +0200, Tob...@gm... wrote: > Dear Haines, > > I'm sorry for the problems you have with the way Jabref handles groups > in the new version. Let me explain what happened: Previously, the > group membership was stored at the end of the file in one of these > Jabref comments. This behaviour had some disadvantages, so we changed > it. Now Jabref rembers the group information in the bibtex entry > itself (BibEntry). So your entries now have a groups field (have a > look at the bibtex source), where the names of the static groups are > saved. > > Because only the names of the groups are stored in this new field, > JabRef can no longer differentiate between groups with the same > name. This might be a bit inconvienent, but you can fix it easily by > giving the groups different names and then manually correcting the > assignments. > > I hope this helps for now. If you still experience problems, please > post them on github. https://github.com/JabRef/jabref/issues Best, > Tobias Thanks, Tobias, that was a big help. The only problem I have is that when I change the name of a group and associate an entry to it, the other groups with same name are highlighted. When I try to remove these others from being associated with the entry, the original association is also lost. I'll bring this up in github. Haines Brown > > -----Ursprüngliche Nachricht----- > Gesendet: Sunday, 12 June 2016 um 15:45:13 Uhr > Von: jab...@li... > An: jab...@li... > Betreff: Jabref-users Digest, Vol 115, Issue 2 > Send Jabref-users mailing list submissions to > jab...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/jabref-users > or, via email, send a message with subject or body 'help' to > jab...@li... > > You can reach the person managing the list at > jab...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Jabref-users digest..." > > > Today's Topics: > > 1. Re: Groups using not possible (Bernhard Kleine) > 2. Re: Groups using not possible (Bernhard Kleine) > 3. Re: Groups using not possible (Haines Brown) > 4. Re: Groups using not possible (Bernhard Kleine) > 5. Re: Groups using not possible (Haines Brown) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 12 Jun 2016 11:44:07 +0200 > From: Bernhard Kleine <ber...@gm...> > Subject: Re: [Jabref-users] Groups using not possible > To: jab...@li... > Message-ID: <4c3...@gm...> > Content-Type: text/plain; charset="windows-1252" > > Am 10.06.2016 um 07:13 schrieb Bernhard Kleine: > > > I started using groups with the previous jabref version. I have some > > 1300 bibentries and groups are as large as 140 or as small as 3 entries. > > > > When I want to display groups, however, I tried en vain to see the > > selected entries, mostly jabref adds the entry selected to a groups when > > clicking on a group. This is not the behaviour I am used to. How to > > display a group and not add or delete entries from group without the > > risk to do the wrong? It is not obvious. > > > > Bernhard > I looked in detail: I had selected a group of 13 entries. I added the > pdf location of one of this papers to jabref in the "allgemein > (General?)" dialogue of the edit article form. When I finished adding > the pdf location, the selection of the 13 papers in the group got lost. > Clicking on the group in the Group form did not bring up the selection > again, but deleted the selected entry from the group. Re-clicking added > it again, but still the selection was gone. I do not find a simple way > to select a group when a paper is selected in that group. > > Bernhard > > spitzhalde9 > > 79853 lenzkirch > > ber...@gm... > > www.b-kleine.com, www.urseetal.net > > - > > thunderbird mit enigmail > > GPG schl?ssel: D5257409 > > fingerprint: > > 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09 > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 819 bytes > Desc: OpenPGP digital signature > > ------------------------------ > > Message: 2 > Date: Sun, 12 Jun 2016 13:05:03 +0200 > From: Bernhard Kleine <ber...@gm...> > Subject: Re: [Jabref-users] Groups using not possible > To: jab...@li... > Message-ID: <ccd...@gm...> > Content-Type: text/plain; charset="windows-1252" > > Am 12.06.2016 um 11:44 schrieb Bernhard Kleine: > > Am 10.06.2016 um 07:13 schrieb Bernhard Kleine: > > > >> I started using groups with the previous jabref version. I have some > >> 1300 bibentries and groups are as large as 140 or as small as 3 entries. > >> > >> When I want to display groups, however, I tried en vain to see the > >> selected entries, mostly jabref adds the entry selected to a groups when > >> clicking on a group. This is not the behaviour I am used to. How to > >> display a group and not add or delete entries from group without the > >> risk to do the wrong? It is not obvious. > >> > >> Bernhard > > I looked in detail: I had selected a group of 13 entries. I added the > > pdf location of one of this papers to jabref in the "allgemein > > (General?)" dialogue of the edit article form. When I finished adding > > the pdf location, the selection of the 13 papers in the group got lost. > > Clicking on the group in the Group form did not bring up the selection > > again, but deleted the selected entry from the group. Re-clicking added > > it again, but still the selection was gone. I do not find a simple way > > to select a group when a paper is selected in that group. > > > > Bernhard > Unselecting "gruppenzugeh?rigkeit bearbeiten (manage entries in a > group?)" did allow me again to select groups. It is not mentioned in the > German Manual. > Bernhard > > -- > -- > spitzhalde9 > 79853 lenzkirch > ber...@gm... > www.b-kleine.com, www.urseetal.net > - > thunderbird mit enigmail > GPG schl?ssel: D5257409 > fingerprint: > 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09 > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 819 bytes > Desc: OpenPGP digital signature > > ------------------------------ > > Message: 3 > Date: Sun, 12 Jun 2016 08:18:30 -0400 > From: Haines Brown <ha...@hi...> > Subject: Re: [Jabref-users] Groups using not possible > To: jab...@li... > Message-ID: <201...@en...> > Content-Type: text/plain; charset=us-ascii > > I've complained several times in another thread, so far no response, > that JabRef 3.4 destroyed the @Comment{jabref-meta: groupstree: section > of my .bib databases. The group tree is present, but has lost all > keywords. > > I don't see how this could have happened through my blundering. I can > recover that section from all my databases from a backup when still > running JabRef 9.10 two weeks ago. I did this with a database, but a > major problem remains. If I create a new group, it is not added to the > groupstree, but is recorded somewhere else. Also, creating a link from > an entry to a group creates a link to all groups with the same name. > > Please!!! Someone tell me what's going on. Has a new group mechanism > been created? Where is that information being stored? Was it supposed to > recover groupstree data from the .bib databases? > > I'll have to create links from entries to groups by entering the > information into the databases by hand, but I worry that JabRef 3.4 will > again destroy that information. > > Haines Brown > > > > > > > ------------------------------ > > Message: 4 > Date: Sun, 12 Jun 2016 14:22:30 +0200 > From: Bernhard Kleine <ber...@gm...> > Subject: Re: [Jabref-users] Groups using not possible > To: jab...@li... > Message-ID: <589...@gm...> > Content-Type: text/plain; charset="windows-1252" > > Am 12.06.2016 um 14:18 schrieb Haines Brown: > > I've complained several times in another thread, so far no response, > > that JabRef 3.4 destroyed the @Comment{jabref-meta: groupstree: section > > of my .bib databases. The group tree is present, but has lost all > > keywords. > > > > I don't see how this could have happened through my blundering. I can > > recover that section from all my databases from a backup when still > > running JabRef 9.10 two weeks ago. I did this with a database, but a > > major problem remains. If I create a new group, it is not added to the > > groupstree, but is recorded somewhere else. Also, creating a link from > > an entry to a group creates a link to all groups with the same name. > > > > Please!!! Someone tell me what's going on. Has a new group mechanism > > been created? Where is that information being stored? Was it supposed to > > recover groupstree data from the .bib databases? > > > > I'll have to create links from entries to groups by entering the > > information into the databases by hand, but I worry that JabRef 3.4 will > > again destroy that information. > > > > Haines Brown > I know that there were changes in the group function. But I do not know > whether your problem is related. My groups at least were maintained when > I updated jabref to 3.4. > Regards > Bernhard > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 819 bytes > Desc: OpenPGP digital signature > > ------------------------------ > > Message: 5 > Date: Sun, 12 Jun 2016 09:45:02 -0400 > From: Haines Brown <ha...@hi...> > Subject: Re: [Jabref-users] Groups using not possible > To: jab...@li... > Message-ID: <201...@en...> > Content-Type: text/plain; charset=us-ascii > > On Sun, Jun 12, 2016 at 02:22:30PM +0200, Bernhard Kleine wrote: > > Am 12.06.2016 um 14:18 schrieb Haines Brown: > > > I've complained several times in another thread, so far no response, > > > that JabRef 3.4 destroyed the @Comment{jabref-meta: groupstree: section > > > of my .bib databases. The group tree is present, but has lost all > > > keywords. > > > > > > I don't see how this could have happened through my blundering. I can > > > recover that section from all my databases from a backup when still > > > running JabRef 9.10 two weeks ago. I did this with a database, but a > > > major problem remains. If I create a new group, it is not added to the > > > groupstree, but is recorded somewhere else. Also, creating a link from > > > an entry to a group creates a link to all groups with the same name. > > > > > > Please!!! Someone tell me what's going on. Has a new group mechanism > > > been created? Where is that information being stored? Was it supposed to > > > recover groupstree data from the .bib databases? > > > > > > I'll have to create links from entries to groups by entering the > > > information into the databases by hand, but I worry that JabRef 3.4 will > > > again destroy that information. > > > > > > Haines Brown > > > I know that there were changes in the group function. But I do not know > > whether your problem is related. My groups at least were maintained when > > I updated jabref to 3.4. > > Regards > > Bernhard > > I really would like to know what this new groups mechanism is. CHANGELOG > suggests that with JabRef 3.3 the data held in the jabref-meta: > groupstree: sections of bibliographic databases was transferred to > something called "BibEntry". I find it succeeded for some databases, but > not all. > > I see that JabRef now generates a host of files under > /usr/local/share/JabRef/jabref-master/... and apparently overwriting > them are user's preferences in ~/Xjabref-master/.... Unfortunately I was > unable to locate a BibEntry there. There are MSBibEntry.java files, but > these hold no specific group information. > > So my questions are: > > a) What and where is this "BibEntry"? It apparently is not the name of a > file. > > b) Was it intended that this BibEntry preserve the original groups > hierarchy? It does not seem to distinguish groups organized in > hierarchic fashion. Even where I've restored the group tree > functionality, groups with same name but situated in different places in > the tree are not distinguished. Is BibEntry just a flat file database? > > c) How could all group data be lost when I moved up from JabRef 9.10 to > JabRef 3.4? Is there something I should have done to prevent it? While I > can recover old group hierarchies data, I don't want to loose recent > additions again. > > Haines Brown > > > > ------------------------------ > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > > ------------------------------ > > _______________________________________________ > Jabref-users mailing list > Jab...@li... > https://lists.sourceforge.net/lists/listinfo/jabref-users > > > End of Jabref-users Digest, Vol 115, Issue 2 > ******************************************** |
From: <Tob...@gm...> - 2016-06-12 14:32:13
|
Dear Haines, I'm sorry for the problems you have with the way Jabref handles groups in the new version. Let me explain what happened: Previously, the group membership was stored at the end of the file in one of these Jabref comments. This behaviour had some disadvantages, so we changed it. Now Jabref rembers the group information in the bibtex entry itself (BibEntry). So your entries now have a groups field (have a look at the bibtex source), where the names of the static groups are saved. Because only the names of the groups are stored in this new field, JabRef can no longer differentiate between groups with the same name. This might be a bit inconvienent, but you can fix it easily by giving the groups different names and then manually correcting the assignments. I hope this helps for now. If you still experience problems, please post them on github. https://github.com/JabRef/jabref/issues Best, Tobias -----Ursprüngliche Nachricht----- Gesendet: Sunday, 12 June 2016 um 15:45:13 Uhr Von: jab...@li... An: jab...@li... Betreff: Jabref-users Digest, Vol 115, Issue 2 Send Jabref-users mailing list submissions to jab...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/jabref-users or, via email, send a message with subject or body 'help' to jab...@li... You can reach the person managing the list at jab...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Jabref-users digest..." Today's Topics: 1. Re: Groups using not possible (Bernhard Kleine) 2. Re: Groups using not possible (Bernhard Kleine) 3. Re: Groups using not possible (Haines Brown) 4. Re: Groups using not possible (Bernhard Kleine) 5. Re: Groups using not possible (Haines Brown) ---------------------------------------------------------------------- Message: 1 Date: Sun, 12 Jun 2016 11:44:07 +0200 From: Bernhard Kleine <ber...@gm...> Subject: Re: [Jabref-users] Groups using not possible To: jab...@li... Message-ID: <4c3...@gm...> Content-Type: text/plain; charset="windows-1252" Am 10.06.2016 um 07:13 schrieb Bernhard Kleine: > I started using groups with the previous jabref version. I have some > 1300 bibentries and groups are as large as 140 or as small as 3 entries. > > When I want to display groups, however, I tried en vain to see the > selected entries, mostly jabref adds the entry selected to a groups when > clicking on a group. This is not the behaviour I am used to. How to > display a group and not add or delete entries from group without the > risk to do the wrong? It is not obvious. > > Bernhard I looked in detail: I had selected a group of 13 entries. I added the pdf location of one of this papers to jabref in the "allgemein (General?)" dialogue of the edit article form. When I finished adding the pdf location, the selection of the 13 papers in the group got lost. Clicking on the group in the Group form did not bring up the selection again, but deleted the selected entry from the group. Re-clicking added it again, but still the selection was gone. I do not find a simple way to select a group when a paper is selected in that group. Bernhard > spitzhalde9 > 79853 lenzkirch > ber...@gm... > www.b-kleine.com, www.urseetal.net > - > thunderbird mit enigmail > GPG schl?ssel: D5257409 > fingerprint: > 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature ------------------------------ Message: 2 Date: Sun, 12 Jun 2016 13:05:03 +0200 From: Bernhard Kleine <ber...@gm...> Subject: Re: [Jabref-users] Groups using not possible To: jab...@li... Message-ID: <ccd...@gm...> Content-Type: text/plain; charset="windows-1252" Am 12.06.2016 um 11:44 schrieb Bernhard Kleine: > Am 10.06.2016 um 07:13 schrieb Bernhard Kleine: > >> I started using groups with the previous jabref version. I have some >> 1300 bibentries and groups are as large as 140 or as small as 3 entries. >> >> When I want to display groups, however, I tried en vain to see the >> selected entries, mostly jabref adds the entry selected to a groups when >> clicking on a group. This is not the behaviour I am used to. How to >> display a group and not add or delete entries from group without the >> risk to do the wrong? It is not obvious. >> >> Bernhard > I looked in detail: I had selected a group of 13 entries. I added the > pdf location of one of this papers to jabref in the "allgemein > (General?)" dialogue of the edit article form. When I finished adding > the pdf location, the selection of the 13 papers in the group got lost. > Clicking on the group in the Group form did not bring up the selection > again, but deleted the selected entry from the group. Re-clicking added > it again, but still the selection was gone. I do not find a simple way > to select a group when a paper is selected in that group. > > Bernhard Unselecting "gruppenzugeh?rigkeit bearbeiten (manage entries in a group?)" did allow me again to select groups. It is not mentioned in the German Manual. Bernhard -- -- spitzhalde9 79853 lenzkirch ber...@gm... www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schl?ssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature ------------------------------ Message: 3 Date: Sun, 12 Jun 2016 08:18:30 -0400 From: Haines Brown <ha...@hi...> Subject: Re: [Jabref-users] Groups using not possible To: jab...@li... Message-ID: <201...@en...> Content-Type: text/plain; charset=us-ascii I've complained several times in another thread, so far no response, that JabRef 3.4 destroyed the @Comment{jabref-meta: groupstree: section of my .bib databases. The group tree is present, but has lost all keywords. I don't see how this could have happened through my blundering. I can recover that section from all my databases from a backup when still running JabRef 9.10 two weeks ago. I did this with a database, but a major problem remains. If I create a new group, it is not added to the groupstree, but is recorded somewhere else. Also, creating a link from an entry to a group creates a link to all groups with the same name. Please!!! Someone tell me what's going on. Has a new group mechanism been created? Where is that information being stored? Was it supposed to recover groupstree data from the .bib databases? I'll have to create links from entries to groups by entering the information into the databases by hand, but I worry that JabRef 3.4 will again destroy that information. Haines Brown ------------------------------ Message: 4 Date: Sun, 12 Jun 2016 14:22:30 +0200 From: Bernhard Kleine <ber...@gm...> Subject: Re: [Jabref-users] Groups using not possible To: jab...@li... Message-ID: <589...@gm...> Content-Type: text/plain; charset="windows-1252" Am 12.06.2016 um 14:18 schrieb Haines Brown: > I've complained several times in another thread, so far no response, > that JabRef 3.4 destroyed the @Comment{jabref-meta: groupstree: section > of my .bib databases. The group tree is present, but has lost all > keywords. > > I don't see how this could have happened through my blundering. I can > recover that section from all my databases from a backup when still > running JabRef 9.10 two weeks ago. I did this with a database, but a > major problem remains. If I create a new group, it is not added to the > groupstree, but is recorded somewhere else. Also, creating a link from > an entry to a group creates a link to all groups with the same name. > > Please!!! Someone tell me what's going on. Has a new group mechanism > been created? Where is that information being stored? Was it supposed to > recover groupstree data from the .bib databases? > > I'll have to create links from entries to groups by entering the > information into the databases by hand, but I worry that JabRef 3.4 will > again destroy that information. > > Haines Brown I know that there were changes in the group function. But I do not know whether your problem is related. My groups at least were maintained when I updated jabref to 3.4. Regards Bernhard -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature ------------------------------ Message: 5 Date: Sun, 12 Jun 2016 09:45:02 -0400 From: Haines Brown <ha...@hi...> Subject: Re: [Jabref-users] Groups using not possible To: jab...@li... Message-ID: <201...@en...> Content-Type: text/plain; charset=us-ascii On Sun, Jun 12, 2016 at 02:22:30PM +0200, Bernhard Kleine wrote: > Am 12.06.2016 um 14:18 schrieb Haines Brown: > > I've complained several times in another thread, so far no response, > > that JabRef 3.4 destroyed the @Comment{jabref-meta: groupstree: section > > of my .bib databases. The group tree is present, but has lost all > > keywords. > > > > I don't see how this could have happened through my blundering. I can > > recover that section from all my databases from a backup when still > > running JabRef 9.10 two weeks ago. I did this with a database, but a > > major problem remains. If I create a new group, it is not added to the > > groupstree, but is recorded somewhere else. Also, creating a link from > > an entry to a group creates a link to all groups with the same name. > > > > Please!!! Someone tell me what's going on. Has a new group mechanism > > been created? Where is that information being stored? Was it supposed to > > recover groupstree data from the .bib databases? > > > > I'll have to create links from entries to groups by entering the > > information into the databases by hand, but I worry that JabRef 3.4 will > > again destroy that information. > > > > Haines Brown > I know that there were changes in the group function. But I do not know > whether your problem is related. My groups at least were maintained when > I updated jabref to 3.4. > Regards > Bernhard I really would like to know what this new groups mechanism is. CHANGELOG suggests that with JabRef 3.3 the data held in the jabref-meta: groupstree: sections of bibliographic databases was transferred to something called "BibEntry". I find it succeeded for some databases, but not all. I see that JabRef now generates a host of files under /usr/local/share/JabRef/jabref-master/... and apparently overwriting them are user's preferences in ~/Xjabref-master/.... Unfortunately I was unable to locate a BibEntry there. There are MSBibEntry.java files, but these hold no specific group information. So my questions are: a) What and where is this "BibEntry"? It apparently is not the name of a file. b) Was it intended that this BibEntry preserve the original groups hierarchy? It does not seem to distinguish groups organized in hierarchic fashion. Even where I've restored the group tree functionality, groups with same name but situated in different places in the tree are not distinguished. Is BibEntry just a flat file database? c) How could all group data be lost when I moved up from JabRef 9.10 to JabRef 3.4? Is there something I should have done to prevent it? While I can recover old group hierarchies data, I don't want to loose recent additions again. Haines Brown ------------------------------ ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e ------------------------------ _______________________________________________ Jabref-users mailing list Jab...@li... https://lists.sourceforge.net/lists/listinfo/jabref-users End of Jabref-users Digest, Vol 115, Issue 2 ******************************************** |
From: Haines B. <ha...@hi...> - 2016-06-12 13:45:12
|
On Sun, Jun 12, 2016 at 02:22:30PM +0200, Bernhard Kleine wrote: > Am 12.06.2016 um 14:18 schrieb Haines Brown: > > I've complained several times in another thread, so far no response, > > that JabRef 3.4 destroyed the @Comment{jabref-meta: groupstree: section > > of my .bib databases. The group tree is present, but has lost all > > keywords. > > > > I don't see how this could have happened through my blundering. I can > > recover that section from all my databases from a backup when still > > running JabRef 9.10 two weeks ago. I did this with a database, but a > > major problem remains. If I create a new group, it is not added to the > > groupstree, but is recorded somewhere else. Also, creating a link from > > an entry to a group creates a link to all groups with the same name. > > > > Please!!! Someone tell me what's going on. Has a new group mechanism > > been created? Where is that information being stored? Was it supposed to > > recover groupstree data from the .bib databases? > > > > I'll have to create links from entries to groups by entering the > > information into the databases by hand, but I worry that JabRef 3.4 will > > again destroy that information. > > > > Haines Brown > I know that there were changes in the group function. But I do not know > whether your problem is related. My groups at least were maintained when > I updated jabref to 3.4. > Regards > Bernhard I really would like to know what this new groups mechanism is. CHANGELOG suggests that with JabRef 3.3 the data held in the jabref-meta: groupstree: sections of bibliographic databases was transferred to something called "BibEntry". I find it succeeded for some databases, but not all. I see that JabRef now generates a host of files under /usr/local/share/JabRef/jabref-master/... and apparently overwriting them are user's preferences in ~/Xjabref-master/.... Unfortunately I was unable to locate a BibEntry there. There are MSBibEntry.java files, but these hold no specific group information. So my questions are: a) What and where is this "BibEntry"? It apparently is not the name of a file. b) Was it intended that this BibEntry preserve the original groups hierarchy? It does not seem to distinguish groups organized in hierarchic fashion. Even where I've restored the group tree functionality, groups with same name but situated in different places in the tree are not distinguished. Is BibEntry just a flat file database? c) How could all group data be lost when I moved up from JabRef 9.10 to JabRef 3.4? Is there something I should have done to prevent it? While I can recover old group hierarchies data, I don't want to loose recent additions again. Haines Brown |
From: Bernhard K. <ber...@gm...> - 2016-06-12 12:22:55
|
Am 12.06.2016 um 14:18 schrieb Haines Brown: > I've complained several times in another thread, so far no response, > that JabRef 3.4 destroyed the @Comment{jabref-meta: groupstree: section > of my .bib databases. The group tree is present, but has lost all > keywords. > > I don't see how this could have happened through my blundering. I can > recover that section from all my databases from a backup when still > running JabRef 9.10 two weeks ago. I did this with a database, but a > major problem remains. If I create a new group, it is not added to the > groupstree, but is recorded somewhere else. Also, creating a link from > an entry to a group creates a link to all groups with the same name. > > Please!!! Someone tell me what's going on. Has a new group mechanism > been created? Where is that information being stored? Was it supposed to > recover groupstree data from the .bib databases? > > I'll have to create links from entries to groups by entering the > information into the databases by hand, but I worry that JabRef 3.4 will > again destroy that information. > > Haines Brown I know that there were changes in the group function. But I do not know whether your problem is related. My groups at least were maintained when I updated jabref to 3.4. Regards Bernhard |
From: Haines B. <ha...@hi...> - 2016-06-12 12:18:39
|
I've complained several times in another thread, so far no response, that JabRef 3.4 destroyed the @Comment{jabref-meta: groupstree: section of my .bib databases. The group tree is present, but has lost all keywords. I don't see how this could have happened through my blundering. I can recover that section from all my databases from a backup when still running JabRef 9.10 two weeks ago. I did this with a database, but a major problem remains. If I create a new group, it is not added to the groupstree, but is recorded somewhere else. Also, creating a link from an entry to a group creates a link to all groups with the same name. Please!!! Someone tell me what's going on. Has a new group mechanism been created? Where is that information being stored? Was it supposed to recover groupstree data from the .bib databases? I'll have to create links from entries to groups by entering the information into the databases by hand, but I worry that JabRef 3.4 will again destroy that information. Haines Brown |
From: Bernhard K. <ber...@gm...> - 2016-06-12 11:05:23
|
Am 12.06.2016 um 11:44 schrieb Bernhard Kleine: > Am 10.06.2016 um 07:13 schrieb Bernhard Kleine: > >> I started using groups with the previous jabref version. I have some >> 1300 bibentries and groups are as large as 140 or as small as 3 entries. >> >> When I want to display groups, however, I tried en vain to see the >> selected entries, mostly jabref adds the entry selected to a groups when >> clicking on a group. This is not the behaviour I am used to. How to >> display a group and not add or delete entries from group without the >> risk to do the wrong? It is not obvious. >> >> Bernhard > I looked in detail: I had selected a group of 13 entries. I added the > pdf location of one of this papers to jabref in the "allgemein > (General?)" dialogue of the edit article form. When I finished adding > the pdf location, the selection of the 13 papers in the group got lost. > Clicking on the group in the Group form did not bring up the selection > again, but deleted the selected entry from the group. Re-clicking added > it again, but still the selection was gone. I do not find a simple way > to select a group when a paper is selected in that group. > > Bernhard Unselecting "gruppenzugehörigkeit bearbeiten (manage entries in a group?)" did allow me again to select groups. It is not mentioned in the German Manual. Bernhard -- -- spitzhalde9 79853 lenzkirch ber...@gm... www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09 |
From: Bernhard K. <ber...@gm...> - 2016-06-12 09:44:40
|
Am 10.06.2016 um 07:13 schrieb Bernhard Kleine: > I started using groups with the previous jabref version. I have some > 1300 bibentries and groups are as large as 140 or as small as 3 entries. > > When I want to display groups, however, I tried en vain to see the > selected entries, mostly jabref adds the entry selected to a groups when > clicking on a group. This is not the behaviour I am used to. How to > display a group and not add or delete entries from group without the > risk to do the wrong? It is not obvious. > > Bernhard I looked in detail: I had selected a group of 13 entries. I added the pdf location of one of this papers to jabref in the "allgemein (General?)" dialogue of the edit article form. When I finished adding the pdf location, the selection of the 13 papers in the group got lost. Clicking on the group in the Group form did not bring up the selection again, but deleted the selected entry from the group. Re-clicking added it again, but still the selection was gone. I do not find a simple way to select a group when a paper is selected in that group. Bernhard > spitzhalde9 > 79853 lenzkirch > ber...@gm... > www.b-kleine.com, www.urseetal.net > - > thunderbird mit enigmail > GPG schlüssel: D5257409 > fingerprint: > 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09 |
From: Haines B. <ha...@hi...> - 2016-06-11 12:47:00
|
On Tue, Jun 07, 2016 at 08:56:41AM -0400, Haines Brown wrote: > When I moved to JabRef 3.4, I encountered a problem I had not seen > before. It is perhaps easiest to explain with a hypothetical example. > > Suppose I have these groups: > > hacksaw > |--teeth > |--metal > dentifrice > |--teeth > |--whitening > cogwheel > |--diameter > |--teeth > > Now suppose I have a bibliographic entry that has to do with > dentistry. I naturally link it to dentifrice, teeth. But what happens is > that all three instances of "teeth" are highlighted, so that when I > select articles having to do with dentifrice, teeth, also selected are > articles on hacksaw teeth and cogwheel teeth. > > I have been using JabRef 2.10 and apparently missed some configuration > option that is in 3.4. This behavior has brought an end to my work because I don't know if establishing links between database entries and JabRef groups is causing irreparable damage. Normally, in "@comment{jabref-meta groupstree:" links are organized in a hierarchy. Using my little hypothetical above, they would appear as: 1. ExplicitGroup:hacksaw\;0\;<a key value>\;; 2. ExplicitGroup:teeth\;0\;<a key value>\;; 1. ExplicitGroup:dentifrice\;0\;a key value>\;; 2. ExplicitGroup:teeth\;0\;<a key value>\;; ... In JabRef 3.4, there is also a "@comment{jabref-meta groupstree:" section in each database. However, it is no longer being used. New links do not show up in it at all. All my old links between entries and group names are gone. That is, each group is empty: 3 ExplicitGroup:,groupname>\;0\;; Nevertheless if I click on a group, it somehow selects entries. This suggests that JabRef 3.4 is using a different mechanism than the old groupstree. However, this new mechanism is not hierarchical. For example, in my hypothetical above, if I click on hacksaw,teeth, entries for dentifrice,teeth and cogwheel,teeth are also selected. This seems a major bug. Is everyone experiencing the same thing, or have I grossly mis-configured JabRef? Haines Brown |
From: Bernhard K. <ber...@gm...> - 2016-06-10 05:13:44
|
I started using groups with the previous jabref version. I have some 1300 bibentries and groups are as large as 140 or as small as 3 entries. When I want to display groups, however, I tried en vain to see the selected entries, mostly jabref adds the entry selected to a groups when clicking on a group. This is not the behaviour I am used to. How to display a group and not add or delete entries from group without the risk to do the wrong? It is not obvious. Bernhard -- spitzhalde9 79853 lenzkirch ber...@gm... www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09 |
From: Marisano J. <mar...@gm...> - 2016-06-08 16:03:10
|
Hi Haines, Sorry I can't help you: I don't use groups at all, and we're in finals week at my university. [I suspect that the end of the academic year may be making a lot of folks less responsive right now.] Just wanted to say *something*. Marisano On Wed, Jun 8, 2016 at 4:10 AM, Haines Brown <ha...@hi...> wrote: > On Tue, Jun 07, 2016 at 08:56:41AM -0400, Haines Brown wrote: > > When I moved to JabRef 3.4, I encountered a problem I had not seen > > before. It is perhaps easiest to explain with a hypothetical example. > > > > Suppose I have these groups: > > > > hacksaw > > |--teeth > > |--metal > > dentifrice > > |--teeth > > |--whitening > > cogwheel > > |--diameter > > |--teeth > > > > Now suppose I have a bibliographic entry that has to do with > > dentistry. I naturally link it to dentifrice, teeth. But what happens is > > that all three instances of "teeth" are highlighted, so that when I > > select articles having to do with dentifrice, teeth, also selected are > > articles on hacksaw teeth and cogwheel teeth. > > > > I have been using JabRef 2.10 and apparently missed some configuration > > option that is in 3.4. > > Not wishing to continue with this multiplication of groups, I reverted > to JabRef 9.10. However, its group function is now gone. Whatever group > I select, no entries are associated with it. I can create link groups > with entries, but all old information is missing. > > What is the file that holds this information? Knowing it I could > partially recover from a backup. > > Haines Brown > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _______________________________________________ > Jabref-users mailing list > Jab...@li... > https://lists.sourceforge.net/lists/listinfo/jabref-users > |
From: Haines B. <ha...@hi...> - 2016-06-08 11:10:55
|
On Tue, Jun 07, 2016 at 08:56:41AM -0400, Haines Brown wrote: > When I moved to JabRef 3.4, I encountered a problem I had not seen > before. It is perhaps easiest to explain with a hypothetical example. > > Suppose I have these groups: > > hacksaw > |--teeth > |--metal > dentifrice > |--teeth > |--whitening > cogwheel > |--diameter > |--teeth > > Now suppose I have a bibliographic entry that has to do with > dentistry. I naturally link it to dentifrice, teeth. But what happens is > that all three instances of "teeth" are highlighted, so that when I > select articles having to do with dentifrice, teeth, also selected are > articles on hacksaw teeth and cogwheel teeth. > > I have been using JabRef 2.10 and apparently missed some configuration > option that is in 3.4. Not wishing to continue with this multiplication of groups, I reverted to JabRef 9.10. However, its group function is now gone. Whatever group I select, no entries are associated with it. I can create link groups with entries, but all old information is missing. What is the file that holds this information? Knowing it I could partially recover from a backup. Haines Brown |
From: Haines B. <ha...@hi...> - 2016-06-07 12:56:50
|
When I moved to JabRef 3.4, I encountered a problem I had not seen before. It is perhaps easiest to explain with a hypothetical example. Suppose I have these groups: hacksaw |--teeth |--metal dentifrice |--teeth |--whitening cogwheel |--diameter |--teeth Now suppose I have a bibliographic entry that has to do with dentistry. I naturally link it to dentifrice, teeth. But what happens is that all three instances of "teeth" are highlighted, so that when I select articles having to do with dentifrice, teeth, also selected are articles on hacksaw teeth and cogwheel teeth. I have been using JabRef 2.10 and apparently missed some configuration option that is in 3.4. Haines Brown |
From: Haines B. <ha...@hi...> - 2016-06-06 16:23:26
|
I installed JabRef 3.4 on Debian Wheezy and encountered a very problematic behavior. I can best explain it by a simple hypothetical. Suppose I have groups like this: tools |--grinding |--sanding teeth |--grinding |--dentures And a bibliographic entry that concerns machine shop practices. I drag it to tools, grinding, and (now) the group grinding becomes highlighted as it should. But the group grinding under teeth does as well. So if I click on either grinding, the entries for teeth and tools in the database are both selected. Am I missing something in JabRef configuration? Haines Brown |
From: Peretsman-Clement, G. <gpe...@ca...> - 2016-05-24 18:57:38
|
Hello from an enthusiastic JabRef newbie, Can't find an answer to this (probably stupid) question in JabRef documentation, or in any YouTube video: How to move selected imported references from the Inspection window into an open JabRef database? Or save them to a new JabRef database? Screenshot would help. Thank you! Gail Clement Gail P. Clement | Head of Research Services | Caltech Library | Mail Code 1-43 | Pasadena CA 91125-4300 | 626-395-1203 http://orcid.org/0000-0001-5494-4806 | library.caltech.edu |
From: Rich S. <rsh...@ap...> - 2016-05-19 23:28:21
|
I'm running version 3.3 on Slackware-14.1. There's an interesting (actually, annoying) response an entry in the 'Proceeding' category. This document type has no author field. Therefore, when the list of documents is displayed the author field is at the end of the previously entries that are listed in alphabetical order. All documents entered after the Proceedings one are in entry order, not alphabetical sequence. It took me a while to recognize that it's the blank author field causing the problem. I changed the document type from 'Proceeding' to 'Conference' and moved the Editor names to Author, and every row was once again alphabetically sorted. I'm sure this is unintended behavior and can likely be fixed by adding an Author field to the required field tab, even if the 'author' is really a set of editors. Rich |
From: Panos I. <pan...@gm...> - 2016-05-18 18:06:10
|
Thanks for the info Felix. It does look like an interesting application. I'll keep it in mind for next time! Panos On Wed, May 18, 2016 at 9:47 AM, Felix Wilke <fel...@gm...> wrote: > Hey, in case you need more styles later on: I wrote a handy tool to > compile Export Formatters: > > https://sourceforge.net/projects/efe/ > > greetings > felix > > On 16 May 2016 at 12:31, Panos Ioannidis <pan...@gm...> > wrote: > >> This is to let you know that I found the solution on how to generate the >> reference list! >> >> In case anyone has the same question, I got the sample html layout file >> from here >> >> http://haertle.ch/programs/jabref/ >> >> and then tweaked the contents of the html_layout.html file, so that it >> contains the same formatting rules as my jstyle file (for the particular >> journal I'm interested in). >> >> Last, I created a new custom export type from "Options -> Manage Custom >> exports" by selecting the html_layout.html file and giving the other >> details as well (name of the journal in the first field and the ".html" >> extension in the last field). >> >> After doing these, you can select your references and choose "File -> >> Export selected entries". From the "Save" window that will appear, select >> your newly created custom export type from the "Files of type" dropdown >> menu. Clicking "Save" will create an html file which you can open in a web >> browser and then copy/paste the reference list to your LO document. >> >> If anyone needs the files I used I'll be happy to share them. >> >> Panos >> >> >> On Mon, May 16, 2016 at 9:01 AM, Panos Ioannidis < >> pan...@gm...> wrote: >> >>> Marisano, thanks! The CITATION section was what I was looking for! >>> >>> I have one more question! Is there a way to generate a reference list, >>> formatted according to a style which I can copy/paste in the References >>> section of my document? The reason I'm asking is because when I enter the >>> citations by using the "link" between Jabref and LibreOffice, my document >>> gets "heavy" (takes too long to add another citation) after adding 30-40 >>> references. Something that gets close to what I want is to right-click on >>> your selected references and choose "Copy... -> Export to Clipboard". But >>> the problem is that the "Export format" window that appears doesn't contain >>> any style... >>> >>> Thanks, >>> Panos >>> >>> >>> On Sat, May 14, 2016 at 3:08 PM, Marisano James <mar...@gm...> >>> wrote: >>> >>>> Hi Panos, >>>> >>>> Are you referring to the use of .jstyle files with LibreOffice (or >>>> OpenOffice)? If so, then the page you want to look at is: >>>> >>>> http://help.jabref.org/en/OpenOfficeIntegration >>>> >>>> In a style file there's a section labeled, "CITATION" (all caps). In >>>> that section you'll find the constants, "AuthorLastSeparator" and >>>> "AuthorLastSeparatorInText". These can be used to change the appearance of >>>> the separator between the last names of two authors. In your case, I >>>> believe AuthorLastSeparator is set to <", ">, that is, in the CITATION >>>> section: >>>> >>>> AuthorLastSeparator=", " >>>> >>>> appears (or perhaps to nothing at all, and AuthorSeparator is set to >>>> <", ">). Try setting AuthorLastSeparator equal to <" and ">, saving the >>>> style file, reloading it in JabRef, and updating the bibliography in LO or >>>> OO by pressing the circle arrow button in the OpenOffice/LibreOffice area >>>> to the left of the JabRef window. >>>> >>>> Cheers, >>>> Marisano >>>> >>>> On Sat, May 14, 2016 at 4:13 AM, Panos Ioannidis < >>>> pan...@gm...> wrote: >>>> >>>>> Hello, >>>>> >>>>> I'm having fun using JabRef to manage the references for the >>>>> manuscript I'm preparing! I have managed to format my references according >>>>> to the journal's guidelines, but have a problem for citations in the text. >>>>> >>>>> So, when I have a reference with exactly two authors, the citation in >>>>> the text is like "(Johnson,Jackson 2008)" instead of "(Johnson *and* >>>>> Jackson 2008)". >>>>> >>>>> How can I format the citations in the text? Is this done by using >>>>> formatters other than those listed here >>>>> <http://help.jabref.org/en/CustomExports>? Because as far as I can >>>>> tell the formatters affect only the reference list, at the end of the >>>>> manuscript. >>>>> >>>>> Thanks, >>>>> Panos >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Mobile security can be enabling, not merely restricting. Employees who >>>>> bring their own devices (BYOD) to work are irked by the imposition of >>>>> MDM >>>>> restrictions. Mobile Device Manager Plus allows you to control only the >>>>> apps on BYO-devices by containerizing them, leaving personal data >>>>> untouched! >>>>> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j >>>>> _______________________________________________ >>>>> Jabref-users mailing list >>>>> Jab...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/jabref-users >>>>> >>>>> >>>> >>> >> >> >> ------------------------------------------------------------------------------ >> Mobile security can be enabling, not merely restricting. Employees who >> bring their own devices (BYOD) to work are irked by the imposition of MDM >> restrictions. Mobile Device Manager Plus allows you to control only the >> apps on BYO-devices by containerizing them, leaving personal data >> untouched! >> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j >> _______________________________________________ >> Jabref-users mailing list >> Jab...@li... >> https://lists.sourceforge.net/lists/listinfo/jabref-users >> >> > |
From: sukhjit s. <suk...@gm...> - 2016-05-18 16:39:37
|
I am trying to export bib to .csv and there are many issues being faced: 1. special symbols are not coverted properly to the same symbols e.g. " " chaning to different sysmbols 2. If my Jabref entry has (http://www.uppaal.org/) content then it is converted to (http://†<http://xn--2ca093n>‹www.​uppaal.​org/​). 3. Author in other languaes correct in Jabref António José Silva and Jorge Gustavo Rocha and in .csv it is like {António José Silva and Jorge Gustavo Rocha} The encoding of JabRef is UTF-8 Please help to resolve the issue and also tell if this problem with Excel Encoding Thanks -- Er. Sukhjit Singh Sehra Assistant Professor Dept of Computer Science Engg. Guru Nanak Dev Engineering College, Ludhiana, Punjab Mobile No:- 09855959200 **Kindly visit sikh-relics.in - A Gallery of Blessed Relics of Sikh Guru Sahib |
From: Panos I. <pan...@gm...> - 2016-05-16 10:32:20
|
This is to let you know that I found the solution on how to generate the reference list! In case anyone has the same question, I got the sample html layout file from here http://haertle.ch/programs/jabref/ and then tweaked the contents of the html_layout.html file, so that it contains the same formatting rules as my jstyle file (for the particular journal I'm interested in). Last, I created a new custom export type from "Options -> Manage Custom exports" by selecting the html_layout.html file and giving the other details as well (name of the journal in the first field and the ".html" extension in the last field). After doing these, you can select your references and choose "File -> Export selected entries". From the "Save" window that will appear, select your newly created custom export type from the "Files of type" dropdown menu. Clicking "Save" will create an html file which you can open in a web browser and then copy/paste the reference list to your LO document. If anyone needs the files I used I'll be happy to share them. Panos On Mon, May 16, 2016 at 9:01 AM, Panos Ioannidis <pan...@gm...> wrote: > Marisano, thanks! The CITATION section was what I was looking for! > > I have one more question! Is there a way to generate a reference list, > formatted according to a style which I can copy/paste in the References > section of my document? The reason I'm asking is because when I enter the > citations by using the "link" between Jabref and LibreOffice, my document > gets "heavy" (takes too long to add another citation) after adding 30-40 > references. Something that gets close to what I want is to right-click on > your selected references and choose "Copy... -> Export to Clipboard". But > the problem is that the "Export format" window that appears doesn't contain > any style... > > Thanks, > Panos > > > On Sat, May 14, 2016 at 3:08 PM, Marisano James <mar...@gm...> > wrote: > >> Hi Panos, >> >> Are you referring to the use of .jstyle files with LibreOffice (or >> OpenOffice)? If so, then the page you want to look at is: >> >> http://help.jabref.org/en/OpenOfficeIntegration >> >> In a style file there's a section labeled, "CITATION" (all caps). In that >> section you'll find the constants, "AuthorLastSeparator" and >> "AuthorLastSeparatorInText". These can be used to change the appearance of >> the separator between the last names of two authors. In your case, I >> believe AuthorLastSeparator is set to <", ">, that is, in the CITATION >> section: >> >> AuthorLastSeparator=", " >> >> appears (or perhaps to nothing at all, and AuthorSeparator is set to <", >> ">). Try setting AuthorLastSeparator equal to <" and ">, saving the style >> file, reloading it in JabRef, and updating the bibliography in LO or OO by >> pressing the circle arrow button in the OpenOffice/LibreOffice area to the >> left of the JabRef window. >> >> Cheers, >> Marisano >> >> On Sat, May 14, 2016 at 4:13 AM, Panos Ioannidis < >> pan...@gm...> wrote: >> >>> Hello, >>> >>> I'm having fun using JabRef to manage the references for the manuscript >>> I'm preparing! I have managed to format my references according to the >>> journal's guidelines, but have a problem for citations in the text. >>> >>> So, when I have a reference with exactly two authors, the citation in >>> the text is like "(Johnson,Jackson 2008)" instead of "(Johnson *and* >>> Jackson 2008)". >>> >>> How can I format the citations in the text? Is this done by using >>> formatters other than those listed here >>> <http://help.jabref.org/en/CustomExports>? Because as far as I can tell >>> the formatters affect only the reference list, at the end of the manuscript. >>> >>> Thanks, >>> Panos >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Mobile security can be enabling, not merely restricting. Employees who >>> bring their own devices (BYOD) to work are irked by the imposition of MDM >>> restrictions. Mobile Device Manager Plus allows you to control only the >>> apps on BYO-devices by containerizing them, leaving personal data >>> untouched! >>> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j >>> _______________________________________________ >>> Jabref-users mailing list >>> Jab...@li... >>> https://lists.sourceforge.net/lists/listinfo/jabref-users >>> >>> >> > |