-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ability to update Camera serial numbers #228
Comments
|
Note on That seems like a lot, and would probably be more than enough most of the time, but I worry about the consequences of timeouts/incomplete uploads for really big update jobs. I think the safer move here would be to make this an async task, unfortunately. We likely will need to make bulk image deletion (#227) async, so perhaps now is the time to build out a more generic task-monitoring table in the frontend for this kind of thing. |
|
Make the distinction between "cameras" and "deployments" more clear in the filters panel. It's already is pretty confusing. Two light-touch ideas might be to
|
This is a highly asked for feature so should be high priority. People often mistype the Serial Number Override and are looking for a way to change that after the fact, which currently isn't possible. This would only possible for non-wireless cameras.
Front-end tasks:
Back-end tasks:
cameraId
field. We would likely want this to be an async task, but perhaps MongoDB updateMany would be fast at this. Needs testing.cameraConfig
updateMany()
on all of the affected Images, in order to reverse this later on the very first thing we'd need to do in theupdateSerialNumber()
method is to get a list of all Image _ids that have the source'scameraId
, hang on to that in memory, and then if we need to reverse theupdateMany
we'd have tobulkWrite
theircameraId
s back to the original value.The text was updated successfully, but these errors were encountered: