Re: [dspace-tech] Upgrading Dspace 4.3 to 6.2 re-using usage events of previous years (statistics)

[Tim Donohue]

Hi Lewatle,

You should be very careful about copying custom code from 4.x to 6.x, as
both the webapps and the Java API have changed quite a bit between those
releases.  So, I worry that simply copying everything from your dspace 4.x
webapps into your DSpace 6 codebase would result in a large number of
errors.  DSpace code is constantly improving, so if you simply copy all
your files from an old version of DSpace, that old code is not guaranteed
to work with a much newer version of DSpace.

Instead, assuming you are using a code repository (like Git or SVN), you
may want to either perform a code merge, or generate a diff/patch (from
your 4.3 site), so that you can only reapply the customizations you've made
to the 6.x site.  If the customizations are minimal (e.g. header/footer/css
changes), you may end up better off simply upgrading to out-of-the-box
DSpace 6, and then manually reapplying your customizations after the
initial upgrade is found to be successful.

The upgrade process itself should take care of moving forward any
statistics you have had previously. So, as long as you are upgrading on the
same server, you should be able to just follow the normal upgrade process
documented at:
https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace

Since you've made customizations, I highly recommend testing your upgrade
process on a test server. That way you can work out any issues on that test
server before attempting it on Production (and you won't have to worry so
much if you hit a bump in the road, as you'll have time to resolve it
without affecting your Production site).

Good luck. If you hit more specific issues during your test of the upgrade,
feel free to email this mailing list or use on of the other support options
available: https://wiki.duraspace.org/display/DSPACE/Support

- Tim


On Tue, Sep 12, 2017 at 5:01 AM Lewatle Johannes Phaladi 
wrote:

> Dear DSpace Team,
>
> I am going to be upgrading soon to version 6.x and I have done most
> customizations on test site, the only last stage I haven't done yet is on
> migrating statisctics and keep on having previous usage stats going forward.
>
> please rectify me on this steps if i am getting it wrong:
> I would copy all customizations from  webbapps directory as follows
>  $ cp -R dspace4.3/webapps to
> /dspace-6.2-src-release/dspace/modules/jspui/src/main/
> then run  /dspace-6.2-src-release/dspace$ mvn package
> and also /dspace-6.2-src-release/dspace/target/dspace-installer/$ ant
> update
>
> will the above process be able to re-use old stats to the new installation
> ?
>
> Regards,
> Lewatle
>
> --
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Upgrading Dspace 4.3 to 6.2 re-using usage events of previous years (statistics)

[Lewatle Johannes Phaladi]

Hi Tim,

Thanks very much for detailed explanation and definitely I will follow your 
advise and not copy files to new downloaded DSpace 6.x as you metioned 
there is several changes and it is better to upgrade normaly and do 
customizations manually. On stats when I read upgrade steps there is no 
where I saw detailing even after installation is completed how to copy 
dspace4.3install/webapps/solr to new  dspace6.2install/webapps/solr is this 
process going to happen automatically like it is happening on discovery, in 
all the upgrade i have done, there is no one occasion where I have managed 
to upgrade and have previous statistics, everytime we started from that 
month of upgrade and that is not well on my side because old stats should 
be reused.

I am not using Git or SVN.

Regards,
Lewatle 

On Tuesday, 12 September 2017 16:25:47 UTC+2, Tim Donohue wrote:
>
> Hi Lewatle,
>
> You should be very careful about copying custom code from 4.x to 6.x, as 
> both the webapps and the Java API have changed quite a bit between those 
> releases.  So, I worry that simply copying everything from your dspace 4.x 
> webapps into your DSpace 6 codebase would result in a large number of 
> errors.  DSpace code is constantly improving, so if you simply copy all 
> your files from an old version of DSpace, that old code is not guaranteed 
> to work with a much newer version of DSpace.  
>
> Instead, assuming you are using a code repository (like Git or SVN), you 
> may want to either perform a code merge, or generate a diff/patch (from 
> your 4.3 site), so that you can only reapply the customizations you've made 
> to the 6.x site.  If the customizations are minimal (e.g. header/footer/css 
> changes), you may end up better off simply upgrading to out-of-the-box 
> DSpace 6, and then manually reapplying your customizations after the 
> initial upgrade is found to be successful.
>
> The upgrade process itself should take care of moving forward any 
> statistics you have had previously. So, as long as you are upgrading on the 
> same server, you should be able to just follow the normal upgrade process 
> documented at:
> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
>
> Since you've made customizations, I highly recommend testing your upgrade 
> process on a test server. That way you can work out any issues on that test 
> server before attempting it on Production (and you won't have to worry so 
> much if you hit a bump in the road, as you'll have time to resolve it 
> without affecting your Production site).
>
> Good luck. If you hit more specific issues during your test of the 
> upgrade, feel free to email this mailing list or use on of the other 
> support options available: 
> https://wiki.duraspace.org/display/DSPACE/Support
>
> - Tim
>
>
> On Tue, Sep 12, 2017 at 5:01 AM Lewatle Johannes Phaladi <
> joem...@gmail.com > wrote:
>
>> Dear DSpace Team,
>>
>> I am going to be upgrading soon to version 6.x and I have done most 
>> customizations on test site, the only last stage I haven't done yet is on 
>> migrating statisctics and keep on having previous usage stats going forward.
>>
>> please rectify me on this steps if i am getting it wrong:
>> I would copy all customizations from  webbapps directory as follows 
>>  $ cp -R dspace4.3/webapps to 
>> /dspace-6.2-src-release/dspace/modules/jspui/src/main/
>> then run  /dspace-6.2-src-release/dspace$ mvn package 
>> and also /dspace-6.2-src-release/dspace/target/dspace-installer/$ ant 
>> update
>>
>> will the above process be able to re-use old stats to the new 
>> installation ?
>>
>> Regards,
>> Lewatle 
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
>
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Upgrading Dspace 4.3 to 6.2 re-using usage events of previous years (statistics)

