Naming taxonomy cont

[Null]

So far have features like Search and everything else working, which is great!

Everything else is working as I want it to

Just need some additional advice on naming the tiddlers:

⠀

Example of how I’d name some of them:

USA/Alabama/Public Parks/Entry1
USA/Alabama/Public Parks/Entry2
USA/California/Public Parks/Entry1
USA/Florida/Golf Course/Entry1
USA/Florida/Golf Course/Entry2
USA/Florida/Public Parks/Entry1
Canada/Ontario/Public Parks/Entry1
Worldwide/Public Parks/Entry1
Worldwide/Public Parks/Entry2

Is this a solid naming scheme?
Would this work to avoid duplicates and avoid overwriting any tiddlers down the road?

⠀

And use a custom caption field – these would be the visible, “fake” so to say, titles

[pmario]

I think, it is solid that way.

@Null

And use a custom caption field – these would be the visible, “fake” so to say, titles

There are some threads here at Talk, that discuss using the caption-field as a title.

[Null]

Thanks!
yesterday asked for some initial guidance:

Any recommendations on how to maintain each tiddler title unique

In addition to my last comment I did previously build a tiddlywiki where all (well many) of my customisations (not content) were under the / “root” and hierarchically named like plugins. If I was doing this again I would turn / into an additional system namespace, I now know how to do this https://namespaces.tiddlyhost.com/ Perhaps it is worth asking others if they would use such a feature? One could imagine adopting \ as a non system namespace, under which data is hierarchically organised a…

and got working a tweak from user Yan:

as I’m the exclusive user of my wiki, so I am happy with this small tweak you can drag into your wiki by @vilc. You can always switch it around as needed if you want to prioritise the title over the caption .

[vuk]

There’s never a silver bullet for naming.

While there’s no duplicates, there’s a lot of redundancy in your example. Think USA/Alabama/Public Parks/Entry1 vs USA/Alabama/Public Parks/Entry2. Whole USA/Alabama/Public Parks/ is the same, and if you’d have more levels of nesting and thousands of tiddlers, this gets worse size-wise.

If your smallest data entity is a location, all these fancy worldwide maps achieve uniqueness using coordinates for example. And additional data (category, state, country in your example) can be present as fields of Location tiddlers.

I’m not advocating for a total refactoring by any means. But you need to pick your data structure with a wider strategy than just avoiding duplicates. When you’ll search for locations in USA Alabama, will you be more comfortable with searching for ‘tiddlers with USA/Alabama title prefix’ or tiddlers that have both an USA field and Alabama field? Of course this can be pushed further and you may end with wanting to eliminate redundancy completely a la RDBM. I may be wrong but I think @Scott_Sauyet did some work showcasing how to search a la SQL SELECT with the TiddlyWiki tools, you may want to find that one and have a look at it as well, to get a wider perspective.