Re: [O] org-id fixups and minor changes

[Gustav Wikström]

Hi again,

 

FYI, I’ve applied a patch that will make it easier to change the default without breaking any existing functionality. I.e. we can avoid breakage for existing attachment-folders if we at some point in the future would choose to change default for ID’s to timestamp.

 

Commit 42b8db0d3

 

/G

 

From: Gustav Wikström
Sent: den 31 augusti 2019 21:17
To: Carsten Dominik <address@hidden>
Cc: address@hidden
Subject: RE: [O] org-id fixups and minor changes

 

Hi Carsten,

 

Yeah – you’re right, I didn’t think that much about automated ID creation so I stopped at seconds. I agree that it would be more general with more precision but that will also add some more noise into each ID. Maybe that’s not significant. But I also wonder how common it will be to try to batch-add ID’s…? I have nothing against adding more precision though, if that’s requested. What do you think?

 

Regarding documentation I’ll try to give it some thought. Maybe I’ll find some time to describe this area better 😊.

 

I wouldn’t mind changing the default from random to timestamp. But I’m not so sure about all the others? One thing that complicates things is the way attachment functionality parse the ID. If we use timestamps as the default ID it makes sense to change the default way org-attach parses the ID into folders as well. Something like “YYYY/MM/DD_and_the_rest”. But that will be a breaking changing. The existing folder-structure for attachments wouldn’t match the new any longer. Cleverness in code might solve the breakage though… If there is interest in changing the default I can try to solve the issue with the breaking change as well.

 

Regards

Gustav

 

From: Carsten Dominik <address@hidden>
Sent: den 10 augusti 2019 00:34
To: Gustav Wikström <address@hidden>
Cc: address@hidden
Subject: Re: [O] org-id fixups and minor changes

 

Hi Gustav,

 

I can see that it feels more natural to use timestamps.  I certainly see that relative file names are good for across-computer compatibility.

 

You system assumes, if I see that correctly (have not studied it yet), that not more that one ID will be created per second.  Or do you have something in place that will catch this, for example if someone uses the mapping API to assign IDs to a whole bunch of entries in a short time?

 

You are right that this is not documented in the manual, even though it is used for lings and for attachments.  Maybe it would be good to explain it in an appendix to the manual?  Would you like to draft such a section, since you have been looking into this problem?

 

Do you think the default setting for Org should be modified?

 

Carsten