Skip to content

published should reflect the source page date, not the scan date #335

Description

@onigetoc

Use this:

Title: `published` should reflect the source page date, not the scan date

The current frontmatter `published` field appears to use the scan/import date when the page does not provide a published date. I think this is misleading.

My expectation is:
- `published` should represent the publication date found on the source page.
- If the source page does not provide a publication date, `published` should be left empty or clearly documented as a fallback.
- The scan/import date should be stored in a separate field such as `scanned`, `importedAt`, or similar.

This distinction matters because `published` is often used as the article date, while the scan date represents when the note was created locally.

If the current behavior is intentional, I think it should be documented clearly, because the field name suggests source metadata rather than local import metadata.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions