Uploading digital image more than 64MB

[binay...@gmail.com]

Hi,

we want to upload digital object more than 64MB but seems like ATOM having 

limitation.It is not allowing  to upload more than 64MB.

is there anyway i can upload more than 64MB digital object?

do i need to do any configuration change for the same?

Regards

Binaya

[Dan Gillean]

Hello Binaya,

During installation, the 64MB upload limit is set in the PHP pool configuration file, found in /etc/php/7.0/fpm/pool.d/atom.conf - see this part of the documentation:

• https://www.accesstomemory.org/docs/latest/admin-manual/installation/linux/ubuntu-xenial/#php

There are a number of other places you should check for file size limitations as well. For example, the php.ini file installed on your server holds a number of values that affect uploads and imports, including upload_max_filesize, max_input_time, max_execution_time, memory_limit, and more. See:

• http://ca.php.net/manual/en/features.file-upload.common-pitfalls.php
• https://www.accesstomemory.org/docs/latest/admin-manual/installation/execution-limits/
  

These settings are generally maintained in the php.ini file in your environment. The confusing part is that the location of this file is not consistent, and there can even be more than one file - one for your browser settings, and one for the command-line, for example. Here are a couple of links to help you locate it:

• https://www.howtogeek.com/50853/find-the-php-ini-file-location-from-the-command-line/
• https://www.templatemonster.com/blog/where-is-php-ini/

If you make changes to any of the PHP configuration files, you should clear your application cache and restart PHP-FPM after.

To clear the application cache, run the following from the root AtoM directory:

• php symfony cc

To restart PHP-FPM, you can use the following command, depending on you operating system:

• On Ubuntu 14.04 - sudo service php5-fpm restart
• On Ubuntu 16.04 sudo systemctl restart php7.0-fpm

Please note - changing these and other values might still not allow you to upload large files via your user interface! Most browsers have a built-in timeout limit of about 1 minute, and a large upload is likely to time out in the browser before completing. This means that even if you increase all of the values listed above, your browser may still terminate the upload of a large file before it can complete.

There are a couple of workarounds for this.

First, the CSV import template can include 2 columns for importing digital objects:

• digitalObjectURI can be used to link to external digital objects that are accessible on the web - the URI must end in a file extension for this to work
• digitalObjectPath can be used to import local digital objects that have been loaded onto your server
• See: https://www.accesstomemory.org/docs/2.3/user-manual/import-export/csv-import/#digital-object-related-import-columns

In our upcoming AtoM 2.4 release, imports are being handled by the job scheduler so they can be performed asynchronously in the background, instead of synchronously by the browser when you initiate the upload. This will prevent imports from timing out in the browser. In the meantime, you can use the command-line import to create new item level descriptions and attach digital objects to them at the same time, using this method.

There is also a command-line task to import digital objects and attach them to existing descriptions. See:

• https://www.accesstomemory.org/docs/latest/user-manual/import-export/csv-import/#load-digital-objects-via-the-command-line
  

I hope this helps!

Regards,

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--
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-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/f914fe4f-0bf0-444b-b34d-8b58d87e9ac1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[binay...@gmail.com]

Hi Dan,

Thanks for the Reply.

Is there anyway we can increase the timeout value for the larger file upload?

Or it is always advised to go for command line upload for larger file.

Regards

Binaya

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.

[Dan Gillean]

Hi Binaya,

You can increase the PHP settings such as max_input_time and max_execution_time on the server side. On the browser side, there are ways to change the default timeout settings - do a quick search based on your preferred browser. However, letting services run without a timeout limit on your server and in your browser can be very insecure, and can also affect the performance of the application as a whole. For large digital objects, the command-line is still probably the best way to upload them for now.

The long-term solution is for us to add support for asynchronous digital object imports, using the job scheduler. This will require development which, for Artefactual to be able to undertake, would require either code contributions from the community, or development sponsorship. For more on our business model and how we maintain and develop AtoM, please see:

• https://wiki.accesstomemory.org/Development/Philosophy

Cheers,

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.

Visit this group at https://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/fcc921bb-3bdb-40c7-ba99-22930d72c6a4%40googlegroups.com.