Re: [atom-users] Uploading digital objects to a different server using AtoM GUI

[Dan Gillean]

Hi Mario, 

Thank you for sharing this! I hope it might be useful to others. Would you mind if I add it to our wiki, in the Community documentation?

• https://wiki.accesstomemory.org/Community/Community_resources/Documentation
  

Cheers, 

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

@accesstomemory

he / him

On Wed, Nov 4, 2020 at 12:35 PM Mario Villar <hdig...@gmail.com> wrote:

Hi all,

By default, AtoM saves the digital objects that we upload in the server's own storage unit where it is hosted, in the "uploads" directory.
Sooner or later when we handle audio files as is my personal case, the disk capacity will fill up.

While there is the option of CSV importing digital objects pointing to an external path, or linking to an external server, many users are more comfortable using the built-in GUI.

In order to get the digital objects to be stored on an external network drive, in my case a NAS, I followed the following steps that I share with you in case someone finds it useful :

1 - Mount network drive via "mount" command, for example in /media /SHARED

(It's up to you the syntax used in the command)

2 - Add to / etc / fstab:

//IPOFEXTERNALSERVER / media / SHARED cifs uid = 33, username = (YOURUSERNAME), vers = 1.0, password = (YOURPASSWORD), sec = ntlm, iocharset = utf8, gid = 33 0 0

I'm using v 1.0 of cifs to maximize compatibility with older NAS boxes, as my case. For newer boxes, you can use 3.0

3 - Rename the "uploads" folder within the AtoM working directory to "uploads_old" for example.

4 - Create a symbolic link called "uploads" that points to where we mount the network drive.

5 - Give 755 permissions to the destination network drive, and change the owner of it to "www-data (33)", as well as the group. Do it recursively.

1 - Mount network drive via mount command, for example in / media / SHARED

2 - Add to / etc / fstab:

//192.168.10.203/pools/A/A0/ARNU / media / SHARED cifs uid = 33, username = mvillar, vers = 1.0, password = MV8600coc, sec = ntlm, iocharset = utf8, gid = 33 0 0

3 - Rename the "uploads" folder within the AtoM working directory to "uploads_old" for example.

4 - Create a symbolic link called "uploads" that points to where we mount the network drive.

6 - Regenerate the derivatives of digital objects.

Tested on Ubuntu 18.04.
It is recommended for ease of use using Webmin, going to the part of "Disk And Network Filesystem" in the "System" section.
In my particular case the type of mount point corresponds to the CIFS protocol. We can also using Webmin select which type of protocol or flie system we prefer.

--
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/5536e80e-1803-4fc3-8780-f27caf1897b2n%40googlegroups.com.

[Mario Villar]

Hi Dan,

I've made a corrected and updated version. Here follows :

"By default, AtoM saves the digital objects that we upload in the server's own storage unit where it is hosted, in the "uploads" directory.
Sooner or later when we handle audio files as is my personal case, the disk capacity will fill up.

While there is the option of CSV importing digital objects pointing to an external path, or linking to an external server, many users are more comfortable using the built-in GUI.
In order to get the digital objects to be stored on an external network drive, in my case a NAS, I followed the following steps that I share with you in case someone finds it useful :

1 - Mount network drive via "mount" command, for example in /media /SHARED

It could be done using SMB or CIFS protocol.
First we must install the packages, it's up to you the one chosen :

apt-get install smbfs smbclient

or

apt-get install cifs-utils

Then

apt-get update

Now, we check connection and shares of the external server :

smbclient -L IPOFEXTERNALSERVER -U USERNAME

It should display the network shares available on the server

According to the protocol enabled on external server, we mount the unit.
If using SMB :

mount -t smbfs -o username=YOURUSERNAME //IPOFEXTERNALSERVER/SHARE_NAME /MOUNT_POINT -o OPTIONS

If using CIFS (recommended):

mount -t cifs //IPOFEXTERNALSERVER /MOUNT_POINT -o OPTIONS

2 - Add to / etc / fstab:

//IPOFEXTERNALSERVER / media / SHARED cifs uid = 33, username = (YOURUSERNAME), vers = 1.0, password = (YOURPASSWORD), sec = ntlm, iocharset = utf8, gid = 33 0 0

I'm using v 1.0 of cifs to maximize compatibility with older NAS boxes, as my case. For newer boxes, you can use 3.0

3 - Rename the "uploads" folder within the AtoM working directory to "uploads_old" for example.

4 - Create a symbolic link called "uploads" that points to where we mount the network drive.

5 - Give 755 permissions to the destination network drive, and change the owner of it to "www-data (33)", as well as the group. Do it recursively.

1 - Mount network drive via mount command, for example in / media / SHARED

2 - Add to / etc / fstab:

//IPOFEXTERNALSERVER/SHARENAME / media / SHARED cifs uid = 33, username = USERNAME, vers = 1.0, password = YOURPASSWORD, sec = ntlm, iocharset = utf8, gid = 33 0 0

3 - Rename the "uploads" folder within the AtoM working directory to "uploads_old" for example.

4 - Create a symbolic link called "uploads" that points to where we mount the network drive.

6 - Regenerate the derivatives of digital objects.

Tested on Ubuntu 18.04.
It is recommended for ease of use using Webmin, going to the part of "Disk And Network Filesystem" in the "System" section.
In my particular case the type of mount point corresponds to the CIFS protocol. We can also using Webmin select which type of protocol or flie system we prefer."

It will be a honor to see that added to the wiki

Cheers

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZJt_mE0VB%3DKjqwd-%3DVTdOukkAZ%3D%3Dk9GPFhaDZQqUsOhPA%40mail.gmail.com.

--

Mario Villar Corbo

http://www.vulneratomnes.blogspot.com

[Dan Gillean]

Thank you Mario! 

I have added your instructions to our wiki, here: 

• https://wiki.accesstomemory.org/wiki/Community/Community_resources/Documentation#Configuring_AtoM_uploads_to_be_stored_on_a_different_server
  

Cheers, 

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

@accesstomemory

he / him

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAJ%3DC-4sbqix6W-xSSqofgnPK%2BKMg8iV46f-UT3VGj03sA%2B-1iw%40mail.gmail.com.