Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

Jira Legacy
serverSystem

...

JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODSOURCE-68

1. Click to see the log of the loaded file 

...

3. Send delete request passing JobExecution id as URI parameter

MethodDescription



DELETE

/change-manager/jobExecutions/{jobExecutionId}/records

Delete JobExecution and associated records in SRS. Refer to API documentation.


Code Block
curl -w '\n' -X DELETE -D -   \
   -H "Content-type: application/json"   \
   -H "Accept: */*"   \
   -H "x-okapi-tenant: diku"  \
   -H "x-okapi-token: {{valid-token}}" \
   {{host}}/change-manager/jobExecutions/3e46d1a3-2bb4-4951-91f8-e53c5dfc7cec/records

...

Warning: After removal of the target records in SRS, related Instance (from Inventory) doesn't get remove. Instance keeps alive removed. The Instance remains in Inventory and does not know about records absence and that the SRS MARC has been removed. The Instance's SOURCE field is still equal to MARC. As a result, the 'View source' button continues and quickMARC actions continue to be displayed. This behavior may be reviewed and refined in the future.