How do you avoid overwriting Tiddlers of the same name?

[Steve Guillaudeu]

(Relative newby #question) - 

Is there a way to ensure #import of a group of tiddlers from one TW into your TW does not overwrite existing tiddlers that happen to have the same name?

I'm trying to prevent problems I foresee years from now that could come from extensive shared TW use by a group or family.

Thank you for the help!  

Probably irrelevant, currently using:

Stroll with all empty TW5 tiddlers imported

(Ideally, I want to incorporate #TiddlyMap or #TiddlyRoam)

json import/exports of tiddlers

ON

Windows 10 Enterprise 10.0.18363 Build 18363

Edge Version 85.0.564.51 (Official build) (64-bit)

Chrome  Version 85.0.4183.102 (Official Build) (64-bit)

OR

Safari 14.0

macOS 10.14 Mojave

[PMario]

Hi,

I did create a "bundler" plugin, that also contains some new functions for the TW import mechanism.

With the default setting, it tells you, that there are some existing tiddlers. The text is: "Existing tiddler will be overwritten!" .. BUT the import button will be kept active.

There is a second setting, where it says: "A tiddler with that name exists. A new name will be used!"

TW has a possibility to preview the "diffs". So you will exactly see, what's different.

The intro thread can be found at: https://groups.google.com/forum/#!msg/tiddlywiki/_Uqbg08Pjow/xcQ_eKMFDQAJ

The plugin can be downloaded at: https://wikilabs.github.io/editions/bundler/#%24%3A%2Fplugins%2Fwikilabs%2Fbundler

have fun!

mario

[TW Tones]

Stev..

First and foremost if you can host a bob or bob.exe server you can have contention on tiddlers controlled. When one person is editing it another cant. However after that they can edit it and "replace" the tiddler.

Bob is at present the only way to have simultaneous access to one wiki for edit.

I am working on the larger picture of logins and tracking changes, but I do not have a finished product to share. The key for both node and single file, is I believe, the ability to checkin and out tiddlers Or whole wiki, so only one editor at a time will save disaster, next is a software layer within the wiki that managers the interaction of multiple users over time.

Regards

Tony

[Steve Guillaudeu]

Thank you both! I'll install that great bundler plugin and add "what about bob?" to my growing reading list :).