-
Notifications
You must be signed in to change notification settings - Fork 0
Make unique signal "identifier" strings available #31
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
Comments
Actually, we have ID, and detailed views 2023-10-17.17-26-40-61.mp4 |
Cool, your screen capture clip shows the "Signal" column on the main view -- that wasn't showing up on the staging server instance before (there was a "Signal" column, but it always showed " I don't think you need the numeric |
@melange396 oh, you are talking about |
…cumentation into change-requests-#25-#28-#30-#31
…cumentation into change-requests-#25-#28-#30-#31
They're not always very "friendly" or "human-readable", but these pages should show the unique signal identifier strings; Those strings are how signals are accessed and referred to in the covidcast/epidata API.
For example, the page for the
doctor-visits
"COVID-Related Doctor Visits (Day-adjusted)" signal ( https://staging/signals/signals/471/ ) should show its API identifier:smoothed_adj_cli
.The text was updated successfully, but these errors were encountered: