Dear all,
As some of you have already noticed and many of you have also reported it via different channels, OPS at the moment is not as up to date as it normally would be. This is partially also due to annual Office closure in week 52.
Please use biblio coverage table available here to track progress in loading newly available data to OPS:
https://www.epo.org/searching-for-paten ... tions.html
This table is updated daily and update of the table is set on 15:00 CET.
We are doing our best to close the gap as soon as possible and the best indicator of how far we are is the table I am linking here for your convenience.
We are sorry for any inconvenience caused by this and we hope the issue will be resolved in the next few days
Regards,
Vesna for OPS support
Issues with biblio in OPS Published services
-
- Posts: 1298
- Joined: Thu Feb 22, 2007 5:32 pm
-
- Posts: 6
- Joined: Fri Jul 02, 2021 9:01 am
Re: UPDATE 13.1.2022 - Issues with biblio in OPS Published services
Dear EPO,
As an OPS user, I continue to see that patents are delivered via DocDB, these patents are also present in newEspacenet. But even today (17 Jan 2022 10am) these patents are still missing in OPS.
An example: US11205661B2 (Release date: 2021-12-21)
https://worldwide.espacenet.com/patent/ ... 11205661B2
OPS
http://ops.epo.org/3.2/rest-services/pu ... e,abstract
Antwort:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fault
xmlns="http://ops.epo.org">
<code>SERVER.EntityNotFound</code>
<message>No results found</message>
</fault>
I just found this example by chance after a short check. I am sure that there are more of them.
Please ask the responsible team again to check the situation and perform 1:1 matching tests if necessary.
I would like to thank the OPS support team for always responding to our requests quickly and competently. We were always very well advised and our concerns were always taken seriously, thank you again!
Unfortunately, this does not help when there are always technical problems that take a long time to be solved. We can all imagine how difficult it can be to keep dozens of gateways running with their own lives. But in the end, it takes a fully functioning solution to give DocDB customers, customers with an OPS 4G+ account, the performance they need to run their business.
We hope that the last gaps will be found quickly and their data can be imported into OPS.
Please feel free to contact me with any questions or ideas.
With kind regards,
Kerstin Thoma.
As an OPS user, I continue to see that patents are delivered via DocDB, these patents are also present in newEspacenet. But even today (17 Jan 2022 10am) these patents are still missing in OPS.
An example: US11205661B2 (Release date: 2021-12-21)
https://worldwide.espacenet.com/patent/ ... 11205661B2
OPS
http://ops.epo.org/3.2/rest-services/pu ... e,abstract
Antwort:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fault
xmlns="http://ops.epo.org">
<code>SERVER.EntityNotFound</code>
<message>No results found</message>
</fault>
I just found this example by chance after a short check. I am sure that there are more of them.
Please ask the responsible team again to check the situation and perform 1:1 matching tests if necessary.
I would like to thank the OPS support team for always responding to our requests quickly and competently. We were always very well advised and our concerns were always taken seriously, thank you again!
Unfortunately, this does not help when there are always technical problems that take a long time to be solved. We can all imagine how difficult it can be to keep dozens of gateways running with their own lives. But in the end, it takes a fully functioning solution to give DocDB customers, customers with an OPS 4G+ account, the performance they need to run their business.
We hope that the last gaps will be found quickly and their data can be imported into OPS.
Please feel free to contact me with any questions or ideas.
With kind regards,
Kerstin Thoma.
-
- Posts: 1298
- Joined: Thu Feb 22, 2007 5:32 pm
Re: UPDATE 13.1.2022 - Issues with biblio in OPS Published services
Dear Kerstin,
We have a very specific issue with US B's, there is another user who reported that via this forum few days ago and as far as I hear that should also be fixed in this week.
Regards,
Vesna for OPS support
We have a very specific issue with US B's, there is another user who reported that via this forum few days ago and as far as I hear that should also be fixed in this week.
Regards,
Vesna for OPS support
-
- Posts: 1298
- Joined: Thu Feb 22, 2007 5:32 pm
Re: Issues with biblio in OPS Published services
UPDATE: 18 January 2022
Dear all,
We are currently still facing a technical outage related to the exchange of data from DocDB database to EPODOC, which results in lacking data in tools such as Epoque, OPS, Classic Espacenet and EpoqueNet.
New Espacenet and DOCDB in XML bulk dataset are less impacted by the mentioned outage but are still not as up to date as they should be: https://www.epo.org/searching-for-paten ... tions.html
Please note that missing biblio data also consequently causes missing coverage in families, abstracts or names/titles in EN etc as well as in other data flows that use biblio data records to link with - like image data or full text - "no biblio = no record in a database"
The relevant technical teams are working hard on solving this issue as promptly as possible.
We sincerely apologise for the inconvenience. I will inform you immediately after I am sure that we really managed to solve the issue and fill gaps in data coverage
Kind regards,
Vesna for OPS support
Dear all,
We are currently still facing a technical outage related to the exchange of data from DocDB database to EPODOC, which results in lacking data in tools such as Epoque, OPS, Classic Espacenet and EpoqueNet.
New Espacenet and DOCDB in XML bulk dataset are less impacted by the mentioned outage but are still not as up to date as they should be: https://www.epo.org/searching-for-paten ... tions.html
Please note that missing biblio data also consequently causes missing coverage in families, abstracts or names/titles in EN etc as well as in other data flows that use biblio data records to link with - like image data or full text - "no biblio = no record in a database"
The relevant technical teams are working hard on solving this issue as promptly as possible.
We sincerely apologise for the inconvenience. I will inform you immediately after I am sure that we really managed to solve the issue and fill gaps in data coverage
Kind regards,
Vesna for OPS support