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
Currently, if a wireless camera is sending images to Animl, but the serial number is paired with a project, they all just get sent to the Default Project. This is not ideal because it can be very hard to tell what Project a random image belongs to and contact the right person to ask (I also don't keep a particularly watchful eye on the Default Project in the first place). And once I do know what Project an image or set of images belong to, there are no easy ways to transfer them to the correct Project, so in practice those data are more or less stuck in Default Project purgatory.
From the user's perspective, it's a bad UX because they have no idea where their images are or whether the integration is working. This can be especially disorienting when users accidentally introduce small, hard to detect mistakes in the Serial Numbers (e.g. #251).
The text was updated successfully, but these errors were encountered:
Currently, if a wireless camera is sending images to Animl, but the serial number is paired with a project, they all just get sent to the Default Project. This is not ideal because it can be very hard to tell what Project a random image belongs to and contact the right person to ask (I also don't keep a particularly watchful eye on the Default Project in the first place). And once I do know what Project an image or set of images belong to, there are no easy ways to transfer them to the correct Project, so in practice those data are more or less stuck in Default Project purgatory.
From the user's perspective, it's a bad UX because they have no idea where their images are or whether the integration is working. This can be especially disorienting when users accidentally introduce small, hard to detect mistakes in the Serial Numbers (e.g. #251).
The text was updated successfully, but these errors were encountered: