Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(default option to) disable all yellow topics-creation #99

Open
DavidGretzschel opened this issue Apr 19, 2020 · 2 comments
Open

(default option to) disable all yellow topics-creation #99

DavidGretzschel opened this issue Apr 19, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@DavidGretzschel
Copy link

DavidGretzschel commented Apr 19, 2020

Please add an option to not create any of the extra yellow topics during the PDF-import and processing workflow and enable it by default.

That includes the very source topic.
When I import the PDF "how to avoid big boats" under the "sailing"-concept of my knowledge tree, I don't need another yellow topic named "Sailing" below "Saililng" in which I can see the green PDF-topic "How to Avoid big Boats".
Reading "How to avoid big boats" and extracting the chapter "Various Types of big Boats", I don't want to see another yellow topic named "How to Avoid big Boats" under the green PDF-topic "How to Avoid big Boats".
When I wish to create an extract from the topic "Various Types of big Boats", I don't need another yellow topic named "Various Types of big Boats" between my extract and the text-extract "Containerships".
These extra yellow topics are a pain to manually remove and clutter up the Knowledge Tree for very little gain.
For those of use who use Neural Review and make Concept and Element-links, it's very important to be able to see the KT clearly without extra formatting noise.
Here's an example with "The Mind Illuminated" (as I'm sadly not an owner of "How to Avoid big Boats"
This:
image
looks much more difficult to parse at a glance than this:
image

I understand that this is to break up the number of elements accumulating within a branch so that noone would hit the default "children per branch" limit of 100. But for a PDF workflow, I believe it's reasonable to assume that almost no book has 100 chapters. Nor will any chapter yield 100 extracts. Nor is any extract likely to have 100 subextracts.
And for those few people who do run into this issue, it would be no trouble to simply set the limit to its maximum value of 500.
image

@alexis- alexis- added the enhancement New feature or request label May 9, 2020
@alexis- alexis- added this to the SMA 2.2.0 "Pink panther" milestone May 9, 2020
@alexis-
Copy link
Member

alexis- commented May 9, 2020

Not everyone extracts chapters into their own sub-PDF files, and most books will yield more than a 100 extracts.
Also most people have their children limit set to 100, and few of them know that this option even exist.

This will likely stay the default, but there could be an option in the future to disable the intermediate folder.

@DavidGretzschel
Copy link
Author

Not that opinionated about it having to be default or not. But I definitely do want that option.
An overnested KT looks like trash and I don't want it. I like pretty things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants