data checks: Broken Notfications

For this metric, "broken" refers to a notifcation that references a non-existent object.

For example a notification may reference a Dataset object that was (correctly) deleted.

Datafile

Notifications referencing a Datafile object.

Possible notice types: REQUESTFILEACCESS

All Notifications 14,239
Broken Notifications  |   % Broken 154   |   1.1%
# Unique Non-existent Datafile Objects 123
# Unique Affected Users 143

> See more details

DatasetVersion

Notifications referencing a DatasetVersion object.

Possible notice types: CHECKSUMIMPORT, CREATEDS, FILESYSTEMIMPORT, RETURNEDDS

All Notifications 10,718
Broken Notifications  |   % Broken 1,798   |   16.8%
# Unique Non-existent DatasetVersion Objects 1,618
# Unique Affected Users 599

> See more details

Dataverse

Notifications referencing a Dataverse object.

Possible notice types: CREATEDV

All Notifications 1,900
Broken Notifications  |   % Broken 371   |   19.5%
# Unique Non-existent Dataverse Objects 371
# Unique Affected Users 214

> See more details

DvObject

Notifications referencing a DvObject object.

Possible notice types: REVOKEROLE

All Notifications 2,364
Broken Notifications  |   % Broken 1,045   |   44.2%
# Unique Non-existent DvObject Objects 1,039
# Unique Affected Users 527

> See more details

FileMetadata

Notifications referencing a FileMetadata object.

Possible notice types: MAPLAYERUPDATED

All Notifications 292
Broken Notifications  |   % Broken 256   |   87.7%
# Unique Non-existent FileMetadata Objects 44
# Unique Affected Users 14

> See more details