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
Is your feature request related to new functionality not yet included in the product? Please describe.
Is your feature request related to a problem or a change to existing functionality? Please describe.
Currently, we have the ability to ingest a work or batch of works into the repository one CSV at a time. This means that once a CSV ingest is finished, manual intervention is required to begin ingest of another CSV. It would be much more efficient to have the ability to queue up multiple CSVs to ingest back-to-back.
Describe the solution you'd like
I want to be able to create a queue of CSVs ready for ingest, begin the ingest process, and have them all run successfully without having to start each ingest manually.
Describe alternatives you've considered
Status quo: requires staff user to pay close attention to the status of current ingest to know when another can be started.
How will this impact users?
This would minimize the time staff users spend monitoring the status of ingests, particularly when running multiple ingests over weekends or holidays.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Bulkrax importer allows us some degree of scheduling capability but it only supports Once, Daily, Monthly, or Yearly options without further granularity. This may be an enhancement to propose to the Bulkrax team.
Is your feature request related to new functionality not yet included in the product? Please describe.
Is your feature request related to a problem or a change to existing functionality? Please describe.
Currently, we have the ability to ingest a work or batch of works into the repository one CSV at a time. This means that once a CSV ingest is finished, manual intervention is required to begin ingest of another CSV. It would be much more efficient to have the ability to queue up multiple CSVs to ingest back-to-back.
Describe the solution you'd like
I want to be able to create a queue of CSVs ready for ingest, begin the ingest process, and have them all run successfully without having to start each ingest manually.
Describe alternatives you've considered
Status quo: requires staff user to pay close attention to the status of current ingest to know when another can be started.
How will this impact users?
This would minimize the time staff users spend monitoring the status of ingests, particularly when running multiple ingests over weekends or holidays.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: