Batch upload: why is reindexing required if we supplied an index parameter?
41 views
Skip to first unread message
Paul Collins
Sep 12, 2022, 8:09:02 PM9/12/22
to AtoM Users
Hi Artefactual,
We've recently been batch-uploading some documents (in this case, JPG images) to our catalogue. We did this according to your documentation here:
https://www.accesstomemory.org/en/docs/2.6/admin-manual/maintenance/cli-import-export/#digital-object-load-task
As probably the only person in our organisation with any familiarity with a Unix command line, I tested and wrote up this process for our archivist. Our upload worked fine, but he found that the files came out missing their names ("untitled" or such). The specific command line that we used for the import was this:
sudo -u www-data php symfony digitalobject:load --index --path="/var/tmp/_mattemp/" /var/tmp/_mattemp/_filelist.csv
So, regarding the "untitled" issue, we were advised by your colleague (M.C.) that we could fix the issue by forcing a reindex, as follows:
sudo -u www-data php symfony propel:build-nested-set
sudo -u www-data php symfony digitalobject:regen-derivatives --slug='REDACTED' --index
That's fine, and we can make that part of our process if necessary, but I believe this goes against your documentation, which specifically states that the "--index" parameter on "digitalobject:load" should reindex during import, and NOT require any further indexing commands afterwards.
Could you clarify this for us, please?
Paul C.
We've recently been batch-uploading some documents (in this case, JPG images) to our catalogue. We did this according to your documentation here:
https://www.accesstomemory.org/en/docs/2.6/admin-manual/maintenance/cli-import-export/#digital-object-load-task
As probably the only person in our organisation with any familiarity with a Unix command line, I tested and wrote up this process for our archivist. Our upload worked fine, but he found that the files came out missing their names ("untitled" or such). The specific command line that we used for the import was this:
sudo -u www-data php symfony digitalobject:load --index --path="/var/tmp/_mattemp/" /var/tmp/_mattemp/_filelist.csv
So, regarding the "untitled" issue, we were advised by your colleague (M.C.) that we could fix the issue by forcing a reindex, as follows:
sudo -u www-data php symfony propel:build-nested-set
sudo -u www-data php symfony digitalobject:regen-derivatives --slug='REDACTED' --index
That's fine, and we can make that part of our process if necessary, but I believe this goes against your documentation, which specifically states that the "--index" parameter on "digitalobject:load" should reindex during import, and NOT require any further indexing commands afterwards.
Could you clarify this for us, please?
Paul C.
Dan Gillean
Sep 13, 2022, 8:14:05 AM9/13/22
to ICA-AtoM Users
Hi Paul,
You are correct - if the --index option works as expected, then you should not have to re-index via any other task afterwards.
However, thanks to a previous forum thread where someone else reported this issue last year, we found a bug with this particular task option and have documented it here:
As you will see, this issue has been fixed in the upcoming 2.7 release. The changes are fairly minor, as seen in the related pull request.
Sorry for the confusion!
Cheers,
he / him
--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/932cf592-0c0c-4b6b-9d15-c209bc2925d0n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages