upgrading and the downloads directory

[Elizabeth Thomson]

Hello AtoM folks,

We are currently upgrading from 2.3.1 to 2.4.0 (on RHEL7.4), so far with no issues. However, I wonder how to handle the 'downloads' directory. The upgrade documentation makes specific mention of the 'uploads' directory as being a directory which should rsynched in order to preserve content, but makes no mention of the 'downloads' directory, which I gather is where reports are stored.

Should the 'downloads' directory also be rsynched during an upgrade, or should reports be regenerated following an upgrade?

Many thanks!

[Dan Gillean]

Hi Elizabeth, 

Good point! The Downloads directory is fairly new - as you've noted, reports (that are now generated asynchronously in AtoM), and any cached XML, are stored there. 

Yes, you can follow the same approach rsync approach to copy the contents of this directory to your new AtoM instance. I will try to update the documentation to reflect this soon. Thanks for pointing this out. 

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/0f6d1c06-df48-43ed-9bdc-e8167f714bc6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Elizabeth Thomson]

Many thanks Dan,

We will add this step to our upgrade process.

best regards,

On Wednesday, 22 November 2017 10:52:55 UTC-5, Dan Gillean wrote:

Hi Elizabeth, 

Good point! The Downloads directory is fairly new - as you've noted, reports (that are now generated asynchronously in AtoM), and any cached XML, are stored there. 

Yes, you can follow the same approach rsync approach to copy the contents of this directory to your new AtoM instance. I will try to update the documentation to reflect this soon. Thanks for pointing this out. 

Regards, 

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

@accesstomemory

On Wed, Nov 22, 2017 at 9:54 AM, Elizabeth Thomson <elizabet...@mcgill.ca> wrote:

Hello AtoM folks,

We are currently upgrading from 2.3.1 to 2.4.0 (on RHEL7.4), so far with no issues. However, I wonder how to handle the 'downloads' directory. The upgrade documentation makes specific mention of the 'uploads' directory as being a directory which should rsynched in order to preserve content, but makes no mention of the 'downloads' directory, which I gather is where reports are stored.

Should the 'downloads' directory also be rsynched during an upgrade, or should reports be regenerated following an upgrade?

Many thanks!

--
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 post to this group, send email to ica-ato...@googlegroups.com.

[Dan Gillean]

Hi Elizabeth,

Just a quick note to say that I've updated the documentation, here: 

• https://www.accesstomemory.org/docs/2.4/admin-manual/installation/upgrading/#copy-your-old-data
  

You may be interested in seeing the note I've added about deleting the contents of the jobs subdirectory, if desired. 

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/b3c1a608-6b63-4aac-8236-c4c83da1a103%40googlegroups.com.