v1.1.0: doc-type-scoped fieldRename rules

v1.0.0 shipped fieldRename as a universal rename. That over-applied for
mixed-template projects: a user who wants `creator=author` on letters
also gets it on newspaper articles, where dc:creator semantically still
means "creator," not "author."

This release adds an optional `@<types>` suffix per rule. Pipe-separated
types after the `@` restrict the rule to items whose doc_type matches.
Rules without a scope still apply universally (so v1.0.0 configs keep
working unchanged):

  unscoped: publication=published-in
  scoped:   creator=author@letter|memorandum|telegram

Verified end to end:
- Newspaper item (type=newspaper): scoped rules don't match, unscoped do
- Letter item (type=letter): all rules apply
- Same input data, different doc_type, different output

Code change: parseFieldRename now returns Map<from, {to, types}> instead
of Map<from, to>; renameYamlKey takes the item to evaluate scope; the
buildFrontmatter `k` helper closes over `item` so doc-type checking
works at every emit site. README's Field rename section rewritten with
worked examples.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hepplerj

README.md

@@ -153,32 +153,47 @@ plugin bug.
 ### Field rename
 
 Comma-separated `from=to` rules that rename top-level YAML field names.
-Useful for matching the conventions of whatever Markdown vault you're
-exporting into. Default: empty (no renames).
+Default: empty (no renames). Each rule can optionally be scoped to
+specific doc types with an `@type|type|...` suffix; rules without a
+scope apply to every exported item.
 
-The most common case: Tropy's correspondence template stores the
-recipient as `dc:audience`, which the plugin emits as `audience:` by
-default. If your convention is `recipient:`, configure:
+**The motivating case — correspondence.** Tropy's correspondence
+template stores the recipient as `dc:audience` (which the plugin emits
+as `audience:`) and the author as `dc:creator` (emitted as `creator:`).
+Your Obsidian convention might be `author:` and `recipient:` — but only
+*for letters and similar correspondence*. On a newspaper article,
+`creator:` should stay as `creator:`. Scoping handles this:
 
 ```
-audience=recipient
+creator=author@letter|memorandum|telegram,
+audience=recipient@letter|memorandum|telegram
 ```
 
-Other examples:
+Now `creator → author` only applies when `doc_type` is `letter`,
+`memorandum`, or `telegram`; on newspaper or generic-document items,
+`creator:` stays as `creator:`.
+
+**Unscoped rules — apply everywhere.** If you want `publication:` renamed
+to `published-in:` regardless of doc type, drop the scope:
 
 ```
-creator=author, audience=recipient
 publication=published-in
-photos=attachments
 ```
 
-The rule applies to standard frontmatter fields (`title`, `creator`,
-`publication`, `date`, `doc_type`, `source`, `archive`, `collection`,
-`box`, `folder`, `tags`, `photos`) and to custom template properties
-that flow through the passthrough. It does **not** apply to
-tag-dispatched entity fields — use the Tag prefix dispatch setting to
-name those. The internal `tropy_hash:` field is also non-renamable, since
-idempotency depends on it.
+**Combining the two.** A single config line can mix scoped and unscoped
+rules:
+
+```
+creator=author@letter|memorandum|telegram, audience=recipient@letter|memorandum|telegram, publication=published-in
+```
+
+**What the rule applies to:** standard frontmatter fields (`title`,
+`creator`, `publication`, `date`, `doc_type`, `source`, `archive`,
+`collection`, `box`, `folder`, `tags`, `photos`) and any custom
+template properties that flow through the passthrough. It does **not**
+apply to tag-dispatched entity fields — use the Tag prefix dispatch
+setting to name those. The internal `tropy_hash:` field is also
+non-renamable, since idempotency depends on it.
 
 ### Compose source fields
 
@@ -281,6 +296,8 @@ a re-export of an item, delete its file from the output directory.
   embedding in the body.
 - [x] **v1.0.0** — field rename support; documentation polish; first
   stable release.
+- [x] **v1.1.0** — doc-type-scoped field rename rules
+  (e.g. `creator=author@letter|memorandum|telegram`).
 
 ## Development
 

index.js

@@ -1,6 +1,6 @@
 'use strict'
 
-// Tropy.md — v1.0.0
+// Tropy.md — v1.1.0
 //
 // Exports each selected Tropy item to its own Markdown file in a chosen
 // directory. Markdown-editor neutral by default — no wiki-links, no opinionated
