-
Notifications
You must be signed in to change notification settings - Fork 470
Open
Milestone
Description
Describe the bug
At the moment, submissions can be created via 3 mechanisms:
- Normal workflow
- QuickSubmit plugin
- Import/export toolset
Later, it's sometimes necessary to try to distinguish between these sources using heuristics. For example:
- In the stats toolset, QuickSubmit-based submissions (and possibly import/export ones too) are excluded from editorial stats to avoid a disproportionate effect on e.g. days to publication;
- In the Google Scholar plugin, there may be a related heuristic around issue and submission publication dates (though I'm not 100%
sure it's quickSubmit/importExport causing the issue).
Recommendation:
- Add a column to the
submissionstable, called e.g. "source", allowing a plain-text indication of the submission's origin. - For new submissions populate this based on the use case.
- On upgrade, use the existing (e.g. stats) heuristic to determine the source. This might not be 100% correct but that's no worse than status quo.
- Remove the stats heuristic and have it depend on the source column instead.
Suggested vocabulary for the column:
nativeImportExportfor submissions that were imported via the native import/export pluginquickSubmitfor submissions that were created by the quickSubmit pluginworkflowfor submissions that were created using the normal editorial workflowquickSubmit-heuristicfor submissions that were upgraded from a version without thesourcecolumn, but appear by heuristic to have been created using quickSubmitunknown-upgradefor submissions that were upgraded from a version without thesourcecolumn, and didn't appear to be created usingquickSubmitby the heuristic
Metadata
Metadata
Assignees
Labels
No labels