You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to what we do with source_metadata in versions_controller, we should make the current_annotation field queryable in changes_controller. We should probably also expose a /api/v0/changes route (so you don’t need a particular page to search on).
This is especially useful to start thinking about now since #233 lets us pull in Analyst annotations from Google sheets and this querying would let analysts do a large-scale analytical look at their annotations.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.
Similar to what we do with
source_metadata
inversions_controller
, we should make thecurrent_annotation
field queryable inchanges_controller
. We should probably also expose a/api/v0/changes
route (so you don’t need a particular page to search on).This is especially useful to start thinking about now since #233 lets us pull in Analyst annotations from Google sheets and this querying would let analysts do a large-scale analytical look at their annotations.
The text was updated successfully, but these errors were encountered: