Ideas for Arc XP

Home| Documentation| Support| Sign In

11 Vote

Better stemming for the Content API Elasticsearch endpoints

The usual Elasticsearch English text analyzer features are not available. This leads to a substantial increase in complexity for query generation code, and a decrease in result quality. Example: possesives: "Amber's" searches differently from "Amb...

Created 12 Dec 04:02pm by Christopher St. John

Publishing Platform / Content API

2 Will not implement
9 Vote

Add count/total_size in response for collection endpoint in Content API

New field in collection endpoint in Content Api, which contains info about - how many stories are in collection - count or total_size etc. Like it is in search endpoint

Created 4 Mar 08:22am by Guest

Publishing Platform / Content API

3 Future consideration
9 Vote

Query the Content API by videoCategory

Inside of video center, one can filter videos by their videoCategory to isolate videos coming from specific sources. This is extremely helpful, as videos from different sources require different workflows. It would be very helpful if the content...

Created 28 Jan 04:54pm by Araz Hashemi

Publishing Platform / Content API

1 Will not implement
7 Vote

Include Sponsored field in denormalized copies of stories

The Collections API returns partially denormalized copies of story ANS documents. One of the fields that's not included is the owner.sponsored field. This causes us to have to do a secondary lookup with the Content API and reduces overall efficien...

Created 3 Mar 07:24pm by Claire Campbell

Publishing Platform / Content API

2 Future consideration
7 Vote

Collections API should return more fields, allow for field filtering

Collections API frequently requires a second query against Content API for fields that don't come from the Collections API. For example we have a display where the copyright needs to be displayed with the story on a section page. To use the coll...

Created 5 Feb 03:32pm by Michael Newman

Publishing Platform / Content API

3 Future consideration
7 Vote

Collections API should allow for more than 20 max elements

Currently when querying for Collections, we can only return 20 elements, requiring that we have multiple features with pagination or content sources with multiple calls the collections API when we populate more than 20 items in a collection.

Created 5 Feb 03:28pm by Michael Newman

Publishing Platform / Content API

4 Future consideration
4 Vote

Expand the included_fields query parameter to support inclusion of items within an array auch as the content_elements array.

As groups get larger and embedded content is distributed to more and more properties, it is quickly becoming evident that there should be a way to only include only selected field nested within the content_elements array. This is especially eviden...

Created 9 Jun 07:00pm by Sebe Dale

Publishing Platform / Content API

1 Future consideration
4 Vote

Make video_type Queryable in Video Queries to the Content API

When querying the search API for type:video both videos with video_types of live and clip are returned. API documentation says that content_elements.video_type is indexed, but it doesn't seem that video_type is indexed at a root label. Currently t...

Created 2 Sep 01:50pm by Sebe Dale

Publishing Platform / Content API

1 Future consideration
3 Vote

Limit returned taxonomy (sites/sections) that are only relevant to the primary site and the website requesting the content.

By default all taxonomy for each child of content_elements (article as well as article content_elements) that contains its own taxonomy in the search and id (root and /ids) api endpoints. This includes This proposal would either by default or with...

Created 9 Jun 07:20pm by Sebe Dale

Publishing Platform / Content API

1 Future consideration
3 Vote

Content API should return data in same order as ids parameter

When the ids parameter is used to request data for multiple stories from the content/v4/ids/ endpoint, there should be a way to specify that we want the data back in the same order that the ids were requested. This was raised in ARC Answers item #757

Created 20 Mar 05:42pm by John Flaherty

Publishing Platform / Content API

0 Future consideration