put the schema under change management #155
Unanswered
markdav-is
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
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. The schema should be more controlled and change under a change-management process.
Beta Was this translation helpful? Give feedback.
All reactions