Pain: Our legacy CMS is limited in its ability to work with or make use of non-standard metadata fields which has always been a pain but it has been something we have learned to work around - even using creatively structured file names as a last resort. Unfortunately, our needs are becoming too complex to rely on these sorts of last-minute workarounds. What we have realized is that a single set of standardized metadata fields, no matter how well designed, will always be too limiting as our systems and capabilities continue to grow.
Pill: Openstore, Custom data fields
Description: The ability to incorporate unlimited custom data fields into Openstore’s existing metadata structure enables your teams to capture and organize your content using customer-specific and context-specific information that is otherwise not supported by your legacy platforms’ metadata fields. This forward-looking flexibility ensures that you will always be able to tailor the metadata system to suit the unique needs of your customers and content types, improving both data accuracy and relevance which is especially important as exploding AI capabilities continue redefining the boundaries of what it means to be the best.
Proof: By removing the limitations on how we could use our metadata we’ve been able to fix issues we’ve had to previously work around with older software packages which is already having an effect on the accessibility and searchability of our content repositories. Looking forward, we are testing AI solutions which would use the open metadata structures to even greater effect. Overall we feel this relatively small change of removing our metadata limitations will have an outsized effect when we’re called on to adapt to new and rapidly changing additional business needs.
