...
We receive some design patents from DocDB DOCDB so there are some records with bibliographic information in the database. However, in general, we do not cover design patents, and full text is not available for these records. A quick way to find which designs are available in CLAIMS Direct is to query by kind code since all of them share kind code "S". "E" is also used for design reissues. Therefore, you would search on pnkind:(S* OR E*). You can then see the country coverage for designs by faceting your query by patent country (pnctry). For more information about how to use faceting in CDWI, see the Facet page.
...
Yes. Simple family IDs, as assigned by DocDBDOCDB, are available through both CDWI and CDWS using the search field fam. IFI CLAIMS assigns a default family ID of -1 if we have not received a family ID from DocDBDOCDB. If you see this value, it means either that the record is not available in DocDB DOCDB or we have not yet received the DocDB DOCDB record. In the latter case, the family ID will be populated once we receive the DocDB DOCDB record.
Extended families are only available through CDWS. This is because the extended family can expand literally daily so it must be generated as needed. Instructions on how to access family information through the API can be found on the Family page. To access family data through an on-site instance, see Leveraging On-Site Citation and Family Functionality.
...
With hosted services, you don’t need to worry about updates. It is easy to identify newly updated records via the API. For an on-site server, there is an update process that uses a web service to retrieve data updates that are published sequentially. The server downloads the new data, updates the XML repository, and triggers a SOLR Solr indexing process if you are running that server. There are a variety of load types, but all of this and more is explained in more detail on the Content Update Architecture page.
...
| file-reference-id | load-source | Description |
|---|---|---|
| 303392 | IFI-Cont | ifi-integrated-content update |
| 303372 | DOCDB | DocDB DOCDB update |
| 302363 | USREAS | Reassignment update |
| 302181 | US | Initial load |
...
The CLAIMS Direct index is created and maintained using Apache SOLR Solr (http://lucene.apache.org/solr/) and hence, based on a schema definition, all of the functionality provided by SOLR Solr is available through CLAIMS Direct, including the entire Apache Lucene query language, result set sorting, facet searching, grouping etc. For more information and examples, see the Solr Searching Guide.
The basic search syntax used in CLAIMS Direct is SOLR Solr field name:value. For example:
...
Fields available for searching in CLAIMS Direct, along with tips and examples, can be seen in the Solr Search Fields section. The CLAIMS Direct SOLR Solr index does not store all text. This means that although the entire index is searchable, only certain fields are available for inclusion in a result set. Retrievable fields are marked as "stored" in the SOLR Solr Search Fields tables and a quick reference list is available in the Quick Guide to Stored Solr Fields. You can also find them in the schema where @stored="true", or use the the schema method of the Search service to inspect field attributes.
...
Number formats in CLAIMS Direct are generally provided in DocDBDOCDB-normalized format with a few exceptions, which are:
WO: WIPO's format has changed over the years and you can find 3 formats in DocDBDOCDB. We have standardized WO publication numbers to WO-YYYYNNNNNN. For example, the DocDB DOCDB number WO8002869 becomes WO-1980002869-A1 in CLAIMS Direct.
US applications: The DocDB DOCDB format is YYYYNNNNNN, while the CLAIMS Direct format is US YYYYNNNNNNN.
...
Before you conduct any searches, we recommend that you familiarize yourself with the searching options available in CLAIMS Direct using the SOLR Solr Searching Guide.
...