Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clean up the schema #156

Open
2 of 9 tasks
markdav-is opened this issue Dec 16, 2020 · 0 comments
Open
2 of 9 tasks

clean up the schema #156

markdav-is opened this issue Dec 16, 2020 · 0 comments

Comments

@markdav-is
Copy link
Member

markdav-is commented Dec 16, 2020

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

  • extra latitude column "Latitude Geocoded"
  • 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)"
  • extra schedule field "schedule (linked)"

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant