ISAN API 3.0 - deduplication

The deduplication service enables to list potential duplicates of an ISAN application and to take an appropriate action to pursue the ISAN application process. 

List all potential duplicates

When an ISAN application returns the status "pending", then a manual deduplication is required to assess if the ISAN has already been registered or not. To list all potential duplicates use the service /deduplication/queries

POST /deduplication/queries List matching candidates

Refer to ISAN swagger site for details and examples in json and xml

• The service enables to filter witch files are returned to compare the matching candidates with the submitted application.
• The first item of the list corresponds to the submitted application, followed thereafter by the matching candidates.
• The score provided in the status enable to compute a distance between the submitted application ("scores"/"reference") and each matching candidate (scores"/"relative")

Based on these comparisons, several actions are possible (/deduplication) to pursue the ISAN application service.

Take the deduplication action

Several deduplication actions are possible for each ISAN returned in the list of potential duplicates.

PATCH /deduplication Perform deduplication operations - Reject candidates, confirm duplicate....

Refer to ISAN swagger site for details and examples in json and xml

Use the "action" field to specify on the of the following action:

• is_new: none of the listed ISAN in POST /deduplication/queries is identifying the application. A new ISAN will be allocated.
• is_duplicate: The specified ISAN is identifying the same work as the application. No ISAN will be allocated, instead the existing ISAN will be associated to the application.
• reject: reject the specified list of ISAN as potential duplicates => these ISAN are not identifying the same work as the application
• is_new_and_link_isan: the specified ISAN does not identify the same work as the application, but is linked to it (example: the application and the potential duplicate are both part of the same sequel). The two ISAN will be linked as "linkedIsan". A qualifier (Linked ISAN Type) for the the ISAN link is required (example: "type": "sequel"). A new ISAN will be allocated, the existing ISAN will be linked as a LinkedIsan.
• is_missed_duplicate: specify a duplicate ISAN that has been missed by the matching (not listed in POST /deduplication/queries) that identifies already the application. No ISAN will be allocated, instead the existing ISAN will be associated to the application.