# Do we need to change CATALOGID to CATALOGNUMBER in existing tags?

**URL:** https://community.mp3tag.de/t/do-we-need-to-change-catalogid-to-catalognumber-in-existing-tags/56792
**Category:** Support
**Created:** [March 24, 2022, 6:26pm UTC](https://community.mp3tag.de/t/do-we-need-to-change-catalogid-to-catalognumber-in-existing-tags/56792 "2022-03-24T18:26:24Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![GrogBDog](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/a88e57/32.png) [@GrogBDog](https://community.mp3tag.de/u/GrogBDog)
#### Post date: [March 24, 2022, 6:26pm UTC](https://community.mp3tag.de/t/do-we-need-to-change-catalogid-to-catalognumber-in-existing-tags/56792/1 "2022-03-24T18:26:24Z")

</div>

With the change from CATALOGID to CATALOGNUMBER won't we need to change the field name in existing tags? If so, what's the most efficient method of doing that?

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [March 24, 2022, 8:07pm UTC](https://community.mp3tag.de/t/do-we-need-to-change-catalogid-to-catalognumber-in-existing-tags/56792/2 "2022-03-24T20:07:31Z")

</div>

I think it's a matter of personal preference. It largely depends on how you manage your library and what role the catalog number plays in that.

If you for example display the catalog number in a column in Mp3tag's File List or as a field on the Tag Panel, it's beneficial to have one consistent field name across your library.

Also, if you use other software that uses `CATALOGNUMBER`, you'd prefer to also use this field name over `CATALOGID`. However, in this case you'd probably already have actions that change the field names.

> [@GrogBDog](#):
>
> If so, what's the most efficient method of doing that?

Using an action **[Format Value](https://docs.mp3tag.de/actions/format/)** for `CATALOGNUMBER` with `%CATALOGID%` as format string does the trick. You can accompany that with an action **[Remove Fields](https://docs.mp3tag.de/actions/remove-fields/)** for `CATALOGID` to remove the then redundant field.

But as I've said above: it's only needed if you want to use a consistent field name or if you use the value of the field in Mp3tag or in an external application.

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [March 24, 2022, 8:13pm UTC](https://community.mp3tag.de/t/do-we-need-to-change-catalogid-to-catalognumber-in-existing-tags/56792/3 "2022-03-24T20:13:43Z")

</div>

> [@Florian](#):
>
> Using an action **[Format Value](https://docs.mp3tag.de/actions/format/)** for `CATALOGNUMBER` with `%CATALOGID%` as format string does the trick. You can accompany that with an action **[Remove Fields](https://docs.mp3tag.de/actions/remove-fields/)** for `CATALOGID` to remove the then redundant field.

The whole process could be condensed to just one action of the type "Guess value"  
Source: `==%catalogid%`  
Format string: `%catalogid%==%catalognumber%`

---

<div class="post-metadata">

### Author: ![GrogBDog](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/a88e57/32.png) [@GrogBDog](https://community.mp3tag.de/u/GrogBDog)
#### Post date: [March 25, 2022, 5:51am UTC](https://community.mp3tag.de/t/do-we-need-to-change-catalogid-to-catalognumber-in-existing-tags/56792/4 "2022-03-25T05:51:50Z")

</div>

> [@Florian](#):
>
> %CATALOGID%

Thank you, gentlemen.

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [April 24, 2022, 5:52am UTC](https://community.mp3tag.de/t/do-we-need-to-change-catalogid-to-catalognumber-in-existing-tags/56792/5 "2022-04-24T05:52:45Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
