Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update list of OPS fulltext countries #50

Closed
amotl opened this issue Apr 17, 2022 · 2 comments · Fixed by #49
Closed

Update list of OPS fulltext countries #50

amotl opened this issue Apr 17, 2022 · 2 comments · Fixed by #49

Comments

@amotl
Copy link
Member

amotl commented Apr 17, 2022

Dear @aghster,

thank you again for your contribution #3 submitted the other day. In the OPS manual 1.3.16 1, I observed the following change log items since I've looked at it the last time:

  • 2019-05-07 1.3.10 Updated fulltext collection.
  • 2019-09-05 1.3.15 Updated the fulltext country code list.
  • 2020-09-14 1.3.16 Correction to countries list.

Maybe it is not too difficult to figure out what has changed here, and converge that into a patch, if necessary.

With kind regards,
Andreas.

Footnotes

  1. https://documents.epo.org/projects/babylon/eponet.nsf/0/F3ECDCC915C9BCD8C1258060003AA712/$File/ops_v3.2_documentation_-_version_1.3.16_en.pdf

@aghster
Copy link
Contributor

aghster commented Apr 17, 2022

This may be the list you are looking for: https://www.epo.org/searching-for-patents/data/web-services/ops/faq.html#faq-74

@amotl
Copy link
Member Author

amotl commented Apr 18, 2022

Thank you very much. ccc50d9 will bring the list of full text authorities for EPO/OPS up to speed.

Those countries have been added:
BG, CZ, DK, EE, GR, IT, LT, ME, RS, SE, SK

Thank you, @epo!

@amotl amotl linked a pull request Apr 18, 2022 that will close this issue
@amotl amotl closed this as completed in #49 Nov 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants