Re: Properties ID vs. CUSTOM_ID (was: Automatically Generating IDs From Title and Date)

[John Kitchin <jkitchin@andrew.cmu.edu>]

[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]

There is not an issue using a human-readable id in :ID: as long as it is
unique. It will store fine, link fine, etc...

John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu


On Thu, Dec 22, 2016 at 5:03 AM, Karl Voit <devnull@karl-voit.at> wrote:

> * Karl Voit <devnull@Karl-Voit.at> wrote:
> > * Samuel Wales <samologist@gmail.com> wrote:
> >> On 12/18/16, Karl Voit <devnull@karl-voit.at> wrote:
> >>>   Usually, my IDs start with the current ISO day to enforce uniqueness
> >>>   and look like this:
> >>
> >> my understanding, which might be incorrect, is that custom id is for
> >> human-readable purposes, while id is for uuid.  although you could
> >> prepend to uuid.
> >
> > To me, using :ID: was straight forward since I never read about any
> > other ID when I began with Org-mode in 2011.
>
> Another argument:
>
> According to
> http://orgmode.org/worg/org-contrib/org-depend.html
> I have to use :ID: properties and not :CUSTOM_ID: properties.
>
> ,----[ task with dependency to a generated ID ]
> | ** TODO a task
> | :PROPERTIES:
> | :BLOCKER: 6347hsfdl387ns43
> | :ID:
> `----
>
> ... in comparison to:
>
> ,----[ task with dependency to a manually written ID ]
> | ** TODO a task
> | :PROPERTIES:
> | :BLOCKER: contacting-customer-XY
> | :ID:
> `----
>
> I prefer the example with the manually written ID since it is human
> readable.
>
> --
> mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
>        > get Memacs from https://github.com/novoid/Memacs <
>
> https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on
> github
>
>
>

[-- Attachment #2: Type: text/html, Size: 3044 bytes --]