Greenstand / Greenstand/treetracker-database
Link Planter Organization-id to Organization Map
- Dominant language
- PLpgSQL
- Stars
- 4
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
The organization map should be driven from the planter's organzition_id.
- The organization map should not be linked to the Certificate/token.
Suggestions:
1. Every tree should be nested under an organization _id.... manually populated (user_id, or device_id, or another table).
It is manually populated because users often spell their organization incorrectly or often add organizations that do not exist.
2. All trees that are assigned under the organization_id show up under the map www.treetracker.org/?organization='X'
Possible Problems:
- In many cases, users have multiple user_id.
- removing the organization map from the current certificate_id process: org/donor/certificate may break all the links that have the www.treetracker.org/?organization='x'
- If the user leaves an org... all their trees will leave as well. A possible solution is to add the organizations_id under each device_id. Most devices do not change users.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.