You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to make it easier for people to test the system, the UI should allow the user to upload a CSV file with membership data matching the ULI Template Schema.
This means that data will need to be converted from CSV to JSON either on the client side, before submitting it to the Batch Ingest API, or the Ingest API will need to be extended to support CSV.
There are two possibilities if the functionality is implemented on the API: a) either the endpoint could be the same (in which case the function would have to check the content type and convert if CSV, otherwise use JSON), or b) a different URL could be used. Using the same URL is probably preferable if this is to be done on the ULI API rather than UI.
The text was updated successfully, but these errors were encountered:
The Batch Ingest API uses records in JSON format, which are represented by an array of ULI payload items. For example:
In order to make it easier for people to test the system, the UI should allow the user to upload a CSV file with membership data matching the ULI Template Schema.
This means that data will need to be converted from CSV to JSON either on the client side, before submitting it to the Batch Ingest API, or the Ingest API will need to be extended to support CSV.
There are two possibilities if the functionality is implemented on the API: a) either the endpoint could be the same (in which case the function would have to check the content type and convert if CSV, otherwise use JSON), or b) a different URL could be used. Using the same URL is probably preferable if this is to be done on the ULI API rather than UI.
The text was updated successfully, but these errors were encountered: