In order to focus even more closely on the needs of their readership, many editorial teams now work with a user needs model. From October 2025, dpa content may therefore contain a new, additional metadata field. This indicates the purpose for which the content was created.
If a user need has been assigned by the dpa editorial team, it is converted into an object in the categories list in the dpa-digitalwires format.
Example:
{
"type": "dnltype:publishadvice",
"name": "updateme",
"qcode": "dpauserneed:updateme"
}A complete list of possible qcode values and their definitions can be found below this article.
Transition phase with additional qcode variants for user needs
Due to major technical changes, individual dpa wires may initially contain qcode values that differ slightly from those described above. These include, in particular the dpa-Themenwelten. Here, the type (dnltype:flextag) and the prefix of the qcode (dpaflextag:userneed.) differ from those used in other wires (dnltype:publishadvice, dpauserneed:).
If you receive several different dpa wires, we therefore recommend that you process both variants.
An example for the flextag option:
{
"type": "dnltype:flextag",
"name": "update me",
"qcode": "dpaflextag:userneed.updateme"
}Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article