Installing Additional Streams


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:

StreamDescriptionInstallation Package
xmlDefault stream for patent content


Note: the xml stream is the default stream delivered with the alexandria-schema-tools package

litigationLitigation data which supports the Litigation APIalexandria-schema-litigation
entitiesCompany hierarchy data that is the foundation of our IP Profilesalexandria-schema-entities
trademarksComing soonn/a


In order to accept stream updates, the appropriate schema needs to be installed and created.

# sudo yum -y install alexandria-schema-<stream>, e.g.,
sudo yum -y install alexandria-schema-litigation
# or
sudo yum -y install alexandria-schema-entities

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:

# psql -U alexandria -f /usr/share/alexandria/alexandria-schema-entities/alexandria-schema-<stream>.sql, e.g.,
psql -U alexandria -f /usr/share/alexandria/alexandria-schema-litigation/alexandria-schema-litigation.sql
# or
psql -U alexandria -f /usr/share/alexandria/alexandria-schema-entities/alexandria-schema-entities.sql

Because of the dependency on the PostgreSQL schema, 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.

Data Updates

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 reporting.t_client_load_process.


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.