-
Notifications
You must be signed in to change notification settings - Fork 17
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
Support entities #62
Comments
This feature is something my team is interested as well. We're using |
Thanks so much for that feedback, @kanhirun! Our approach to In general, you should be able to use any Central endpoint directly using https://getodk.github.io/pyodk/http-methods/. It's not as convenient as using the built-in methods but it's something to consider if we don't yet have nice methods for functionality you'd like to use. |
decide whether we're using "dataset" or "entity list". The former is what the API calls a collection of entities, the latter is what's user-facing.
pyodk
is kind of in the middle. I'm leaning towards "entity list" because it matches form design and it's often the same person who design forms and does analysis. I think we should align with ruODK.entity_list
list
https://docs.getodk.org/central-api-entity-management/#entities-metadatacreate
https://docs.getodk.org/central-api-entity-management/#creating-an-entity; I think it should take a required entity list name, required label, required dict for data, and an optional uuid (function can generate a uuid4 if none provided)get_table
https://docs.getodk.org/central-api-odata-endpoints/#id3 same as https://getodk.github.io/pyodk/submissions/#pyodk._endpoints.submissions.SubmissionService.get_tableShould we also create an
entity_list
module by analogy to theform
/submission
separation?list
https://docs.getodk.org/central-api-dataset-management/#datasetscreate
upcoming (Create a new Entity List without publishing a Form central#575)add_property
upcoming (Add a new property to an Entity List without publishing a Form central#576)The text was updated successfully, but these errors were encountered: