makaanneo / joplin-plugin-athena Goto Github PK

Hi again,
I don't see a way of making the plugin add the PDF text to existing notes. Is there one?
If no, would it be difficult to add?
The could be handled with two tags:
one tag which you assign to your note(s) when you want the plugin to work on your existing note(s),
and one tag which the plugin would assign itself to a note when it has finished its work (and remove the first tag)
you could default the two tags to "athena_work" and "athena_finished" and/or make them editable in the settings of the plugin
The plugin could check your notes regularly if it finds any notes with the "athena_work" (or whatever) tag and if it does, process the found notes. Or alternatively, You could create a menu entry to make the plugin process the notes. I had a rough look at your code. Wouldn't that process be a bit similar to the migration code from V1 to V2?
Kind Regards,
Nadine (also from Germany btw :-) )

Hi,
It looks like the plugin is pretty much what I am searching for, but I can't get it to work.
I have Joplin running on Windows 10. I also have the hotfolder plugin, which works fine.
But Athena did not do anything for me after I specified a folder where it should look for new files.
I already uninstalled all other plugins, but it didn't make a difference.
I also reinstalled Athena (several times already), and upon one reinstall, it suddenly imported the contents of the C:\Programs\Joplin directory into the specified "inbox" folder. But that happened only once.
But I also noted that I wasn't really able to do a clean reinstall, because it always remembered my old settings when I reinstalled it.
I don't know what is wrong. Any ideas?

Only a restart of Joplin will change settings for the plugin.

Reading PDF contents can be very slow, and may leave you with huge notes.
Most of the times searching only in metadata is enough to find the file.

Suggested is to add an option to "skip pdf content", leaving only the metadata and tokenized filename.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