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
Previously, when rerunning an entry that came from a zip file, the rerun
would fail because it would look for the CSV in an assumed location
which is based on it's last importer ID. Since this was a rerun, it
does not do an unzip into the assumed location so the directory does not
exist.
This commit will first check if the assumed location exists, and if not,
it will look for the location of the last unizpped files and use that
for the rerun.
This does cause an interesting behavior where if the entry is a work
with a file attached, it will add the file again resulting in duplicate
files. I feel this is such an edge case though because typically if the
entry is successful, the user will not rerun it. I added a hint text to
the importer to let the user know this is a possibility.
Ref:
- notch8/palni_palci_knapsack#210
Copy file name to clipboardExpand all lines: app/views/bulkrax/importers/_edit_item_buttons.html.erb
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@
5
5
<h5>Options for Updating an Entry</h5>
6
6
<hr/>
7
7
<p>Rebuild metadata and files.</p>
8
+
<pclass="text-warning">Files may be duplicated if this option is used on a successful entry. Consider using <em>Remove and then Build</em> instead.</p>
0 commit comments