In the latest 2023 DOCDB backfile, we're seeing some instances of a date "10101" and I'm wondering how that date should be interpreted. We did not see any instances of this in the 2022 backfiles. I also do not see any mention of this date code in the documentation or README.
For example, in DOCDB-202308-001-BY-0459.xml
....
<exch:exchange-document country="BY" doc-number="7030" kind="C1" doc-id="519086119" date-publ="20001230" family-id="83744584" is-representative="YES" date-of-last-exchange="20230219" date-added-docdb="20221031" originating-office="EP">
<exch:bibliographic-data>
<exch:publication-reference data-format="docdb">
<document-id>
<country>BY</country>
<doc-number>7030</doc-number>
<kind>C1</kind>
<date>20001230</date>
</document-id>
</exch:publication-reference>
<exch:publication-reference data-format="epodoc">
<document-id>
<doc-number>BY7030</doc-number>
</document-id>
</exch:publication-reference>
<exch:application-reference is-representative="NO" doc-id="581870646" data-format="docdb">
<document-id>
<country>BY</country>
<doc-number>20000352</doc-number>
<kind>A</kind>
<date>10101</date>
</document-id>
</exch:application-reference>
<exch:application-reference data-format="epodoc">
<document-id>
<doc-number>BY20000000352</doc-number>
</document-id>
</exch:application-reference>
<exch:priority-claims>
<exch:priority-claim sequence="1" data-format="docdb">
<document-id doc-id="581870646">
<country>BY</country>
<doc-number>20000352</doc-number>
<kind>A</kind>
<date>10101</date>
</document-id>
<exch:priority-active-indicator>Y</exch:priority-active-indicator>
</exch:priority-claim>
<exch:priority-claim sequence="1" data-format="epodoc">
<document-id>
<doc-number>BY20000000352</doc-number>
</document-id>
</exch:priority-claim>
...
Thanks,
Joe
How to interpret date of "10101" in latest DOCDB backfile
-
- Posts: 1298
- Joined: Thu Feb 22, 2007 5:32 pm
Re: How to interpret date of "10101" in latest DOCDB backfile
Hi Joe
I will ask the team to correct the date and re-exchange it in next Amend front file.
There are many reasons why such issues can happen in a big data set like DOCDB. I don't want to speculate what the cause was in this case, but the good thing is that Amend file can correct the issue quickly and easily.
Regards,
Vesna for Patent data
I will ask the team to correct the date and re-exchange it in next Amend front file.
There are many reasons why such issues can happen in a big data set like DOCDB. I don't want to speculate what the cause was in this case, but the good thing is that Amend file can correct the issue quickly and easily.
Regards,
Vesna for Patent data