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 |