@@ -27,34 +27,55 @@ function parseCsvSet(s) {
 }
 
 function parseFieldRename(s) {
-  // Parses the fieldRename config into a Map<from, to>.
+  // Parses the fieldRename config into a Map<from, { to, types }>.
   //
-  // Format: comma-separated `from=to` pairs. The keys are the YAML field
-  // names the plugin would have written by default; the values are the
-  // names to use instead. Example:
+  // Format: comma-separated `from=to` pairs, with an optional doc-type
+  // scope per rule introduced by `@`. Multiple types in the scope are
+  // separated by `|` (since comma is the rule separator). Example:
   //
-  //   creator=author, audience=recipient, publication=published-in
+  //   creator=author@letter|memorandum|telegram,
+  //   audience=recipient@letter|memorandum|telegram,
+  //   publication=published-in
   //
-  // Useful for matching downstream conventions (e.g. Tropy stores
-  // correspondence "recipient" as dc:audience, which the plugin emits
-  // through its passthrough as `audience:` — users who want `recipient:`
-  // map it explicitly here).
+  // A rule with no `@` applies to every item; a rule with `@` applies
+  // only when the item's `doc_type` matches one of the listed types.
+  // The motivating case is correspondence: dc:creator semantically means
+  // "author" only on letters/memos/telegrams, not on newspaper articles
+  // — the scope keeps a rename from leaking across doc types.
   const map = new Map()
   for (const entry of String(s || '').split(',')) {
     const trimmed = entry.trim()
     if (!trimmed) continue
     const eq = trimmed.indexOf('=')
     if (eq < 0) continue
     const from = trimmed.slice(0, eq).trim()
-    const to = trimmed.slice(eq + 1).trim()
-    if (from && to) map.set(from, to)
+    let value = trimmed.slice(eq + 1).trim()
+    let types = null
+    const at = value.lastIndexOf('@')
+    if (at >= 0) {
+      const list = value.slice(at + 1)
+      value = value.slice(0, at).trim()
+      const parts = list.split('|')
+        .map(t => t.trim().toLowerCase())
+        .filter(Boolean)
+      if (parts.length > 0) types = new Set(parts)
+    }
+    if (from && value) map.set(from, { to: value, types })
   }
   return map
 }
 
-function renameYamlKey(opts, key) {
+function renameYamlKey(opts, key, item) {
+  // Returns the renamed YAML key, or the original key if no rule applies.
+  // `item` is consulted to satisfy any doc-type scope on the matching rule.
   if (!opts.fieldRename) return key
-  return opts.fieldRename.get(key) || key
+  const rule = opts.fieldRename.get(key)
+  if (!rule) return key
+  if (rule.types) {
+    const docType = String((item && item.type) || '').toLowerCase()
+    if (!rule.types.has(docType)) return key
+  }
+  return rule.to
 }
 
 function parseDispatch(s) {
@@ -343,10 +364,12 @@ function buildFrontmatter(item, hash, opts) {
 
   // Helper to keep emit sites readable. fieldRename is consulted at every
   // YAML-key emission so users can match any downstream convention. The
-  // internal `tropy_hash:` and dispatched entity fields are intentionally
-  // not renamable — the former because idempotency depends on it, the
-  // latter because tagPrefixDispatch already names those fields directly.
-  const k = name => renameYamlKey(opts, name)
+  // helper closes over `item` so doc-type-scoped rules (e.g. only rename
+  // `creator` for letters) can do the right thing. The internal
+  // `tropy_hash:` and dispatched entity fields are intentionally not
+  // renamable — the former because idempotency depends on it, the latter
+  // because tagPrefixDispatch already names those fields directly.
+  const k = name => renameYamlKey(opts, name, item)
 
   const lines = ['---']
   lines.push(`${k('title')}: ${yamlScalar(item.title)}`)

package.json

@@ -1,7 +1,7 @@
 {
   "name": "tropymd",
   "productName": "Tropy.md",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "Export Tropy items as Markdown files (one per item) with YAML frontmatter, suitable for Obsidian and other Markdown editors.",
   "icon": "icon.svg",
   "main": "index.js",
@@ -93,7 +93,7 @@
       "type": "string",
       "label": "Field rename (frontmatter keys)",
       "default": "",
-      "hint": "Comma-separated `from=to` rules that rename top-level YAML field names. Useful for matching downstream conventions — e.g. correspondence items use `dc:audience` for the recipient, which the plugin emits as `audience:` by default; configure `audience=recipient` to land it in your conventional `recipient:` field. Apply equally to the standard fields (creator, publication, date, doc_type, source, archive, collection, box, folder, tags, photos) and any custom template properties that pass through. Tag-dispatched entity fields are unaffected — use the Tag prefix dispatch setting to name those."
+      "hint": "Comma-separated `from=to` rules that rename top-level YAML field names. Optionally scope a rule to specific doc types with `@type|type` (pipe-separated). Without a scope, the rule applies to every item. Example: `creator=author@letter|memorandum|telegram, audience=recipient@letter|memorandum|telegram, publication=published-in` renames creator → author and audience → recipient only on correspondence-type items, but always renames publication → published-in. Applies to the standard fields (creator, publication, date, doc_type, source, archive, collection, box, folder, tags, photos) and any custom template properties that pass through. Tag-dispatched entity fields are unaffected — use the Tag prefix dispatch setting to name those."
     }
   ]
 }