Versions Compared

Key

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


New DAS exchange API

Table of Contents
maxLevel5
typeflat

Children Display
pageNew DAS exchange API

Section


Column

The following diagram describes the exchange flows for registration and retrieval of documents hosted in OFF

draw.io Diagram
bordertrue
diagramNameDocuments-hosted-by-OFF
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth697
revision1


Exchange flow to retrieve document from the OFF digital library

  1. OSF sends a document retrieval request to WIPO DAS and receives a request acknowledgement id issued by WIPO DAS (i.e. POST /das/v1/requests/retrievals
  2. WIPO DAS forwards the retrieval request to the OFF (i.e. POST /das/v1/requests/retrievals
  3. OFF prepares the requested document for download and notify WIPO DAS of the document availability by referring to the request acknowledgement id returned by WIPO DAS (i.e. POST /das/v1/requests/notifications
  4. WIPO DAS retrieves the file location URL based on  (i.e. GET /das/v1/requests/files/url-downloads)
  5. WIPO DAS download the document file content from OFF
  6. WIPO DAS prepares the requested document for download by OSF and notifies the OSF of the document availability by referring to the request acknowledgement id returned in step 1 (i.e. POST /das/v1/requests/notifications
  7. OSF retrieves the file location URL for document download by referring to the request acknowledgement id returned in step 1 (i.e. GET /das/v1/requests/files/url-downloads)
  8. OSF uses the given file location URL obtained in step 7 to download the document file content
  9. Optionally OSF deletes the download files from the DAS transit zone (i.e. DELETE /das/v1/requests/files
Note
titleNote:
If OSF does not delete the downloaded file, WIPO DAS will delete it after a pre-defined period (e.g. 1 week)



Column
width40%

a.- New DAS exchange API

...

Table of Contents
maxLevel5

Page Tree
roota.-

...

New DAS exchange API
pagea.- Initial private_key_jwt registration process