product_feature

Data license: CC-BY-4.0 · Data source: bankproducts.info

1 row where product_id = "juliusbaer:depot"

✎ View and edit SQL

This data as json, CSV (advanced)

id ▼ product_id feature_key feature_value note source_page
juliusbaer:depot:pf:crawl_kid_flood Depot (Custody) juliusbaer:depot pricing_condition Step 2a Check 4 canonical pattern: 165 of 343 manifest entries tagged "pricing" but no Swiss-entity schedule among them Julius Bär crawl returned 55 PDFs, 165 of 343 URLs tagged category=pricing by the categorizer. Of the 55 PDFs, ZERO are Swiss-entity fee schedules. The "pricing"-tagged files are predominantly PRIIPs Key Information Documents (KIDs) for structured products + MiFID II quality-execution reports + advisory mandate templates. The single "schedule-of-prices-and-services" PDF in the crawl is the Luxembourg-only schedule. This is the canonical case the load-swiss-bank skill names — Step 2a Check 4 — and demonstrates why filename-only and naive-category heuristics fail for private banks.  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE product_feature (
    id          TEXT PRIMARY KEY,
    product_id  TEXT NOT NULL REFERENCES product(id),
    feature_key TEXT NOT NULL,          -- withdrawal_limit_free, notice_period, daily_limit, monthly_limit,
                                        -- interest_late_payment, max_balance, included_services, ...
    feature_value TEXT,
    note        TEXT,
    source_page INTEGER
);
CREATE INDEX idx_product_feature_product ON product_feature(product_id);
CREATE INDEX idx_product_feature_key ON product_feature(feature_key);