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

Hypothesis: too heavy file #24

Open
AtomicNess123 opened this issue Jan 8, 2021 · 4 comments
Open

Hypothesis: too heavy file #24

AtomicNess123 opened this issue Jan 8, 2021 · 4 comments

Comments

@AtomicNess123
Copy link

Hi, I have been using orger to for my hypothesis database. However, the org file has become too big at this point.

Do you know of a way to start syncing into a second file after the file has become too big? (or start syncing into a second file from a predefined time point instead of syncing into the same file)? Thanks!

@karlicoss
Copy link
Owner

Hi! Yeah, it's soon going to be a problem for me as well. Not supported as is at the moment, but I might look at it soon-ish!

@hwiorn
Copy link

hwiorn commented Mar 25, 2022

@karlicoss
I have 1k+ annotations. It's not many.
But it seems to be quite slowly to load it at first when I'm trying to link it to org-roam notes.

How about these Orger options?

  1. Split org files by numbers(e.g: 5000 annotations per file).
  • Output: HypView-0001.org, HypView-0002.org, ...
  1. Split org files per on web page.
  • Output: HypView-github-karlicoss-orger-issues-24.org
  1. Split org files per on hypothesis annotation group.
  • Output: HypView-PromnesiaDev.org

1 or 2 can be implemented inside Orger itself. 3 should change the hypexport to handle hypothesis group fields for Orger.

@AtomicNess123
Copy link
Author

Yes, I have +10k annotations, and I can't use the file in Agenda anymore 😆

@karlicoss
Copy link
Owner

Yeah, @hwiorn I think 1 makes the most sense -- in addition to it being possible to implement in Orger itself, it's also can be completely agnostic of Hypothesis, so it'll also work for other modules. Perhaps it could be a code change somewhere around this line

def make_tree(self) -> OrgNode:

Another option would be to split by file size, although I'd imagine with something like 1000 annotations per file it won't matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants