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
We currently ignore the persisted ids of returned entities, which makes it very difficult for users to save the results on their own backends as well as use other parts of the interface that require an entity's id (e.g. transferring rights).
Although not technically correct, as we don't support GET operations yet (see #14), we can use the @id in the returned JSON-LD to denote the persisted id. Doing so results in a relative URL to the current route, which works for /manifestations and /rights, but will require some special handling for RightsAssignments since its route is /rights/transfer (e.g. its @id will probably look something like ../rights_assignment/<id>).
The text was updated successfully, but these errors were encountered:
We currently ignore the persisted ids of returned entities, which makes it very difficult for users to save the results on their own backends as well as use other parts of the interface that require an entity's id (e.g. transferring rights).
Although not technically correct, as we don't support
GET
operations yet (see #14), we can use the@id
in the returned JSON-LD to denote the persisted id. Doing so results in a relative URL to the current route, which works for/manifestations
and/rights
, but will require some special handling for RightsAssignments since its route is/rights/transfer
(e.g. its@id
will probably look something like../rights_assignment/<id>
).The text was updated successfully, but these errors were encountered: