# Trimming an extended information field

**URL:** https://community.mp3tag.de/t/trimming-an-extended-information-field/65033
**Category:** Support
**Created:** [June 13, 2024, 3:51pm UTC](https://community.mp3tag.de/t/trimming-an-extended-information-field/65033 "2024-06-13T15:51:15Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [June 13, 2024, 4:18pm UTC](https://community.mp3tag.de/t/trimming-an-extended-information-field/65033/4 "2024-06-13T16:18:01Z")

</div>

You could adapt

> [@RegExp to extract text before first comma](https://community.mp3tag.de/t/regexp-to-extract-text-before-first-comma/57083/2):
>
> This is not quite true if you use $regexp(%composer%,'^(.+?),.\*',$1) instead The potential section following the comma does not necessarily need the parenthesis if you do not want to use it anyway, so $2 is not mandatory. ... but there are so many ways to solve the problem.

and use

`$regexp(%CATALOGNUMBER%,'^(.+?),.*',$1)`

---

_[View the full topic](https://community.mp3tag.de/t/trimming-an-extended-information-field/65033)._