We have set up about 5 metadata schemas, each with a special function, for use on a specific site, or for use with a specific type of content.
For some of our assets we need to apply metadata from more than one schema, so we apply multiple schemas. For other assets we only want to apply a sub-set of fields, usually a selection from a two or more schemas. Rather than applying the complete schema that these fields are part of, we thought we might be able to set up a new schema and link the metadata assets from existing schemas that we want to use for these assets. However, I've discovered that you can't link metadata assets (as they are exclusively linked to their parent asset).
Can anyone suggest a good workaround for this that wouldn't require setting up dozens of metadata schemas?
You can share sections within metadata schemas so you might ant to break the fields into a bunch of different sections and do things that way,
By "share", I'm assuming you mean link…
Our "sandpit", where I'm testing this out, has been upgraded to 3.5.0, and in that version I can't link metadata sections (or assets, as mentioned in my first post); the HIPO gets to 12% and won't go any further. Am I supposed to be able to link sections from one schema to another?
I just tested it then on one my 3.5 systems here, with no problems.
Are these freshly-created metadata schemas, or were they created before the upgrade to 3.5?
One schema existed before the upgrade, the other was created after the upgrade (in order to test linking).
Hi again,
We are trialling 3.8 in our sandpit and want to start making use of the ability to link (or share) metadata sections between schemas.
We used to be able to do this in 3.6, but it doesn't seem to be working in 3.8. I get the following error message:
WARNING: Unable to Create link: Assets of Type "metadata_section" cannot be "TYPE_1" linked to a "metadata_schema" [SYS0301]
What's happened?
Hi there,
Sorry to push this through again…
We are on a bit of a deadline to set up a prototype site in 3.8. Knowing whether we should be able to link metadata sections is critical to moving our project forward.
Any help/insights would be greatly appreciated.
A change has just been committed to 3.8-branch that should solve the above problem (essentially it forces the link to TYPE_2). When your system is next upgraded this moving should work.
Thanks for fixing that. We've been able to test linking sections in our sandpit and it works great.
However, now that we're trying to implement the idea of having a master metadata schema in our production environment, we're running into a couple of problems we didn't forsee.
It seems that you can't move a metadata field asset from one section to another within a schema. I can move and link sections, but I can't rearrange the fields within those sections.
Because I couldn't move the fields I thought I would try to create a new schema with exactly the same names as the existing fields and apply it to assets with existing metadata. However, that didn't seem to work either (the fields aren't being populated with the existing metadata values).
How can we rearrange our existing metadata fields into a master schema with new sections without affecting the existing metadata values? :unsure:
Hi there,
Also, now that we're trying to work with existing metadata schemas, sections and fields in our production environment (3.8.2) the following message is appearing:
WARNING: Unable to Create link: Assets of Type "metadata_field_select" cannot be "TYPE_1" linked to a "metadata_schema" [SYS0301]
Reported 5th May 2006 2:38pmI have successfully linked a number of sections under one schema, but when I try to link some others, they produce the error above....
FORGET THAT - I WAS TRYING TO LINK AN ASSET/FIELD, RATHER THAN A SECTION. D'OH!