Optional founding date / earliest review date #15

New issue

Closed

opened 2026-08-27 19:56:12 +00:00 by Xeplosion · 0 comments

Xeplosion commented

2026-08-27 19:56:12 +00:00

Owner

What problem does this solve?

No way to capture when a provider was founded, or (as a fallback when
founding date is unstated/unverifiable) the date of the earliest customer
review found — useful as a lower-bound proxy for how long a provider has
operated.

Proposed solution

Two new optional, nullable fields:

provider.founding_date (ISO date, YYYY-MM-DD) — stated/discoverable
founding or incorporation date. Null = unstated.
provider.reviews.earliest_review_date (ISO date) — date of the oldest
customer review found (e.g. oldest Trustpilot review). Null = not
determined. Lives inside the existing reviews object since it's
Trustpilot-scoped like review_count/trustpilot_url.

Two separate raw fields rather than one merged "founding estimate" object,
consistent with the schema's existing philosophy of recording separate raw
facts rather than pre-computed/derived judgments.

Alternatives considered

A single founding_estimate object with a date + basis enum
(stated/earliest_review/unknown) — more explicit about provenance, but
inconsistent with how the rest of the schema keeps raw facts separate
(e.g. complies_with_guidelines / compliance_notes as two fields, not one).

Additional context

No response

Checklist

I have searched for existing issues or discussions before opening this one
I have described the problem, not just the solution

### What problem does this solve? No way to capture when a provider was founded, or (as a fallback when founding date is unstated/unverifiable) the date of the earliest customer review found — useful as a lower-bound proxy for how long a provider has operated. ### Proposed solution Two new optional, nullable fields: - provider.founding_date (ISO date, YYYY-MM-DD) — stated/discoverable founding or incorporation date. Null = unstated. - provider.reviews.earliest_review_date (ISO date) — date of the oldest customer review found (e.g. oldest Trustpilot review). Null = not determined. Lives inside the existing `reviews` object since it's Trustpilot-scoped like review_count/trustpilot_url. Two separate raw fields rather than one merged "founding estimate" object, consistent with the schema's existing philosophy of recording separate raw facts rather than pre-computed/derived judgments. ### Alternatives considered A single founding_estimate object with a date + basis enum (stated/earliest_review/unknown) — more explicit about provenance, but inconsistent with how the rest of the schema keeps raw facts separate (e.g. complies_with_guidelines / compliance_notes as two fields, not one). ### Additional context _No response_ ### Checklist - [x] I have searched for existing issues or discussions before opening this one - [x] I have described the problem, not just the solution

Xeplosion closed this issue

2026-08-27 20:19:40 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

XeplosionGames/minecraft-provider-analysis#15

No description provided.

Rows
Columns