I agree, but not all databases works for everybody. For example SPIRES
does not work for me while ADS does. For somebody in high energy
physics the situation could be the opposite.
Unless there is a mechanism that works for everybody, havng it in the
fetcher makes much more sense
Fabio
On Sat, Nov 17, 2012 at 8:19 AM, koppor <email address hidden> wrote:
> This should be a general feature of JabRef, not a feature specific to a given fetcher.
> This is already filed as feature request for JabRef: https://sourceforge.net/p/jabref/feature-requests/689/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1055276
>
> Title:
> Update existing entry
>
> Status in JabRef plugin for fetching BibTeX entry from ADS:
> Confirmed
>
> Bug description:
> Update existing entry in the database to the ADS one. Overwrite/Merge
> option should be provided.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/jabref-ads/+bug/1055276/+subscriptions
I agree, but not all databases works for everybody. For example SPIRES
does not work for me while ADS does. For somebody in high energy
physics the situation could be the opposite.
Unless there is a mechanism that works for everybody, havng it in the
fetcher makes much more sense
Fabio
On Sat, Nov 17, 2012 at 8:19 AM, koppor <email address hidden> wrote: /sourceforge. net/p/jabref/ feature- requests/ 689/ /bugs.launchpad .net/bugs/ 1055276 /bugs.launchpad .net/jabref- ads/+bug/ 1055276/ +subscriptions
> This should be a general feature of JabRef, not a feature specific to a given fetcher.
> This is already filed as feature request for JabRef: https:/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Update existing entry
>
> Status in JabRef plugin for fetching BibTeX entry from ADS:
> Confirmed
>
> Bug description:
> Update existing entry in the database to the ADS one. Overwrite/Merge
> option should be provided.
>
> To manage notifications about this bug go to:
> https:/