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 29,510
Broken Notifications  |   % Broken 15,154   |   51.4%
# Unique Non-existent Datafile Objects 5,877
# Unique Affected Users 1,773

> See more details

DatasetVersion

Notifications referencing a DatasetVersion object.

Possible notice types: CHECKSUMIMPORT, CREATEDS, FILESYSTEMIMPORT, RETURNEDDS

All Notifications 16,777
Broken Notifications  |   % Broken 2,889   |   17.2%
# Unique Non-existent DatasetVersion Objects 2,597
# Unique Affected Users 840

> See more details

Dataverse

Notifications referencing a Dataverse object.

Possible notice types: CREATEDV

All Notifications 2,607
Broken Notifications  |   % Broken 564   |   21.6%
# Unique Non-existent Dataverse Objects 564
# Unique Affected Users 287

> See more details

DvObject

Notifications referencing a DvObject object.

Possible notice types: REVOKEROLE

All Notifications 2,541
Broken Notifications  |   % Broken 1,083   |   42.6%
# Unique Non-existent DvObject Objects 1,074
# Unique Affected Users 539

> See more details

FileMetadata

Notifications referencing a FileMetadata object.

Possible notice types: MAPLAYERUPDATED

All Notifications 379
Broken Notifications  |   % Broken 314   |   82.8%
# Unique Non-existent FileMetadata Objects 61
# Unique Affected Users 18

> See more details