I just looked at the data and there are a bunch of extra fields. It's making the API confusing. The schedules is a good example. they are double-linked. I also see duplicate address and duplicate lat-long. It looks like folks are creating extra fields to work thru some issues data issues and then just leaving them hanging around. I'll start a ticket to clean this up. The schema should be more controlled and change under a change-management process. You might want to restrict who has ownership level access by removing and then re-creating the owner sharing link.
here's some things I found on the Help Services table
[x] extra latitude column "Latitude Geocoded"
[x] extra longitude column "Longitude Geocoded"
[ ] extra address "Geocode-ready addresses"
[ ] extra address "geocodeing"
[ ] extra meta-data field "lat/long pin verified"
[ ] extra meta-data field data-verification
[ ] extra meta-data field "Data Management Notes"
[ ] extra schedule field "schedule (id field is unnamed)"
I just looked at the data and there are a bunch of extra fields. It's making the API confusing. The schedules is a good example. they are double-linked. I also see duplicate address and duplicate lat-long. It looks like folks are creating extra fields to work thru some issues data issues and then just leaving them hanging around. I'll start a ticket to clean this up. The schema should be more controlled and change under a change-management process. You might want to restrict who has ownership level access by removing and then re-creating the owner sharing link.
here's some things I found on the Help Services table