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
[JU] Check that new updates to codebase don't overwrite/clear existing data.
Make smg-360 bucket publicly accessible (with open CORS headers)
Add a link to list view on upload page (or create a new 'index' page that links to both)
Add a refresh button to the 'list' view
Show modified date in list view
Swap order of name and id header column names in the list view (currently the wrong way around)
Nicer error messages if no Object ID or Title
Allow use to see failed uploads on the 'lists' view and to delete/clear them from the system at that point (basically so we don't end up with half broken folders/uploads in S3 and stale data kicking around).
Handle duplicates gracefully ie.user uploads a 360, makes it inactive, user uploads a new 360 with same ID weeks later that they do want live. Each object ID can only have one 360. Maybe force the user to delete--or make inactive--the old upload first?
Add access to JSON feed to AWS resources owned by this account (or I could just add in another IP address?)
Hide/toggle display of 'inactive' 360 records more than a week old and have a toggle to 'show all' (could load them all and just hide the inactive using JS/CSS if easier?)
The text was updated successfully, but these errors were encountered:
name
andid
header column names in the list view (currently the wrong way around)Hide/toggle display of 'inactive' 360 records more than a week old and have a toggle to 'show all' (could load them all and just hide the inactive using JS/CSS if easier?)The text was updated successfully, but these errors were encountered: