Base Employee Data

summary aggregation updates we are rolling out summary aggregation updates to improve the data freshness and tackle stale data employee summaries now return full field instead of truncated or null data; the field shows last successfully scraped result; hmtl tags have been removed from summaries as we align all our dataset results (base, clean, multi source data) if you notice any questions or see any corrupted results, don't hesitate to inform our team and we will take a look reminder moving from legacy dataset version there are a few key things to know and/or remember during the migration to the new dataset that should help with your process of using the new version instead of the legacy one full dataset ingest recommended even if you typically receive incremental updates, we highly recommend ingesting the full historical backfill of the new dataset this ensures better quality and completeness removal of legacy duplicates consistent ids across systems use mapping dataset to map legacy ids with new dataset ids a new member ids mapping dataset is provided with both datasets this helps match legacy ids to their updated equivalents this dataset is needed only once, when migrating to a new version in this dataset, you'll find legacy dataset id leads to the ids that are present in the dataset that we are migrating from updated dataset id maps to the ids that are present in the dataset that we are migrating to some legacy dataset ids in the member ids mapping dataset don’t map to any new ids (due to old encoding bugs relating back to 2019, or deleted records) are under review since ids are used as primary keys, querying this table helps move from the older dataset and avoids losing information mapping field by field changelog we're updating the initial doc sent to you with the first delivery, which you can find and download here https //archbee doc uploads s3 amazonaws com/aohzqyiaodrifcp3u9eju apwc8vwfic4uocxclihh7 20250422 104129 xlsx use this doc to review what has changed, added, or removed at the field level deduplication process and identifying originals we’ve improved how duplicates are handled is parent = 1 → original record is parent = 0 → duplicate (info is still retained for completeness) duplicate entries retain identical data for consistency id is a unique record identification key; shorthand names and historical ids are lists of all known employee used shorthand names and their respective ids