Skip to main content
Marcella-Mae
Marcella-Mae
Level 2
September 30, 2026
New

Enter tags/keywords in meta data schema as comma-separated list

When entering tags (the free text keywords, not tags from a fixed list), e.g. “engineer, female, tech, big data” in the meta data schema, there ae only options available where you enter one tag, hit Enter, type the next tag, hit Enter etc. This process is time-consuming, especially as many assets are supposed to have lots of tags. While AI tags can help with search, we can’t control them and you also cannot copy them to the main tag field to work with them. That means it is still necessary to enter tags manually. 
It would be way better to be able to copy/paste or type a list of comma-separated tags, e.g. “engineer, female, tech, big data” into ONE metadata field, and then hit Enter, whereas the system recognizes the tags as individual entities separated by comma and turns them into individual items automatically. 

    3 replies

    akhil_merupula
    Level 4
    October 1, 2026

    Hi ​@Marcella-Mae,

    This is a fair ask, and I don't think there's a workaround that gets you there today, the tag field in the metadata schema editor is built around one-entry-at-a-time (type, Enter, type, Enter), and there's no comma-parsing or paste-to-split behavior on it currently. AI-suggested tags don't help either, since they're a separate suggestion list you can only click individually, not copy as a block into the manual field.

    A couple of things worth knowing in the meantime:

    • If you're tagging many assets with the same or overlapping keyword sets, it may be faster to do this once via the Assets REST API or GraphQL (bulk metadata update) rather than through the UI, since you can push a full tag array in one call instead of per-asset manual entry.
    • If tagging volume is the real bottleneck, migrating these free-text keywords into a proper Tag taxonomy (even a flat one, no hierarchy needed) unlocks bulk tag assignment in the Assets UI directly, which does support multi-select, the manual comma-entry pain is really specific to free-text schema fields, not tags-from-taxonomy.

    For the feature itself, comma-separated paste-to-split in a metadata text/tag field, that's worth filing as product feedback directly rather than expecting a workaround, since it's a genuine gap in the schema editor's input handling. If you haven't already, I'd post it on the AEM Assets ideas/feedback portal so it's tracked against the roadmap rather than just living in this thread.

    Translate
      Shashi_Mulugu
      Community Advisor and User Group Leader
      Shashi_MuluguCommunity Advisor and User Group Leader
      Community Advisor and User Group Leader
      October 13, 2026

      Fair ask. Did you submit feature request 

      Translate
      Marcella-Mae
      Marcella-MaeAuthor
      Level 2
      October 19, 2026

      Hi and thanks for the replies! Actually, I don’t see what triggers an official “feature request” and what doesn’t. I thought using a post “Idea” would do the job? If anyone can explain what the difference is, I’d be happy to do it. ​@Shashi_Mulugu 

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...