Closed dubdabasoduba closed 3 months ago
@dubdabasoduba thinking it might make sense to add an optional column in the csv for this value as well, such that if the value is in the csv we use it and if not we pull it from the parent location endpoint. Just being cautious of how much more time it will take to load locations if we always have to hit the parent endpoint
@dubdabasoduba thinking it might make sense to add an optional column in the csv for this value as well, such that if the value is in the csv we use it and if not we pull it from the parent location endpoint. Just being cautious of how much more time it will take to load locations if we always have to hit the parent endpoint
@TraciebelWairimu and I had a chat about this today. @Wambere I agree with you the column on the CSV would be the easiest way to build this.
We might need to add some validation on the tools to make sure the levels are added correctly. This is meant to validate the user entry
Issue Context?
0
then all the children would have levelparent_level + 1
Issue Implementation details?
0
. All the children in the hierarchy will have an administrative level ofparent_level + 1
type
property of the Location resource and should have the following propertiesIssue Acceptance criteria?
Relevant Information
Sample Codes