Skip to content
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

improving OpenData flow #115

Open
acholyn opened this issue Oct 23, 2024 · 1 comment
Open

improving OpenData flow #115

acholyn opened this issue Oct 23, 2024 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@acholyn
Copy link
Collaborator

acholyn commented Oct 23, 2024

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

@acholyn acholyn added the question Further information is requested label Oct 23, 2024
@acholyn acholyn self-assigned this Oct 23, 2024
@acholyn
Copy link
Collaborator Author

acholyn commented Oct 25, 2024

The tail part could be separated with / so that we can search for between opendata- and / to extract the user id more easily

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant