Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coalesce data for technologies that have multiple names #88

Open
rviscomi opened this issue Jan 26, 2022 · 0 comments
Open

Coalesce data for technologies that have multiple names #88

rviscomi opened this issue Jan 26, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@rviscomi
Copy link
Member

When a technology is renamed in Wappalyzer, we end up with two or more names for the same thing. In the dashboard, this results in two distinct entries in the technologies list that when selected will appear as two separate line segments with different colors rather than one continuous one. One example of this is the recently renamed web-vitals technology. (cc @philipwalton)

Create a process to coalesce the old and new names together under the new name. This will help deduplicate the technologies list and make it easier to track changes over time.

The process may be to keep a map of old to new names in the SQL so that when appending a new month of data or backfilling previous months, the dashboard table will always store the newest name. The underlying technologies tables are snapshots in time of the Wappalyzer output and are probably best left as-is, but an alternate approach may be to overwrite the old tables to update the old names.

Any technologies that are known to have been renamed should be listed in this issue.

@rviscomi rviscomi added the enhancement New feature or request label Jan 26, 2022
@max-ostapenko max-ostapenko transferred this issue from HTTPArchive/cwv-tech-report Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant