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 16,680
Broken Notifications  |   % Broken 2,358   |   14.1%
# Unique Non-existent Datafile Objects 866
# Unique Affected Users 612

> See more details

DatasetVersion

Notifications referencing a DatasetVersion object.

Possible notice types: CHECKSUMIMPORT, CREATEDS, FILESYSTEMIMPORT, RETURNEDDS

All Notifications 12,196
Broken Notifications  |   % Broken 2,456   |   20.1%
# Unique Non-existent DatasetVersion Objects 2,273
# Unique Affected Users 648

> See more details

Dataverse

Notifications referencing a Dataverse object.

Possible notice types: CREATEDV

All Notifications 2,086
Broken Notifications  |   % Broken 433   |   20.8%
# Unique Non-existent Dataverse Objects 433
# Unique Affected Users 238

> See more details

DvObject

Notifications referencing a DvObject object.

Possible notice types: REVOKEROLE

All Notifications 2,410
Broken Notifications  |   % Broken 1,071   |   44.4%
# Unique Non-existent DvObject Objects 1,065
# Unique Affected Users 533

> See more details

FileMetadata

Notifications referencing a FileMetadata object.

Possible notice types: MAPLAYERUPDATED

All Notifications 330
Broken Notifications  |   % Broken 294   |   89.1%
# Unique Non-existent FileMetadata Objects 49
# Unique Affected Users 15

> See more details