[Tim Donohue]

Hi Lewatle,

Your Solr Statistics data is *not* stored in [dspace]/webapps/solr/.  That
directory is just the Solr web application, and you should have no need to
copy that into the DSpace 6 upgraded site. That Solr web application will
be upgraded automatically for you.

Instead, your Solr Statistics data is stored in the [dspace]/solr/ folder.
That is the Solr data directory. It will not be replaced or overwritten
during the upgrade, and your statistics will remain in tact. So, there is
nothing you should need to do, as that [dspace]/solr folder will not be
touched during the upgrade process, and all your old statistics should
still work in DSpace 6.

Again, I'd highly recommend first trying the upgrade process on a test
server so there are no surprises.  This is especially important as you are
not using Git or SVN to manage your customizations. You should be very
careful to test the upgrade and re-customization process before you do it
on Production.  As a sidenote, if you find yourself beginning to highly
customize DSpace, you may wish to reconsider whether you store those
customizations in Git or SVN, as doing so helps to backup/maintain your
changes, so that there's less danger of accidentally losing your
customizations any time you upgrade your site.

Good luck,

Tim

On Wed, Sep 13, 2017 at 7:35 AM Lewatle Johannes Phaladi 
wrote:

> Hi Tim,
>
> Thanks very much for detailed explanation and definitely I will follow
> your advise and not copy files to new downloaded DSpace 6.x as you metioned
> there is several changes and it is better to upgrade normaly and do
> customizations manually. On stats when I read upgrade steps there is no
> where I saw detailing even after installation is completed how to copy
> dspace4.3install/webapps/solr to new  dspace6.2install/webapps/solr is this
> process going to happen automatically like it is happening on discovery, in
> all the upgrade i have done, there is no one occasion where I have managed
> to upgrade and have previous statistics, everytime we started from that
> month of upgrade and that is not well on my side because old stats should
> be reused.
>
> I am not using Git or SVN.
>
> Regards,
> Lewatle
>
>
> On Tuesday, 12 September 2017 16:25:47 UTC+2, Tim Donohue wrote:
>
>> Hi Lewatle,
>>
>> You should be very careful about copying custom code from 4.x to 6.x, as
>> both the webapps and the Java API have changed quite a bit between those
>> releases.  So, I worry that simply copying everything from your dspace 4.x
>> webapps into your DSpace 6 codebase would result in a large number of
>> errors.  DSpace code is constantly improving, so if you simply copy all
>> your files from an old version of DSpace, that old code is not guaranteed
>> to work with a much newer version of DSpace.
>>
>> Instead, assuming you are using a code repository (like Git or SVN), you
>> may want to either perform a code merge, or generate a diff/patch (from
>> your 4.3 site), so that you can only reapply the customizations you've made
>> to the 6.x site.  If the customizations are minimal (e.g. header/footer/css
>> changes), you may end up better off simply upgrading to out-of-the-box
>> DSpace 6, and then manually reapplying your customizations after the
>> initial upgrade is found to be successful.
>>
>> The upgrade process itself should take care of moving forward any
>> statistics you have had previously. So, as long as you are upgrading on the
>> same server, you should be able to just follow the normal upgrade process
>> documented at:
>> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
>>
>> Since you've made customizations, I highly recommend testing your upgrade
>> process on a test server. That way you can work out any issues on that test
>> server before attempting it on Production (and you won't have to worry so
>> much if you hit a bump in the road, as you'll have time to resolve it
>> without affecting your Production site).
>>
>> Good luck. If you hit more specific issues during your test of the
>> upgrade, feel free to email this mailing list or use on of the other
>> support options available:
>> https://wiki.duraspace.org/display/DSPACE/Support
>>
>> - Tim
>>
>>
>> On Tue, Sep 12, 2017 at 5:01 AM Lewatle Johannes Phaladi <
>> joem...@gmail.com> wrote:
>>
> Dear DSpace Team,
>>>
>>> I am going to be upgrading soon to version 6.x and I have done most
>>> customizations on test site, the only last stage I haven't done yet is on
>>> migrating statisctics and keep on having previous usage stats going forward.
>>>
>>> please rectify me on this steps if i am getting it wrong:
>>> I would copy all customizations from  webbapps directory as follows
>>>  $ cp -R dspace4.3/webapps to
>>> /dspace-6.2-src-release/dspace/modules/jspui/src/main/
>>> then run  /dspace-6.2-src-release/dspace$ mvn package
>>> and also /dspace-6.2-src-release/dspace/target/dspace-installer/$ ant
>>> update
>>>
>>> will the above process be able to re-use old stats to the new
>>> inst

