You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful if this decision to not import the dataset was logged.
Detailed Feature Description
Add logging facilities to Drupal\datastore\Plugin\QueueWorker\ImportQueueWorker::processItem() such that it informs the user that the dataset already exists and will not be imported.
Problem and Motivation
It's convenient to know when this has happened.
Potential Benefits
Users will know when their datasets have been skipped for already existing, and they will be better equipped to validate or debug processes.
Target Audience
End Users
Developers
Administrators
Other
Possible Implementation
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Feature Description
When a queue item is created to import an already-existing datastore, it can recognize that there is already a dataset and thus not re-import it.
This happens right about here in code:
dkan/modules/datastore/src/Plugin/QueueWorker/ImportQueueWorker.php
Line 146 in 3ce8b0b
It would be helpful if this decision to not import the dataset was logged.
Detailed Feature Description
Add logging facilities to
Drupal\datastore\Plugin\QueueWorker\ImportQueueWorker::processItem()
such that it informs the user that the dataset already exists and will not be imported.Problem and Motivation
It's convenient to know when this has happened.
Potential Benefits
Users will know when their datasets have been skipped for already existing, and they will be better equipped to validate or debug processes.
Target Audience
Possible Implementation
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: