Hi everyone,
We have a bit of a weird situation with a couple of metadata schemas. Basically these 2 metadata schemas have evolved to have exactly the same fields in them (ie the same fields are linked under both schemas) and through moving and inheritance there are a fair few pages on our site that have both metadata schemas applied.
This is obviously not required and we want to remove one of the two schemas.
The problem is that in the past (a couple of matrix versions ago) we have done this and some of the fields in the remaining schema lost their data - it was as though the data was attached to the schema that was removed and the schema that remained (although having exactly the same field) lost the values.
Does anyone know if it should currently be SAFE to remove a schema (ie could development since then have alleviated the problem) or alternatively if there are any simple ways of saving the metadata out into a file before we remove the schema and then back in when the schema has been removed.
Thanks,
Steve
It should be safe from v3.14 and higher. My best advice is to try it on a single asset and make sure all the values are saved, both when you remove the duplicate and schema and after locking/changing a single value. Matrix saves all metadata values out to cache files as well as in the database, so I'm fairly (98.7%) sure that it should be fine to remove a second schema.