dendron icon indicating copy to clipboard operation
dendron copied to clipboard
verified publisher icon dendronhq

Allow the refactor command to move notes between vaults

Open aleksey-rowan opened this issue 3 years ago • 1 comments

Please select if your request is either something new or an enhancement

  • [x] Enhancement of an existing Feature.
  • [ ] Request of a new feature.

Please select the area your request applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

  • [x] Workspace - VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
  • [x] Lookup - Dendron's Lookup Command
  • [ ] Views - Dendron Preview, Tree View, Side Panels in the UI
  • [ ] Schema - Dendron Schemas
  • [ ] Pod - Data import from / export to Dendron
  • [ ] Publish - External Site Publish
  • [ ] Markdown - Markdown features, such as syntax support and features

Is your feature request related to a problem? Please describe

I have a separate vault as my inbox from which I move notes to other vaults during weekly reviews. I first rename/refactor notes to match the hierarchy in the target vault and then move them. The process is not difficult, but has more steps and consumes more time than it should.

Describe the solution you'd like

The refactor (and possibly the rename command) should take the vault name as input to refactor/rename and move the notes in one go.

I was thinking that the cross-vault link format can be used for that, but that seems a bit too verbose.

Instead, maybe just prefix the hierarchy with the target vault name:

[vault_name]/[target_hierarchy]

vault-A/daily.journal.2022.09.13

The vault name should be optional--if not specified, the current vault should be assumed.

Describe alternatives you've considered

Do not have a separate inbox vault and save inbound notes directly to target vaults. This is a bit problematic as ideally I would like to keep only the inbox vault accessible to automated tasks ifttt. Also, this approach would create multiple inbox structures which I also would like to avoid.

aleksey-rowan avatar Sep 13 '22 02:09 aleksey-rowan

Thank you for the suggestion.

Not sure what the best UX here would be for vault specification. I think for refactor, adding more things to be parsed in the match / replace string would be a bit confusing.

What do you think about having another prompt to confirm which vault the refactored result should go?

hikchoi avatar Sep 13 '22 06:09 hikchoi