TT;
You say
It is actually easier to have "title" v01ch49pa17 (=volumn 1, chapter 49,
> pqragraph 17) than do it through another field.
Whilst I think this can be an easy interim solution, because the key
contains the structure, and fields are a little more complex initially, I
do not think it the best ultimately. What is happening in this example is
you are creating a compound key. You are storing multiple parameters or
values inside the one key. It becomes harder for you to iterate each
partial key and demands you parse the key. If makes changes and reordering
difficult.
By separating these values into fields (or tags) you can actually apply
multiple structures to the same information. Imagine publishing an abridged
version on top of the previous volume, or an executive summary made up of
an abstract of the underlying full document.
I have a vision of providing tools to tiddlywiki to make such structuring
much simpler, supporting my own interest in tiddlywiki as a modeling
environment helping users build sophisticated knowledge networks using
fundamental database and organization techniques. There has being decades
of great work done in this field that is not readily available to the
general population but a relatively few principles can drive much more
effective knowledge management. Most of this has come from professional and
academic database designers. One of my treasured principals "Normalisation"
that your example breaks is nicely written as;
The content of a record should be "related to the key(title), the whole
key, and nothing but the key".
Tiddlywiki is great platform in which to popularise such knowledge and
methodologies then empower novices to take control of their own knowledge.
Regards
Tony
On Friday, November 1, 2019 at 3:46:10 AM UTC+11, @TiddlyTweeter wrote:
>
> Ciao TonyM
>
> TonyM wrote:
>>
>> I am a bit late to this thread and have not read it all, May I
>> respectfully suggest the value of the title is something you have chosen to
>> set in your example, it is you who has diminished its value by giving it a
>> numeric title.
>>
>
> You are right. The example, in a way, over-simplifies the issues.
>
>
>> ... it is operating as the "Primary key" to a piece of data.
>
>
> Yeah. Title as "simple king". Point being to start with what is indexed
> already, not what fields do I need add.
>
> For SOME purposes it makes most sense to treat the title as the index and
> present another field as the visible title ("caption" as my first choice).
>
> A good example is novels where you have a simple structure. It is actually
> easier to have "title" as v01ch49pa17 (=volumn 1, chapter 49, pqragraph 17)
> than do it through another field. The user never needs to see the titel
> anyway. You'd likely use a macro to present only a chapter at a time,
> headed by a caption from the first item. Seems logical?
>
> So. I'm, on titles just talking about a minimalist approach to certain
> types of (quite common) situations. This is not really news :-).
>
> Text field in general is another issue. A dopo.
>
> Best wishes
> TT
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/a17348e3-6298-4839-a388-9fea1f7f3c4d%40googlegroups.com.
