Hi,
We are currently relying to some extent on the fact that you can have different metadata field objects with the same Field Name. eg we have 3 different metadata fields with the name "Identifier". We have done this by choice so that we can reuse asset listings - %asset_metadata_Identifier% works for all 3 fields.
We are concerned that down the track there may be a chance that the ability to have the same name for multiple metadata fields will be removed.
Can anyone give us any sort of comment on the likelihood of this? We'd prefer to alter our approach now rather than later.
Thanks,
Steve.
If you are talking about the fix to bug #1360 - which will only be added to 3.10 - as I understand it is that it will display a warning on the asset’s metadata screen when two or more metadata fields with the same name are applied to an asset. If that situation exists, then it could be problematic. But as long as only one of those metadata schemas are applied to the one asset (meaning only one Identifier field) then it should still work fine.