New Espacenet version will probably require adaptations

[aghster]

Hi,

the EPO has recently released a beta of the upcoming new Espacenet. When the current Espacenet will be replaced by the new one, this will probably require some adaptation of all services that obtain their data by crawling Espacenet.

I just wanted to give you a heads up.

[amotl]

Thanks for the heads up! Let's have a look at this on behalf of the canonical example document EP0666666.

As far as i can see, links should go to [1], at least while in beta, that is. However, this won't open the detail view, so getting what you want will be another click away.

Also, fulltext information would be available in JSON format from e.g. [2,3]. However, as OPS is the primary data source here, this would just be used in fallback situations. If full text information for more authorities will be available through OPS (as you mentioned in #3), this fallback would probably become obsolete.

[1] https://worldwide.espacenet.com/beta/search/publication/EP0666666
[2] https://worldwide.espacenet.com/3.2/rest-services/highlight/family/022711419/publication/EP/0666666/A2?fields=publications.claims_en&q=pn=EP0666666
[3] https://worldwide.espacenet.com/3.2/rest-services/highlight/family/022711419/publication/EP/0666666/A2?fields=publications.desc_en&q=pn=EP0666666

[aghster]

OPS still lacks full-text for DE and US, for example, while Espacenet apparently covers these authorities. Therefore, I think the fallback to Espacenet is rather important, as long as OPS does not cover all main authorities.

Can a link of type [2] be compiled through a script? Where do you get the familiy number from?

[amotl]

OPS still lacks full-text for DE and US [...] therefore I think the fallback to Espacenet is rather important

Ahja, bummer. Then we will have to keep it, thanks!

Can a link of type [2] be compiled through a script?

Good question, i was thinking the same. The link above will trigger when clicking on the document in the left hand side of the navigation in New Espacenet.

Where do you get the family number from?

It is probably the family ID, right? If EPO uses the same identifiers as in the OPS system here, we will have a way to line this slot properly, being able to generate the full URL to the resource.

[amotl]

The "aggregated" endpoint also yields a nice response, see [1].

[1] https://worldwide.espacenet.com/3.2/rest-services/search/family/022711419/aggregated/biblio?q=pn%3DEP0666666&qlang=cql

[amotl]

Dear @aghster,

c3f1dff, 2d89bc6 and bc10015 will bring in some fixes and improvements to the Espacenet adapter subsystem.

With kind regards,
Andreas.