Rick, I always try and keep tiddlers as object-types for ease of use, each object can have a page with a list of its type on it
- Character - Story - Location - Storylin arc (is this only a relationship)? - Items (Are these just tiddlers with story content? But I also note that some of the additional information may not be suited to a field within the object. I do think Marios TOCP with custom fields eg location-parent may be helpful. Are you going to manually reference characters and locations like tagging or will you prefer automatic identification from the text? If manual perhaps Marios GenTags plugin and multiple tag like fields eg location character and structure(Of story), I recomend against loading the tags with too many tags and mixing tags for different objects. As Mario pointed out TOC solutions have you lookedup my suggested twoutlier twoutliner, Or tabbed internal navigation TOC? Regards Tony On Sunday, 13 October 2019 19:54:06 UTC+11, Rick Yagodich wrote: > > Here's the architecture I have in mind for this. A single TW instance will > manage one or more stories (books, novellas, etc) within a shared > environment (setting). It will manage characters, locations, objects, > storylines. > > > - Setting overview > - Characters > - character description > - background > - psychological profile > - character-to-character relationships (static acceptable) > - per-scene character arcs > - Locations > - location description > - location-to-location relationships (parent-child, e.g. room in > house in city in country) > - Items > - item-scene locations (ref location) > - item-scene states (e.g. broken) > - Story (ordered) > - title > - summary > - Storylines > - storyline description > - Chapters (ordered in story) > - chapter summary > - Scenes (ordered in chapter) > - scene summary > - characters in scene > - character prevalence in scene (pov, present, referenced, > mentioned) > - per-scene character arc (dupl.) > - locations in scene > - items in scene > - item state in scene > - storylines in scene > > When viewed as a reference work, it would then have the following > capabilities to surface its data: > > > - *Default page*: showing Setting overview. Links to Characters-list, > Stories-list, Locations-list, Items-list. > - *Characters-list*: shows all characters, links to Character-page. > - *Stories-list*: shows all stories, links to Story-page. > - *Locations-list*: show all locations, links to Location-page. > - *Items-list*: shows all items, links to Item-page. > - *Character-page*: shows character description & > character-to-character relationships. Lists Stories character present in, > links to Character-story-arc page. > - *Character-story-arc page*: shows all per-scene character arcs for > this character, within this story, ordered by chapter and scene-in-chapter. > - *Story-page*: shows story's title & summary. Lists all storylines, > links to Storyline-arc-page. Links to Detailed-story-page. > - *Detailed-story-page*: shows all chapter summaries within this > story, ordered by chapter. > - *Storyline-arc-page*: shows storyline description. Shows all scene > summaries, ordered by chapter and scene-in-chapter, referenced to this > storyline. > - *Location-page*: shows location description. > - *Item-page*: shows item description. Lists all scenes, ordered by > chapter and scene-in-chapter, wherein the item is in-scene, with its state > in that scene. > > -- 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/c74a1ef4-e831-4626-be54-8908c6bd5d23%40googlegroups.com.
