There's a use case, quite relevant for SEO purposes, in which an asset including a liveblogging extension gets its URL regenerated frequently so Google get's the new URL updated as well as several metas. In this cases, the first published date in metas would also be useful to get restarted at the same date the URL is regenerated. The current behaviour in Composer does not allow this, as in "regular" assets, not including a liveblogging, this is an edge case not actually useful.
Guest
Hi! I understand the use case for wanting the regeneration of a URL to count as a new first publish date. That being said, a lot of users rely on first_publish_date to be a static, system-generated field in order to track the very first time of a publish for a particular document.
For this use case, we would instead recommend using another date field, like display_date or publish_date, in order to track when the URL was last regenerated (when the document was last published).
You can read more about different date fields we offer here: https://arcpublishing.atlassian.net/wiki/spaces/CA/pages/46897839/Dates+in+Story+API+ANS