Re: Should a human ever set the ID property? Should a human only ever set the CUSTOM_ID property?

[Karl Voit <devnull@Karl-Voit.at>]

* Grant Rettke <gcr@wisdomandwonder.com> wrote:
> Good evening,

Hi!

> Just learned about CUSTOM_ID property. 

I was not aware of it either until a couple of minutes ago.

> It seems like if you want to define a custom identifier, then you
> do it here and that identifier will get used correctly in all of
> the weavers. It also seems like a human should never set the value
> of the ID property.

Well, either I don't understand CUSTOM_ID vs ID not completely or
I've got some arguments for writing IDs by myself:

I only create ID-properties manually and only for cases where I want
to link to a heading. My IDs look like
"2016-08-25-install-xubuntu-notebook" and therefore, all links to it
are self-explanatory: id:2016-08-25-install-xubuntu-notebook

I use them with org-depend.el for blocking, setting status on
completing tasks, and so forth.

So far, I do not think that I can use CUSTOM_ID for org-depend.el.
At least a test with ":BLOCKER: a-custom-id" (or "#a-custom-id") did
not seem to have any impact.

My blogging system[1] is also using (manually crafted) IDs to refer
to blog articles.

> The reason I ask is that I've got code that makes sure that every
> headline has an ID property set unique because org-uuid makes it so
> easy. 

I can't follow your argument. What is org-uuid and why should I have
automatically generated IDs? 

I once had "org-mobile-force-id-on-agenda-items" activated which
produced random(?) IDs for all headings. I could not find any use
for it.


[1] https://github.com/novoid/lazyblorg
-- 
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