Participants
| Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Agenda
- Ed-Fi to CEDS CommunicationData Movement
- API-first strategy
- Bulk data exchange over API
Materials
| View file | ||||
|---|---|---|---|---|
|
Notes
Ed-Fi to CEDS Integration was discussed. A few points made during the discussion:
- it was generally agreed that a new mapping/transformation strategy was needed, and not a database to database one
- The concept that Ed-Fi needs a single input point was also raised
- it was also noted that it is difficult to see what to integrate with - that CEDS looks like many projects and not a clear architecture or platform
- It was noted that CEDS is working on a JSON schema
One suggestion that was well-received was to go ahead and try a JSON-to-JSON mapping as a means of exploring the technology and process for maintaining the possibility. This does not have to be a CEDS structure necessarily.
API First strategy
Ed-Fi reviewed the history here, including the plans to look for API-first strategy for feeding downstream analytics, as opposed to the database access strategy of AMT
One suggestion that emerged was to look at if the ODS could add a feature to push HTTP requests to other endpoints – effectively a simple version of propagating API events.