Re: [dspace-tech] Upgrading Dspace 4.3 to 6.2 re-using usage events of previous years (statistics)

[Lewatle Johannes Phaladi]

Hi Tim,

Thank you very much for clear explanation and yes I have started upgrading 
on test server and all seems to go well, i will do nothing on stats upgrade 
and run the upgrade following this documentation : 
https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace 

 

Regards,
Lewatle 

On Wednesday, 13 September 2017 15:57:15 UTC+2, Tim Donohue wrote:
>
> Hi Lewatle,
>
> Your Solr Statistics data is *not* stored in [dspace]/webapps/solr/.  That 
> directory is just the Solr web application, and you should have no need to 
> copy that into the DSpace 6 upgraded site. That Solr web application will 
> be upgraded automatically for you.
>
> Instead, your Solr Statistics data is stored in the [dspace]/solr/ folder. 
> That is the Solr data directory. It will not be replaced or overwritten 
> during the upgrade, and your statistics will remain in tact. So, there is 
> nothing you should need to do, as that [dspace]/solr folder will not be 
> touched during the upgrade process, and all your old statistics should 
> still work in DSpace 6.  
>
> Again, I'd highly recommend first trying the upgrade process on a test 
> server so there are no surprises.  This is especially important as you are 
> not using Git or SVN to manage your customizations. You should be very 
> careful to test the upgrade and re-customization process before you do it 
> on Production.  As a sidenote, if you find yourself beginning to highly 
> customize DSpace, you may wish to reconsider whether you store those 
> customizations in Git or SVN, as doing so helps to backup/maintain your 
> changes, so that there's less danger of accidentally losing your 
> customizations any time you upgrade your site.
>
> Good luck,
>
> Tim
>
> On Wed, Sep 13, 2017 at 7:35 AM Lewatle Johannes Phaladi <
> joem...@gmail.com > wrote:
>
>> Hi Tim,
>>
>> Thanks very much for detailed explanation and definitely I will follow 
>> your advise and not copy files to new downloaded DSpace 6.x as you metioned 
>> there is several changes and it is better to upgrade normaly and do 
>> customizations manually. On stats when I read upgrade steps there is no 
>> where I saw detailing even after installation is completed how to copy 
>> dspace4.3install/webapps/solr to new  dspace6.2install/webapps/solr is this 
>> process going to happen automatically like it is happening on discovery, in 
>> all the upgrade i have done, there is no one occasion where I have managed 
>> to upgrade and have previous statistics, everytime we started from that 
>> month of upgrade and that is not well on my side because old stats should 
>> be reused.
>>
>> I am not using Git or SVN.
>>
>> Regards,
>> Lewatle 
>>
>>
>> On Tuesday, 12 September 2017 16:25:47 UTC+2, Tim Donohue wrote:
>>
>>> Hi Lewatle,
>>>
>>> You should be very careful about copying custom code from 4.x to 6.x, as 
>>> both the webapps and the Java API have changed quite a bit between those 
>>> releases.  So, I worry that simply copying everything from your dspace 4.x 
>>> webapps into your DSpace 6 codebase would result in a large number of 
>>> errors.  DSpace code is constantly improving, so if you simply copy all 
>>> your files from an old version of DSpace, that old code is not guaranteed 
>>> to work with a much newer version of DSpace.  
>>>
>>> Instead, assuming you are using a code repository (like Git or SVN), you 
>>> may want to either perform a code merge, or generate a diff/patch (from 
>>> your 4.3 site), so that you can only reapply the customizations you've made 
>>> to the 6.x site.  If the customizations are minimal (e.g. header/footer/css 
>>> changes), you may end up better off simply upgrading to out-of-the-box 
>>> DSpace 6, and then manually reapplying your customizations after the 
>>> initial upgrade is found to be successful.
>>>
>>> The upgrade process itself should take care of moving forward any 
>>> statistics you have had previously. So, as long as you are upgrading on the 
>>> same server, you should be able to just follow the normal upgrade process 
>>> documented at:
>>> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
>>>
>>> Since you've made customizations, I highly recommend testing your 
>>> upgrade process on a test server. That way you can work out any issues on 
>>> that test server before attempting it on Production (and you won't have to 
>>> worry so much if you hit a bump in the road, as you'll have time to resolve 
>>> it without affecting your Production site).
>>>
>>> Good luck. If you hit more specific issues during your test of the 
>>> upgrade, feel free to email this mailing list or use on of the other 
>>> support options available: 
>>> https://wiki.duraspace.org/display/DSPACE/Support
>>>
>>> - Tim
>>>
>>>
>>> On Tue, Sep 12, 2017 at 5:01 AM Lewatle Johannes Phaladi <
>>> joem...@gmail.com> wrot