“It will allow users to batch-add many files at once to their repository”
How can I use File Sideload to achieve this batch upload?
In the old Dropbox, you put files in a directory on the server, pointed to it from within Omeka, told it which “Collection” to add them to, and clicked the button.
With File Sideload, I’d like to so same: Automatically batch upload from server-side directory, initializing Item records for each, mapped into an Item Set.
The description of this plugin says it can be used for batch uploading, but all I’ve been able to find is how to upload into Omeka-S, one-by-one.
Batch-adding items using the FileSideload module is available via the CSV Import module (see documentation). The exact behavior you describe is not available in the Omeka S module.
In the documentation ‘CSV import’ they say about Sideload: “For the data in this column, you need to include the full file name, including extension”.
I have 12 manuscripts with hundreds of images each. Is there a way in Omeka-S to upload them in batch?
Hi, thx for your previous reaction. I get 2 errors.
1." (dcterms:title) is not a valid item set" : without importing media, this error was there already there . I could make my items with the correct title
2. “Cannot sideload file, File does not exist or does not have sufficient permissions”
I Create a directory (folder) on my server. I did it within the File Sideload module directory and tried also, no extra subdirectory were created.!
That is indeed what the error message told, but individual pictures, without importcsv, I can upload.
No permission error there for the same images on the same location?
And those files are actually located at /home/apache2/htdocs? If so, the permissions rules are basically this: the folder the files are contained in needs to be writable by the server, and the files themselves need to be readable.
The way that File Sideload works is that you upload the files yourself to the server you’re running Omeka on with an SFTP client or something like that: that’s the “sideload” part.
You put the files in a folder on the server (the same folder you configure in File Sideload’s module configuration page), and they get loaded into Omeka from there.
A colleague of mine said that the files in at /home/apache2/htdocs/sideload are set to writable. I am still receiving the same error message, as attached.
What permissions do I need to further provide? I have set up all my files to be readable and writable, and the numeric value is set to 777. I can provide screenshots if needed
In your two screenshots, it looks like you changed the sideload directory. You’re sure you have that right, and it’s where the files are located on the server? Basically you can get that error for two reasons, if the file can’t be read (or deleted after it’s been imported), or if the file just isn’t there.
