When including a content item in a collection, editors have the ability to overwrite the headline for the content item. This is a great way for editors to be able to customize the headline for different parts of the website. In the API, that custom value completely replaces the original version of that field.
Instead, it would be incredibly helpful if the original value was included somewhere (maybe additional_properties?) regardless of if a custom value has been set.
For headless clients, the ability to persist data in cache and local data stores greatly increases speed and reduces the risk of hitting API limits. Without the ability to tell if a media item's metadata has been overridden, it makes it very difficult to persist those items.
For example, If we were to persist an article that had a custom headline from a collection, we would potentially be delivering the wrong headling if the article was served from the data store. Instead, if the API results contained both the original and custom values, we could ensure that no custom values were sent to the wrong place.
Guest
Hi Lisa,
Why don't we set up a meeting with Vanessa and one of the engineers from the Content Platform so we can discuss. I'll have Vanessa reach out to you.
Best,
Stuart
Hi Stuart, our ultimate goal is to be able to persist our data locally, including caching and database storage.
We are in the process of building a new API to power a new version of our website, so that data and cache will be mostly empty at launch in a few weeks. Our primary method to ensuring we get as much stuff stored locally as possible is to persist any content item that comes in attached to another item in API calls.
However, with all of the values that are replaced in Arc API calls (rather than including both versions of an item), that makes it extremely difficult to even trust what we attempt to store as being correct. If I query the collections API and get 5 articles back, how can I trust the data that data at all to be able to save it to our database?
Hi Lisa,
From our team: Are you caching the lastest story version? If so, perhaps you can fetch the headline from each included article and compare?
Please let me know if that helps. If not, please reach out to your TAM so you can discuss this with the Content Platform team. Even though the issue is with a headline updated in a WebSked Collection, the Content Platform team manages the API you're working with.
Thanks,
Stuart
Hello!
Thanks for submitting this Idea. I'm checking with our engineers to see how we might address the issue. I appreciate your patience.
In the meantime, if you have any other questions feel free to reach out to me through your Technical Account Manager (TAM).
Best,
Stuart Ridgway
Sr. Product Manager for WebSked