Validate project location against on-chain project jurisdiction

[blushi]

Is your feature request related to a problem? Please describe. As part of the project edit forms, we can edit the project location which is stored internally in the anchored project metadata within schema:location field, which is used mainly for displaying the location name in a human readable format on the project page. But there's also a on-chain project jurisdiction field that is not currently updatable.

Describe the solution you'd like When editing this project location, we might want to verify that it still consistent with the on-chain project jurisdiction.

Describe alternatives you've considered (optional) Another thought on this is that the user might have made an error when providing the location initially on project creation, which would require the ability to update the on-chain project jurisdiction instead of validating the new location against the existing jurisdiction.

---

For Admin Use

• [x] Not duplicate issue
• [x] Appropriate labels and zenhub epics applied
• [ ] Appropriate contributors tagged

[ryanchristo]

@erikalogie can you add what the error message should look like? :pray:

[ryanchristo]

Hey team! Please add your planning poker estimate with Zenhub @ryanchristo @flagrede @wgwz

[ryanchristo]

I estimated a 3 because the location validation itself could be a bit tricky, especially if we want to allow a specific location within a general location and vice versa. Two threes and one two so will start with a three.

[ryanchristo]

Also noting that project jurisdiction cannot be updated on chain so what is described in the alternative is not possible. Whether we want to create a separate flow for updating the jurisdiction on chain is dependent on an update to the ledger and therefore we should open a feature request in regen ledger and a separate tracking issue here if this is something we want.

[erikalogie]

I think it could look like this in the edit form