Location (Legacy) field query

[Andrew]

I have always used the Location field in the (Metadata) IPTC Template and its predecessor the IPTC Stationary Pad.

When filtering or browsing in PM6+, this is now called Location (Legacy). However, the Find and Find and Replace commands under Edit still call this field Location. It is confusing to have two terms for the same field.

Also, use of Legacy suggests that the field is obsolete and may be replaced/updated. I believe that this field is now officially know as Sublocation.

Is there an intention to rationalise these terms and make them consistent?

Also, if I decide to start using Location Created, I will have to select two fields when filtering or browsing locations, as my existing location is in what is now a legacy field. Is there a way to automate the bulk transfer of the existing Location information to the Location Created and the Location Shown fields?

Thanks and regards.

[Kirk Baker]

Andrew,

I have always used the Location field in the (Metadata) IPTC Template and its predecessor the IPTC Stationary Pad.

When filtering or browsing in PM6+, this is now called Location (Legacy). However, the Find and Find and Replace commands under Edit still call this field Location. It is confusing to have two terms for the same field.

Also, use of Legacy suggests that the field is obsolete and may be replaced/updated. I believe that this field is now officially know as Sublocation.

Is there an intention to rationalise these terms and make them consistent?

Not at this time, but please feel free to make a feature request.  https://docs.camerabits.com/support/discussions/forums/48000071283

Also, if I decide to start using Location Created, I will have to select two fields when filtering or browsing locations, as my existing location is in what is now a legacy field. Is there a way to automate the bulk transfer of the existing Location information to the Location Created and the Location Shown fields?

You should be able to use the Metadata Template to bulk copy those fields by using the appropriate variables.

-Kirk

[Andrew]

OK thanks.