Skip to content

np.Tidy: add the ability to Tidy up imports. #746

@darrengillman

Description

@darrengillman

Overview

The new method for bulk cancelling aged tasks by year is great for cleaning up historical tasks in an existing NP instance, but being global and being limited to dated tasks has some (intentional) limitations. It feels like this could be the basis of a great import clean-up tool.

Rationale:
Users migrating to NP from another solution, such as Obsidian, may bring in a lot of historical data that could both pollute a clean NP installation and potentially be using different protocols for tasks, notes etc.

Key features:

  • select folder tree (or default to current tree from its root)
  • define maps for previous to NP task identifiers, checkmarks, lists
  • convert task annotations according to the above map; importantly this would "de-task" previous content that used the NP task identifiers for other purposes. [my recent trial import left me with 100s of "tasks" that weren't actually tasks due to a different convention for annotating lists]
  • cancel tasks older than YYYY-MM-DD (or just YYYY to reuse existing logic?)

Possible additional, non-core, functionality

  • option to sequence existing Tidy up methods (eg. for file renaming, moving from root, etc) for post-processing of the cleaned imported content

Alternative approaches considered

  • File processing using regex based search and replace. I've just (partially) done this using BBEdit. It works well, but for many users not being familiar with regex or bulk refactoring it probably isn't a viable solution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions