Based on the feedback we have received from the IPOs currently testing the new API.
| # | Question | Answer |
|---|---|---|
| 1 | Will the new implementation of WIPO-DAS allow an OFF to change the priority date and/or the priority document after an OSF has accessed it? Will the OSF be notified about the change? | Yes, changes can still be made after access by an OSF. However, to keep the OSF informed, we are implementing a notification mechanism via email. When the OFF makes a change on a record already accessed by an OSF, DAS will send an automated email to the OSF's registered contact point, informing them of the updated file. |
| 2 | What happens to the original document when a new PDF is uploaded to replace it in the DAS system? Does it get deleted or stored in the WIPO digital library? | As per our internal archive rules, we are required to keep the original file in record for at least 5 years. When a file is replaced in a registered DAS priority, the system will create an audit log. The new document will be assigned to the registered DAS priority, and a pointer to the audit log with the old file's information will be kept. The OSF will only be able to access the latest version of the document. |
| 3 | What happens when our certificate (client-ID) expires after 2 years? How does the certificate renewal process work? | We need to implement a process for the registration of certificates, which will keep track of the certificate's lifecycle. We will set alerts to send reminders as we approach the certificate's expiration date. The process involves multiple areas of WIPO and needs to be designed with checks and reminders. |
| 4 | Can we have a service that returns a list of pdocs registered for our own OFF? | We plan to implement a service that reports the list of registrations/retrievals per office. The output will be in CSV format to make it more user-friendly. We will provide the CURL and JAVA code to consume it once it's ready for testing. |
| 5 | Is WIPO going to provide a dedicated Java client library for using the REST API | At the present moment, our team is primarily concentrating efforts on the development of our new infrastructure. This critical undertaking has required a considerable allocation of our resources, and therefore, the provision of an extensive, specialized client library has not been included within its scope. Our intention was to offer flexibility by allowing our users to develop their own tailored implementations of client services, as per their specific needs and requirements. Alongside our Java implementation examples, there are numerous other resources available online that could assist you in generating client code. I recommend exploring the following wiki posts, which provide information on utilizing Postman and Swagger.io: e.8.- Using Postman to generate client code e.9.- Using Swagger.io to generate Client code (from REST API YAML file) These resources offer alternative ways to generate code and may further support your development endeavors. |
| 6 | What is the maximum file size which can be deposited in WIPO-DAS? | For the moment, the current limit is around 1.5 Gb and we might increase it in the future. |
| 7 | Currently we do not send optional parameters in the payload or as parameters). Is this ok or could it lead to problems? | Is perfectly fine to not send the optional parameters, they are only included as a way to add additional information to the registration, in case the OFF would want to share it. Also, the preference is to not include the optional parameter at all in the JSON file, please do not use “parameter: null”. You either include the optional parameter with its associated information or not include the parameter at all. |