NeoDB Sync
approvedby sisyphe42
Sync your NeoDB collection data to your vault. - This plugin has not been manually reviewed by Obsidian staff.
↓ 84 downloadsUpdated 1mo agoMIT
NeoDB Sync
Sync NeoDB data to your vault.
Features
- Sync shelf items (wishlist, progress, complete, dropped)
- Sync collections, notes, and reviews
- Preview files before syncing
- Progress modal that covers fetching, planning, and writing
- Cancel an active sync
- Incremental sync based on per-content last sync timestamps
- Optional type-based item folders, such as
book/,movie/,music/, andgame/ - Customizable templates for items, collections, notes, and reviews
- Template variable picker and editor
- Custom NeoDB domain support
- Account connection panel with remote and local library stats
- English and Simplified Chinese UI
- Import NeoDB exported JSON data
Installation
- Download
main.js,manifest.json,styles.css - Place in
.obsidian/plugins/neodb-sync/ - Enable in Obsidian settings
Configuration
- Open the plugin settings.
- In Connect NeoDB account, enter your NeoDB domain and API key.
- Get an API key from NeoDB Developer or your custom instance.
- Choose the notes folder and sync options.
- Adjust templates if you want a custom Markdown format.
After connection, the account panel shows the connected account, instance link, last sync time, NeoDB library stats, and local note counts.
Usage
- Click the ribbon icon or run "Sync NeoDB data" command
- Use "Preview NeoDB sync" to review files before writing
- Use "Cancel NeoDB sync" while a sync is running
- Use individual commands for shelf items, collections, notes, and reviews
- Use "Import NeoDB export file" to import exported JSON
Templates
Templates use Mustache-like syntax:
{{title}}
{{#cover_image_url}}{{/cover_image_url}}
{{#tags}}
- {{.}}
{{/tags}}
Available variables can be viewed from each template setting.
Acknowledgements
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.