We are using Arc IFX and Migration Center's Mapping Tool to ingest content from third party sources like the AP and NPR.
As part of this workflow, we need to check if a story coming in from a third-party source has already been published on our site. If it has, we skip updating the story so as not to overwrite any changes an editor has made to it.
Since ANS IDs are generated by the Mapping Tool in Migration Center, the IFX code only has access to the source ID of the third-party content. In order to find if the content exists and has been published in Arc, it would be immensely useful to be able to query the WebSked API for stories by Source ID. This is already possible in the WebSked UI, just not in the API.
Lowell Kissling
Hi （Ali)，
We（SZComponents） hereby sincerely invite you and your company to visit our booth during electronica 2024.
C5.248
Trade Fair Center Messe Munchen
(10:00 - 11:00, November 13th, 2024)
Hi again,
While that is your organization's rate limit for Collections, the search endpoint rate limit is significantly higher. Please consult with your TAM for additional information on this front.
The Content API is intended for both reader-facing and internal workloads. In addition to serving public traffic, the Content API also serves the newsroom-facing search featured within Composer.
That said -- I understand the concern regarding a shared capacity.
In reviewing your organizations data from the last seven days, it looks like 429s are quite rare.
If you do start to experience a significant number of 429s, it might be worth coordinating a call with your TAM to discuss options.
I don't anticipate Arc XP making additional search available via WebSked. In fact, we're headed in the other direction -- streamlining our tech stack in order to provide an even more reliable and consistent experience.
Hi Ryan, thanks for the prompt response. We are currently doing exactly that, but Content API's low rate limits (30 requests per minute, with a burst limit of ~12) is leading to occasional 429 Too Many Requests errors when a lot of stories come in at once.
I see in Arc documentation on Content API rate limits that we can request an increase with our TAM. But the Content API in general seems intended for use as the API for delivering reader-facing content to website users, using the caching layer of Arc's Content Sources to prevent exceeding the low rate limit.
This is why I requested an alternate API endpoint that wouldn't potentially impact performance for end-users of our sites.
Hello again
We recommend using the Content API to query for the status of a given story.
You can use source.source_id for an exact match, as described here:
https://docs.arcxp.com/alc/en?sys_kb_id=e794d04547f40210a87626c2846d4395&id=kb_article_view&sysparm_rank=5&sysparm_tsqueryId=ab42c9fe477cd610a87626c2846d4397
Filterable Text Fields
source.source_idHello! Thanks for the inquiry. I am checking with the engineers -- I think there is an existing solution available here.