CLAIMS Direct offers supplemental content via its streams implementation. Stream content is simply additional data that is stored in separate PostgreSQL schema. Examples of streams:
|xml||Default stream for patent content|
Note: the xml stream is the default stream delivered with the alexandria-schema-tools package
|litigation||Litigation data which supports the Litigation API||alexandria-schema-litigation|
|entities||Company hierarchy data that is the foundation of our IP Profiles||alexandria-schema-entities|
In order to accept stream updates, the appropriate schema needs to be installed and created.
Each package installs the SQL to build the schema in
/usr/share/alexandria/alexandria-schema-<stream>. Depending on which stream you are subscribed to, you build the PostgreSQL schema as follows:
Because of the dependency on the PostgreSQL schema, firstname.lastname@example.org should be informed upon completion of schema creation. Once informed, back file packages will be queued for retrieval by
apgupd and normal front file updates will follow similar to and in-line with the xml stream. For new installations as well as any changes to your subscription, it may take 24 hours for full synchronization of your on-site instance.
apgupd, the update utility for all CLAIMS Direct instances, will query the
update/streams endpoint to retrieve a list of available streams for your instance. For each stream, it will call a stream-specific PostgreSQL function to retrieve the maximum
load-id with which it will retrieve the next update package. Currently, all streams share the same
load-id queue and are all registered in
Although currently all streams share the same update queue, i.e., share a common load-id sequential identifier, this may not be the case with future streams.