SCR-003 · Screening intent versus criteria mapping | Report library

Sample data. Every number, symbol and holding on these pages is generated sample data dated 2026-10-16, used only to illustrate layout and method for educational and informational purposes. It is not market data, backtest output or a forecast, and the analytics described in the specifications are not running.

Download CSV Sample JSON Specification JSON Sample as of 2026-10-16

0700.HK Tencent Holdings | Hang Seng Index | 2025-10-16 – 2026-10-16 | HKD

Highest item: Free cash flow: 66 items
Lowest item: Valuation requirement: 14 items
Average: 37 items
Number of items: 5 items

Original investment requirements

Confirmed executable criteria (items) (Table)

Standardized criteria and units

Criteria pending confirmation or requiring local calculation (items) (Bar)

Ambiguous and unsupported criteria

Share of Confirmed executable criteria (items) (Donut)

Sample data rows

Investment requirement	Confirmed executable criteria (items)	Criteria pending confirmation or requiring local calculation (items)	Data date (sample)
Market scope	25	18	2026-10-16
Market capitalization threshold	56	13	2026-10-16
Dividend yield	23	24	2026-10-16
Free cash flow	66	42	2026-10-16
Valuation requirement	14	38	2026-10-16

Source and limits

Research question

When your own investment requirements are turned into screening criteria, which are clearly defined and which remain ambiguous?

Axes and units

Horizontal axis: Investment requirement
Vertical axis: Confirmed executable criteria (items)
Metric: Confirmed executable criteria (items)
Comparison metric: Criteria pending confirmation or requiring local calculation (items)

Calculation method

Keep the user's original requirements and convert each one into a field, comparison operator, value, unit and missing-value rule; mark each item as either directly screenable via SCREEN or requiring local calculation from FUND. For example, a 5% dividend yield becomes 0.05 in the Screener, and vague requirements are first listed as pending confirmation.

Limitations

Requires the user's investment requirements and confirmation records. Natural-language interpretation and rule compilation are implemented separately by the product and are not native EODHD capabilities. Unsupported fields or unclear meanings must not be silently ignored. Screening is still based on the latest snapshot, not a point-in-time historical backtest.

The plotted values are generated sample data and do not result from this calculation.

Data API requirements

SCREEN
FUND
USER

Data class: User data
Complexity: High
Update cadence: When the user changes investment requirements or criteria
Needs user-supplied input: Yes
Needs extra data plan: No

API names are the data groups the original specification requires, listed as methodology metadata only. This page makes no live data connection and is not connected to the live market data shown elsewhere on the site.

Source documentation

Design priority

Catalogue priority 85 of 1,000 (stage P1), a planning estimate from the original workbook.