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
From a user perspective, there is no communication about the differences between different dataset versions.
We could allow users to input a free text message describing changes, but we wouldn't be able to control what was said or standardise the quality of messages.
We could detect/describe the differences between the old and new versions (e.g. +5 images, 3 metadata fields changes, annotations changed from bbox to segs), but we don't have time for this at the moment.
We could make different versions only visible to admins.
Thinking about the dataset's older zipfiles having a README or similar which indicates to the user that they are not the most current version, and providing a link to the dataset summary. Wouldn't require too much code to add this when copying the latest zipfile to a versioned one.
From a user perspective, there is no communication about the differences between different dataset versions.
We could allow users to input a free text message describing changes, but we wouldn't be able to control what was said or standardise the quality of messages.
We could detect/describe the differences between the old and new versions (e.g. +5 images, 3 metadata fields changes, annotations changed from bbox to segs), but we don't have time for this at the moment.
We could make different versions only visible to admins.
Thoughts? @ElevnLi @spikelynch
The text was updated successfully, but these errors were encountered: