Useally my person does things 2, 3, 4 times from the begining again. Vision in mind, then still lacking this or that, yet not perfect.
The second question is particulary reflected in the first. And if having later 2100 file and wishing to put them on their places, morits would see why.
And thats also for the brain. Some might know mn001 , that it is in the Suttapitaka, in the first vagga. But if having a file called bhu001 one would have problems.
Now one could give them a real name only. karanayametta sutta So, knowing the name, would you know which pitaka, nikaya, vagga and subvagga it belongs?
Therefor both useful systems, that of "modern" codes from ATI (western focus is on suttas and ends there) and the tree from the edlers by names.
that is why there came {pitaka}.{nikaya}.{vagga}.({subvagga}).{sutta no.} as for the filename into being.
If searching for an01.001, by the surfix _{att/tik/any} on matches them well in the preview putting the letters into the search box. On the other side, if searching via sidemap it's fine as well.
This works all fine till atthakatha Abhidhamma and parts of tika. When coming to anya it's no more that clear executeable and Anya it self contains already double and tripple naming. A certain collection has the first book and the first chaper with same name containing things not clear a counterpart of the tipitaka.
Till today, and actually having spend 100's of hour on trying to sort in fine, may person came till abouf jataka to be sure that the system would not run ugly of build on a not suitable structur.
Now this here, my person guesses, since not even abhidhamma (horrible structur) has been sorted well in the west, is the first time after tipitaka.org (which used a simple but not asumesable code and indexssystem for a stabil not dynamic storing, yet hard to find anything if not a little familar) that the whole heritage of the Sanghayana get's sorted.
It's all looked simple for my person as well. Then after you developed structure for the fist and second level, after the 10 file you match a new vagga/subvagga structur... Since from jakata on there is since longer no much broad interest, Anya is like the book shelf in a studend room and not like a chemist register.
Practical Anya:
Caturārakkhadīpanī is a book under the collection Nīti-gantha-saṅgaho in Anya-Commentaty and contains serial book. Within the is the Caper Kāyapaccavekkhaṇā which is the actual file (pagename)
To come to it one follows the indexes (pagenames under the namespace tree calked index) one after another or more direct, since the fist index contains already the whole structur. Thats right, sub indexes are not really necessary if the fist already contains the whole.
So it has more practical reasons. For example think on an, mn, iti. If knowing the system of the Sanghayana one knows that iti is a subvagga of kn. Same counts danger counts for mn. there is no mn123 in the sanghayana edition. It came from many people focusing on a certain levels "gemeinsames vielfaches).
Now, for example, if on works out Visudhimagga the first book, he might expand the capters index and if finished, might copy it into the index of visudhimagga, even to the anya index. Another might work from another level...
It means it has been the result of practical work in the worst situation of knowing the whole of particalar parts. Since it will stay dynamic, the further levels indexes have been not deleted (like cscd) but serve 2 purposes easy to acces in both directions, on which level ever one might enter, and to focus on a scale suitable to ones concentration and reminding and then put it together upwardly, downwardy.
Thats why this system from of pitaka, nikaya, vagga has been keep here as well and the structure is either by name flat (aside anya for all files) but also physical in levels, not only presented by a digital tree like the xml in cscd. If looking on the flat system of cscd one will fine att file codes in the tipitaka and so on. Meaning that even this simple system runned out ugly after finding out detail from the elders.
Further, the middle placed indexes are thought to get enriched by single chapers within one file (anchor content #v1...v5) and the deepes would contain later also the single suttas links (anchor #s001...s057) of the files. Meaning getting a zoom level by level. For one index that becomes to large.
But as told, open to others as well. Just knowing that it can serve for "headage" for weeks and month, yet next day finding out... "ok, again from the beginning". It's like doing/training Jhana, mastering the worlds.
That is why doing = sacrify has it's benefit = having learned a skill.
So know that Nyom has to structer something that probably nobody knows as a whole in it's various details and structur. It needs to be open in that far and "nachvollziehbar" for others, as well as accessable for people coming from differen learnsystems. West does not know the way of the elders and elders do not know the code-thinking of western.
For example look at ATI where it ends and beginns to go astray of suttacentral, having trouble with vinaya and abhidhamma and possible no logical way to ever add the commentaries, yet references to brahmic text from nepal.
But as told, while knowing that even some parts of the suttapitaka in the tipitaka have to be chanced, it can not be expected to be perfect or to work out to be perfect before putting it into the shelf.
If particular names have to chanced late on, if the is no double naming on the pagename level, such can be made by steps online if the whole structur has certain consistence as a whole.5z
Things open to do at this point if wishing to do it in a larfe scale:
- proof and eventually correcting indexes and names of files
- renaming of files
- converting into wiki/wrap standard
- implementing anchors to the single suttas, chapters
- incl. Data table to each file (titel, url, date, origin...)
- upload into the folders (or incl folders) in the single lang-namespaces
So it's really open how one like to do it, but its not really a quick job to develop such, at least for my persons limits.