Hi Sandy,

like helix indicates, it would be challenging to ensure that your handles,
or your currently existing url's will still correctly resolve. However,
making sure that your URLs keep resolving and that the Google Pagerank you
have built up for your repository domain doesn't get lost should be closely
considered in such a project.

What is your primary motive for splitting out the repository in different
instances? Manakin XMLUI enables you to create different themes per
collection/community. So if it comes down to the look and feel, or simply
making it look like different systems, there are already a lot of things
you can do in one instance.

kindest regards,

Bram Luyten

-- 
[image: logo]
*Bram Luyten* *@mire*
*2888 Loker Avenue East, Suite 305, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
  
<http://www.atmire.com/>www.atmire.com<http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml>


On Mon, Jun 4, 2012 at 11:23 AM, helix84 <[email protected]> wrote:

> On Sat, Jun 2, 2012 at 1:20 AM, Sandy De Groote <[email protected]> wrote:
> > Hello All,
> > We are going to be migrating our IR to a new server, moving content from
> > Dspace 1.4 (after possible upgrade to 1.5) to Dspace 1.6.2 (with a new
> > server).  At this time we want to separate our Universities Archives
> > (which is contained in one main community with many sub collections and
> > communities) from the the scholarly content (the rest of the IR).   We
> > are not sure how to best do this.   Is it best to move contents of the
> > entire IR and delete the contents on the two separate servers that are
> > no longer desired or move only the desired content from one IR to the
> > other (and how more complicated does it become to pick and choose
> > content to move).
> >
> > Any one have any advice or any insight into how easy/difficult this will
> > be and which method would be the best to consider (if even advisable)?
>
> Hi Sandy,
>
> since you want to split the server, I assume you don't use and are not
> going to use Handle.net.
>
> Both approaches (cloning dspace into 2 instances; export/import of
> partial structure) would work just fine.
> 1) I strongly recommend you do not stop at 1.6 but continue to 1.8
> 2) Make sure you upgrade to the latest version first thing
> 3) Make sure to follow upgrade instructions at
> <
> https://wiki.duraspace.org/display/DSDOC18/Upgrading+a+DSpace+Installation
> >.
> You don't have to install the code for each version, but you do have
> to do each DB schema upgrade and configuration changes in correct
> order. It saves a lot of potential trouble later. Also, I strongly
> recommend you start with a fresh config/ directory of the latest
> version and modify what you need (instead of trying to add new config
> variables to your 1.4 config).
>
> So I assume you have an old server and two new machines. Here's what I
> would do:
> 1) install DSpace 1.8.2 on the new server
> 2) copy the assetstore to the new server
> 3) export database and import it to the new server (you can overwrite
> the installed empty database)
> 4) run the db upgrade scripts on the new server as per documentation
> 5) starting with a fresh 1.8.2 config, modify it for your institution
> 6) read upgrading documentation again to make sure you didn't miss any
> steps
> 7) start Tomcat
> 8) test, test, test everything
>
> At this point you have a copy of your old DSpace at the new server
> upgraded to DSpace 1.8.2. Since DSpace 1.7, you can do exports in AIP
> format. If you decide to do export/import, I recommend you use AIP:
> <https://wiki.duraspace.org/display/DSDOC18/AIP+Backup+and+Restore>
>
> Now you have 2 options:
> 1) AIP export/import
> 2) Clone the whole new server to the second new server (install
> DSspace 1.8.2, copy over DB & assetstore and configuration), change
> hostname etc., delete redundant contents from each server.
>
> If you have any questions, don't hesitate to ask.
>
> Regards,
> ~~helix84
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to