CUNY Academic Commons

Hi All -- I've added Luke, Kimon, and Laura as watchers of this ticket.

HI Boone,

I'm sorry if I was not clear. Could you please migrate the files that have been uploaded to the staging site since December 2017?
I have to migrate all articles by February 20.

Thank you for your help.

Boone Gorges wrote:

Hi Alessandro,

Sure, I'd be happy to help. Can you help me to understand better what exactly you want to migrate?

Do you want the exact state of the entire jitpstaging site cloned over to the JITP production site? Note that a complete clone will include all settings, and will also mean that any changes that have taken place to the production site since the staging site was originally cloned (such as new comments) will be lost.

If you mean something other than a complete clone of this sort, can you please give more detail on the content that needs migration? If it's very fine-grained, it may not be possible to do in a non-manual fashion.

I can give you an estimate on the timeline once I have a better understanding of what's being asked for. If you can give me a better sense of your specifci deadlines, it will help me understand the context.

Thanks for the clarification, Alessandro. I have synced all files uploaded in December 2017 or Jan/Feb 2018 from jitpstaging to jitp. You will not see these items in the Media Library on jitp.commons, but the files themselves are in the proper directory. So, for example, the original https://jitpstaging.commons.gc.cuny.edu/files/2017/12/mathewsfig9.jpg has been copied to https://jitp.commons.gc.cuny.edu/files/2017/12/mathewsfig9.jpg. When migrating article content, you should just be able to swap out the URL 'jitpstaging.commons' for 'jitp.commons'.

Let me know if this is enough to get you moving.

Dear Boone,

Thank you very much for your prompt support.
It works perfectly!

Best,
Alessandro
Boone Gorges wrote:

Thanks for the clarification, Alessandro. I have synced all files uploaded in December 2017 or Jan/Feb 2018 from jitpstaging to jitp. You will not see these items in the Media Library on jitp.commons, but the files themselves are in the proper directory. So, for example, the original https://jitpstaging.commons.gc.cuny.edu/files/2017/12/mathewsfig9.jpg has been copied to https://jitp.commons.gc.cuny.edu/files/2017/12/mathewsfig9.jpg. When migrating article content, you should just be able to swap out the URL 'jitpstaging.commons' for 'jitp.commons'.

Let me know if this is enough to get you moving.

Boone-- quick question on this process, which we need to repeat again soon for the upcoming issue release.

Are you just copying over the uploads folder from jitpstaging to jitp to complete this step? Just verifying (for search/replace purposes) that if the copy is done in June when the upload occurred in May that the path to the file on the production site will still reflect a original May upload date.

Thx-

Are you just copying over the uploads folder from jitpstaging to jitp to complete this step? Just verifying (for search/replace purposes) that if the copy is done in June when the upload occurred in May that the path to the file on the production site will still reflect a original May upload date.

I'll sync the specific directories you ask me to sync, and use the same paths for the source and destination. So if you want /2018/05/, I'll sync it to /2018/05/ on the production site. Date-related paths will not change - just the domain name.