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
The V2.0 of our catalog will hopefully be able to push edits and new data to I14Y.
In order to have the best possible results we should understand how the I14Y API works.
List of items to check:
(@Damian-Oswald and @hurni feel free to add new ones in this list by editing this comment directly)
API access via token. Is the token stable or must be renewed every time via a pre-request?
API push: Are special characters ("ü") OK or should we escape them?
API push: Is it possible to have some simple formatting in the description field (separated paragraphs). If yes, how can we send the info to the API so that it can be correctly interpreted and displayed?
Non-personal push to I14Y: the catalog will push to I14Y on behalf of itself and not a specific user. Is that altogether possible (non-personal account/token)? Or would rather I14Y like to build a harvester on our data?
By creation of a new dataset or codelist, check how I14Y assign and returns the ID, so that by following updates can be sent using the correct ID
The text was updated successfully, but these errors were encountered:
The V2.0 of our catalog will hopefully be able to push edits and new data to I14Y.
In order to have the best possible results we should understand how the I14Y API works.
List of items to check:
(@Damian-Oswald and @hurni feel free to add new ones in this list by editing this comment directly)
The text was updated successfully, but these errors were encountered: