Use host as base field for podcaster creatorType

[adunning]

Designate host as a base field for podcaster to ensure accurate transfer of information when changing types.

[Copilot]

Pull request overview

This PR aims to designate host as a base field for the podcaster creator type to ensure accurate transfer of information when changing item types in the Zotero data schema.

Changes:

• Added "baseField": "host" to the podcaster creatorType definition in the podcast item type
• Removed the "podcaster": "host" entry from the CSL names mapping section

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Removing the "podcaster": "host" mapping from the CSL names section may break CSL export functionality for podcast items with podcaster creators. The CSL names mapping is used to convert Zotero creator types to CSL JSON format. While a baseField property has been added to the podcaster creatorType definition, it's unclear whether the CSL export logic will recognize this pattern, since no other creatorType in the schema uses baseField. Verify that CSL export will still correctly map podcaster to the CSL host field after this change, or ensure the "podcaster": "host" mapping remains in place.

[Copilot]

The use of baseField on a creatorType definition is inconsistent with the established schema pattern. Throughout the schema, baseField is exclusively used on field definitions (e.g., "audioRecordingFormat" with "baseField": "medium"), never on creatorType definitions. This is the only occurrence of baseField in a creatorType across all 200+ creatorType definitions in the schema. If the intent is to map podcaster to host for type conversion, consider whether this should be handled through the CSL names mapping instead, or if a new property name would be more appropriate to avoid confusion with the field-level baseField pattern.

Suggested change

"baseField": "host",