events - snac-pilot/data-model GitHub Wiki

The SNAC prototypes have been built using batch processing. A batch architecture will not allow us to develop a site that meets modern expectations for update speed.

Some sort of "event bus"/queue needs to be set up for the application parts to communicate.

There are several ways this could be implemented; here are some AWS services that could play a role in this.

• Amazon SQS -- work queue
• Amazon SNS -- notification service
• Redis (on ElasticCache) -- esp. pub sub
• Amazon Kinesis -- maybe best fit for storing all application and server events/logs.

Events

• propose new identity for review
• approve new identity for publication
• Merge Identity (correct type I error)
• Split Identity (correct type II error)
• Merge Identity (mayBeSameAs)
• Split identity (disambiguation page)
• deny same as (mayBeSameAs)
• edit identity/description
• edit related resources/relationships
• Flag bad link / bad data in related resources
• edit related identity/relationships
• edit occupations
• edit location / correct Unknown code display errors
• "String to Thing" request
• page views / page level events
• edit sent for review