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 21,993
Broken Notifications  |   % Broken 7,631   |   34.7%
# Unique Non-existent Datafile Objects 2,790
# Unique Affected Users 1,120

> See more details

DatasetVersion

Notifications referencing a DatasetVersion object.

Possible notice types: CHECKSUMIMPORT, CREATEDS, FILESYSTEMIMPORT, RETURNEDDS

All Notifications 14,084
Broken Notifications  |   % Broken 2,656   |   18.9%
# Unique Non-existent DatasetVersion Objects 2,418
# Unique Affected Users 753

> See more details

Dataverse

Notifications referencing a Dataverse object.

Possible notice types: CREATEDV

All Notifications 2,267
Broken Notifications  |   % Broken 515   |   22.7%
# Unique Non-existent Dataverse Objects 515
# Unique Affected Users 258

> See more details

DvObject

Notifications referencing a DvObject object.

Possible notice types: REVOKEROLE

All Notifications 2,469
Broken Notifications  |   % Broken 1,085   |   43.9%
# Unique Non-existent DvObject Objects 1,075
# Unique Affected Users 541

> See more details

FileMetadata

Notifications referencing a FileMetadata object.

Possible notice types: MAPLAYERUPDATED

All Notifications 363
Broken Notifications  |   % Broken 311   |   85.7%
# Unique Non-existent FileMetadata Objects 59
# Unique Affected Users 17

> See more details