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

Split ORB PDF Scrapper into its own package #143

Open
j-steinbach opened this issue Dec 8, 2020 · 2 comments
Open

Split ORB PDF Scrapper into its own package #143

j-steinbach opened this issue Dec 8, 2020 · 2 comments

Comments

@j-steinbach
Copy link

As mentioned in #140 (comment).


org-roam-bibtex calls itself a

Connector between Org-roam, BibTeX-completion, and Org-ref

whereas the documentation calls ORB PDF Scrapper an

Emacs interface to anystyle, an open-source software based on powerful machine-learning algorithms. It requires anystyle-cli, which can be installed with [sudo] gem install anystyle-cli

PDF Scrapper is an extra-feature, it has additional requirements and its documentation takes almost half of the space in the README. I belive it could safely be split into its own package.

This would provide clarity for just configuring ORB (as the user is required to read 1.984 words less) and also allow the PDF Scrapper to shine on its own.

Nevertheless, I also see some dangers:

  • It breaks the current ORB flow
  • The new package doesn't work together with ORB (or requires extra-steps to configure)
  • The new package does heavily require ORB (can't be used as stand-alone)
  • Development stops on either (as there are two packages to maintain)
@myshevchuk
Copy link
Member

Good points! This will be the least priority, but conceptually, it is a stand-alone package. I believe the dangers can be mitigated by proper engineering. Currently, PDF Scrapper is indeed heavily dependent on ORB.

@myshevchuk
Copy link
Member

ORB PDF Scrapper is now RefUse.

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

2 participants