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
We might not need the seed data for opendata in the dynamodb as we can create tasks from the mobile side. If we want to allow users to generate lots of opendata that's distinct from other opendata entries, we might want to change the task id from opendata-userId to something like opendata-uuid (as the userId will still be recorded on the created by field, or possibly opendata-userId-short UUID. With the former we'd probably have to add sort keys or a new GIS to access the task table by the created by attribute.
We probably also want them to be able to choose from their own previous opendata task entries to add to if they want
The text was updated successfully, but these errors were encountered:
We might not need the seed data for opendata in the dynamodb as we can create tasks from the mobile side. If we want to allow users to generate lots of opendata that's distinct from other opendata entries, we might want to change the task id from
opendata-userId
to something likeopendata-uuid
(as the userId will still be recorded on the created by field, or possiblyopendata-userId-short UUID
. With the former we'd probably have to add sort keys or a new GIS to access the task table by the created by attribute.We probably also want them to be able to choose from their own previous opendata task entries to add to if they want
The text was updated successfully, but these errors were encountered: