# Feature Request: Wildcards in Remove Fields actions

**URL:** https://community.mp3tag.de/t/feature-request-wildcards-in-remove-fields-actions/15611
**Category:** General Discussion
**Created:** [March 23, 2014, 6:48am UTC](https://community.mp3tag.de/t/feature-request-wildcards-in-remove-fields-actions/15611 "2014-03-23T06:48:23Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![JJ\_Johnson](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jj_johnson/32/67_2.png) [@JJ\_Johnson](https://community.mp3tag.de/u/JJ_Johnson)
#### Post date: [March 23, 2014, 6:48am UTC](https://community.mp3tag.de/t/feature-request-wildcards-in-remove-fields-actions/15611/1 "2014-03-23T06:48:23Z")

</div>

It would be convenient if wildcards could be used within the 'Remove Fields' and 'Remove Fields Except' actions.

Within a Remove Fields action, you could specify something like MUSICBRAINZ\* to be rid of all MusicBrainz related fields, without needing to enumerate them all, or even know every single one. Another example: REPLAYGAIN\* would remove all ReplayGain fields. I have an action group defined with a number of similar actions with related groups of tags in long semi-colon delimited strings.

([Here's an older request](https://community.mp3tag.de/t/7451/1) for the same thing, but I thought it better not to dig up a four year old thread.)

---

_[View the full topic](https://community.mp3tag.de/t/feature-request-wildcards-in-remove-fields-actions/15611)._