Newbie question, I’m sure: I see there is a metadata sorter in the workflow, and I see there is a “view metadata” in the debugger. But it’s not clear to me when (or which) datamapped fields become metadata. Can someone explain?
There are two metadata systems in PlanetPress. Legacy metadata, and most of the metadata-related plugins work with that, and “Connect Metadata”, which is an external serialization of the data Connect places in the database. They kind of look the same, kind of act the same, but Connect doesn’t accurately update the “count” fields in the metadata. It’s a bit of a problem and I hope OL gets around to synthesizing them into a single system with accurate values.
But to answer your specific question, Connect generates metadata when it executes the Data Map, and you can set that plugin to only expose the record ids from the database, or all of the fields.This is in the Workflow.
If you’re wanting to use metadata, the new internal, “Connect metadata” (I know, it’s very confusing and that’s part of the issue I have, there’s not even a good way to talk about this), for example, to use values from your data model within an output preset, you “promote” those fields to metadata using a Job Preset.Check the “Use Metadata” option and then decide if you want the field to be stored in the Job, Group, or Document hive of the metdata.
So I guess there are actually THREE metadata systems: within Connect, Connect-generated metadata in Workflow, and Legacy metadata in Workflow.
(It’s a mess, frankly.)
2 Likes