From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: exported contacts problem
Date: Sat, 03 Aug 2019 14:32:38 -0700 [thread overview]
Message-ID: <87pnlmvssp.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAKuG=vtL2NgokmOU6EMpOzQ5dL2QH3BW8yANaYhJ7BR8RmOihw@mail.gmail.com
Neil Jerram <neiljerram@gmail.com> writes:
> I've tried to work on contact conversion and synchronization in the past,
> aiming to merge and unify contacts that I've built up in BBDB, Google
> Contacts, email systems, pre-Android phones, etc. The problematic aspect
> was different systems using different field names and structures, e.g. one
> with separate First Name and Last Name, and another with a combined Name
> field; different approaches to breaking up addresses; additional arbitrary
> notes fields; etc.
>
> With that in mind, I'm curious if the writers on this thread could comment
> on:
> 1. is this situation any better now?
If by "this situation" you mean fragmentation of data formats and
approaches, I don't think it's getting any better!
> 2. if you favour using org-contacts or org-vcard, what do you see as the
> benefit of Org as your master contact format, as opposed to say BBDB or
> .vcf?
I think something similar happens with Org as with happens with Emacs in
general: it's such a nice environment to be working in that people want
to move all their stuff into it. But there are some areas (contact
management, email, large datasets) where Org just isn't going to work as
well as a specialized tool.
But Org can be an excellent *interface* to those tools, mostly through
dynamic blocks. I've started using small sqlite databases to keep track
of things, and dynamic blocks as sql composers/views, and it works
great. It's very easy to play with the queries, and this is the first
time I'm actually starting to feel comfortable with sql.
I think in general Org is best used as a compositional tool for data
drawn from elsewhere.
Eric
next prev parent reply other threads:[~2019-08-03 21:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 15:47 exported contacts problem Jude DaShiell
2019-08-02 16:00 ` Jean Louis
2019-08-02 16:02 ` Jean Louis
2019-08-02 16:06 ` Jude DaShiell
2019-08-02 21:09 ` Eric Abrahamsen
2019-08-02 21:34 ` Jean Louis
2019-08-03 0:26 ` Eric Abrahamsen
2019-08-03 10:33 ` Jean Louis
2019-08-03 15:38 ` Eric Abrahamsen
2019-08-03 16:32 ` Jean Louis
2019-08-03 17:48 ` Neil Jerram
2019-08-03 18:25 ` Jean Louis
2019-08-03 21:32 ` Eric Abrahamsen [this message]
2019-08-03 22:12 ` Jean Louis
2019-08-04 1:28 ` Tim Cross
2019-08-13 22:24 ` David Masterson
2019-08-14 20:38 ` Eric Abrahamsen
2019-08-16 0:07 ` David Masterson
2019-08-03 10:48 ` Jean Louis
2019-08-02 22:19 ` John Kitchin
2019-08-02 20:33 ` Tim Cross
2019-08-02 20:57 ` Jude DaShiell
2019-08-02 21:25 ` Tim Cross
2019-08-02 21:39 ` Jean Louis
2019-08-02 22:07 ` Tim Cross
2019-08-03 8:25 ` Jean Louis
2019-08-02 21:00 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnlmvssp.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).