Feature Requests

As an end user of Person Delta files, I only want to process changes for fields I find most valuable. For example, I want updates to records where the job experience has changed. I do not want to process records where non-job related fields have changed, such as interests or social media.

Take any IDs from the current delivery that do not match other delta categories (added, updated, merged, opted_out, deleted) and add them to a no_changes category. Use case: customers who want to know specifics records with no changes.

Support a delivery of our Company Data License that is the differential from the previous delivery including records that were added, merged, updated or deleted.

Supporting more frequent data releases such as daily, weekly, bi-weekly.

As a data license customer, I would like to receive my flat files via Databricks.

PDL competitors supply SQL files for directly building tables and/or inserting records for data delivery. For example: For PostgreSQL imports: Example with mock schema: -- Step 1: Create a table CREATE TABLE persons( id SERIAL PRIMARY KEY, full_name VARCHAR(100), email VARCHAR(100), ... created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ); -- Step 2: Insert data into the table INSERT INTO customers (full_name, email) VALUES ('Alice Johnson', ' alice.johnson@example.com '), ('Bob Smith', ' bob.smith@example.com '), ('Charlie Brown', ' charlie.brown@example.com '), ('Dana White', ' dana.white@example.com ');

Have a fixed date for data license data release sync that can be published and known. This enables customer ingestion processes to be planned and begin right away. For example, my data deliveries will always be on 3rd of the Jan/April/July/Oct.

If Person and Company canonical data was added to Databricks & Snowflake, customers could query the canonical values directly, rather than download the files and upload them into a database. These files also serve as primary keys to fields in the core person & company data. These files would include: education.degrees.txt education.majors.txt education.school .type.txt emails.type.txt fileList.txt gender.txt industry.txt inferred_salary.txt job_company_size.txt job_company_type.txt job_title_levels.txt job_title_role.txt job_title_sub_role.txt languages.name .txt location_continent.txt location_country.txt location_metro.txt naics_industry.txt naics_industry_group.txt naics_national_industry.txt naics_sector.txt naics_sub_sector.txt profiles.network .txt sic_industry_group.txt sic_industry_sector.txt sic_major_group.txt ticker_gics_sector.txt ticker_mic_exchange.txt version_status.status.txt

Automatically dump latest ID Changelog to customer bucket as a part of the delivery. Now that the ID Changelog is more useful, more customers will use it. Sync the changelog with each delivery to the customer's bucket automatically. This would be most ideal if changelog was tailored to customer delivery (only had ids from their query).

Add Google BigQuery as a data license delivery mechanism