Contained within some files is a record of who last modified the file, specifically a username or a more detailed name available to the originating software.
This check raises a flag if an exact copy of the last modified by name is found in other submisions in the target files. It can be useful in detecting submissions based on another submission. It also checks agains the creator information of other submissions to see if any duplication appears there.
An example of this situation would be where one student sends their submission to a classmate. The classmate then makes alterations to their submission. Since both the original submission and the classmates own submission were edited last by the same person a flag would be raised.
In The Report
The meta last modified by information is present in the report for all submissions and can be reviewed in the individual submission summary.
Process Time Options
Like many of the other checks, there are a few options which can be used to fine tune the behaviour of it at process time, as well as can be set in the default options in the Preferences section.
|Process Options ||Type ||Default |
|Check.Meta.LastModifiedBy.Enabled ||Boolean ||True |
|A true/false setting of if the meta last modified by information should be compared againt other submissions. |
|Check.Meta.LastModifiedBy.Weight ||Float ||0.95 |
|A 0-1 value (percentage) of how heavily a flag raised by this check should be weighted in the report. ≥ 0.85 is considered dangerous, ≥ 0.65 is considered a warning, leaving everything below as just a tertiary notice. |
|Shared.IgnoredUsernames ||Array/List || |
|A shared "safe" list of usernames that are used during the processing of submissions. |