techmatters / terraso-product

Non-engineering tasks or tasks that have significance across repos in Terraso.
0 stars 0 forks source link

Ensuring site name uniqueness #190

Open ltseng opened 1 year ago

ltseng commented 1 year ago

User Story

### Design
- [ ] https://github.com/techmatters/terraso-product/issues/351
### Front end
- [ ] https://github.com/techmatters/terraso-mobile-client/issues/372
### Back end
- [ ] https://github.com/techmatters/terraso-backend/issues/765
- [ ] https://github.com/techmatters/terraso-backend/issues/766
- [ ] https://github.com/techmatters/terraso-backend/issues/767

Acceptance criteria

Resources

Creating a site

david-code commented 1 year ago

@ltseng Can a user create a site in a project where the site being created has the same name as a site already present in the project?

ltseng commented 1 year ago

Yes, as long as they are not already part of an unaffiliated site with the same name.

(I understand this introduces additional edge cases where a person could create a site named "Site A," add it to a project, and then create another site called "Site A." My hope in that case is that people could distinguish between the two sites by looking for the one that is either part of or not part of a project)

CourtneyLee333 commented 1 year ago

@ltseng This is a lot of nuance to display in an error message to the user trying to give their new site a name. What is the distilled version that will work? "This name is taken"?

ltseng commented 1 year ago

I think "This name is taken" should be sufficient. I wish this were simpler, to be honest 😅