curationexperts / epigaea / 2266

90%

Pull #821

travis-ci

Do not send individual notifications for batch operations

Refactor notifications into three kinds:
  * MiraWorkflowNotifications
  * MiraNotifications
  * MiraBatchNotifications

MiraWorkflowNotification:
	Subclasses of the Hyrax workflow notifications.
	They are triggered by Sipity workflow events, as
	defined in `config/workflows/mira_publication_workflow.json`.
	These include comment notifications, and
	publishing and unpublishing of single works.

MiraNotification:
	These are single-item notifications which are
	not triggered by a SipityWorkflow event. These
	are primarily used for notification of
	single-item deposits, either via the
	`/contribute` form or the `Create New Work`
	form on the admin dashboard.

MiraBatchNotification:
	These are batch notifications. They inherit
	some behavior from the `MiraNotification`
	class, but operate at a batch level instead
	of at an individual level. Examples
	include batch xml import, batch metadata
	update, batch publish, batch unpublish, and
	batch template application.

Also included here are README updates with this information,
plus general information about notifications that will be
helpful to someone who is running this application in production.

115 of 115 new or added lines in 21 files covered. (100.0%)

2628 of 2942 relevant lines covered (89.33%)

106.34 hits per line