![]() ![]() 12/000 Betrieb und Support Index), but that meant putting these on the AC–AC levels (eg. ![]() I (re-)introduced index notes I had already experimented with during my last time in NotePlan (eg. These sub-notes do not get entries in the J.D index, by the way. NetApp-Snapshots, 12/006b Testen des Migrations-Patches etc. (originally) 12/006a File(service)-Migration vs. gets too long and unwieldy), it “spawns” linked “sub-notes” with the letters a to z added to the J.D number, eg. If one note (de facto one Markdown file) is not enough (ie. I had already decided to move “sideways” instead in a bit of a “Zettelkasten-inspired” way. And a lot of AC.ID folders would have contained only one file. I didn’t feel right to make it a folder because the then unnumbered files therein would become somewhat messy. 12/006 Upgrade auf ILIAS 7 was a “project” in Agenda’s terms containing “unnumbered” notes, it now was (and still is) a note in NotePlan. The AC–AC and AC levels originally translated themselves into folders, but where eg. Of course stuff I had put in a personal and a work “catch-all” logging/journaling category with yearly projects (2021, 2022 etc.) in Agenda plus some other stuff went (back) into the daily notes in NotePlan, freeing up some “J.D space”. Initially I simply moved the existing structure and notes back from Agenda to NotePlan more or less 1:1. I use it for my files, too, but since I don’t “do” that many (new) files anymore these days it’s a little bit of an “after-use”, albeit a very welcome one. I still use J.D foremost as means to organize notes, nowadays in NotePlan (again). ![]() Since I talked about my own derivate of J.D (and P.A.R.A.) last November my implementation underwent some changes recently. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |