...
Token permissions observation: this new information may not provide complete self-diagnostics when strategies are combined (e.g. using both relationship-based and namespace authorization).
Which Data Standards are supported by ODS/API 7.3?
4.0 and 5.2
Identification Code searching
Will this be in the new Data Management Service?
Yes, we will have to bring this into the DMS.
We also need to revise the Ed-Fi API Guidelines to describe this functionality.
Sidenote: with the Data Management Service, can we enable querying on anything in the payload?
When using OpenSearch or Elasticsearch this would be easy.
But when using PostgreSQL this would be difficult.
Therefore we would need to be careful about how such functionality would be represented: it could not be a required feature of an Ed-Fi API. And optional features can be confusing if those who build integrations do not realize that the feature is optional.
When searching by a descriptor, shouldn’t the
#hash symbol be URL-encoded?ODS/API is not expecting to EDITORIAL AFTER THE MEETING: Yes, it should be URL-encoded. Swagger UI was implicitly encoding before sending the request.
Order and/or query by Last Modified Date
Yes, looks interesting and could open additional use cases.
Is this only for modified dates or also create dates?
Last modified date is initially set as the create date, therefore it isn’t necessary to add a search just on create date.
| Tip |
|---|
Feature discovery board: Using Last Modified Date in Queries |
Viewing and providing input on the Ed-Fi roadmap
...
Q: can the community enter issues into either of the projects (Roadmap, Feature Discovery)?
A: Not fully worked out yet. Support cases need to continue going through the Community Hub.
Q: can you automate pruning requests that don’t have a support case?
A: We will certainly be looking into automation options, directly in GitHub and/or with externa Python scripts.