[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Handle-info] Dspace - Two Instances Migrations
Hi Scott,
Just reading http://www.elook.org/computing/rfc/rfc3651-21.html about HS_ALIAS
This seems like a viable solution with the HS_ALIAS. Each handle would need its HS_ALIAS set to the new one, where does this happen? The Handle Server config file?
Once the replication takes place, are you saying that you can switch off the 2100 Handle server as it will be no longer needed and the redirect will still take place?
Thanks for your help
George
-----Original Message-----
From: Scott Prater [mailto:prater@wisc.edu]
Sent: Saturday, 25 August 2012 12:22 AM
To: George Rokkas
Cc: Bram Luyten; handle-info@cnri.reston.va.us; DSpace Tech
Subject: Re: [Handle-info] Dspace - Two Instances Migrations
Hello, George,
I don't know much about DSpace, but I can talk about some options in the handle server realm. You could simply add HS_ALIAS values to your old handles, pointing to the new handles: then the handle server should redirect.
Is it a requirement that the migrated handles have new IDs? If the goal is simply to migrate the handles, and maintaining the IDs is an option, you could set up your new handle server as a mirror of the current one, let the replication happen, then break the mirror and turn off the old server.
-- Scott
On 08/24/2012 02:39 AM, George Rokkas wrote:
> Hi Bram,
>
> Thanks for the reply.
>
> 1.It's a permanent move
>
> 2.Yes both their own handle servers: 2100 and 10453
>
> 3.It will be shut down, I was planning on bringing the shutdown handle
> across to the second repo.
>
> Thanks
>
> George
>
> *From:*bluyten@gmail.com [mailto:bluyten@gmail.com] *On Behalf Of
> *Bram Luyten
> *Sent:* Friday, 24 August 2012 5:20 PM
> *To:* George Rokkas
> *Cc:* handle-info@cnri.reston.va.us; DSpace Tech
> *Subject:* Re: [Handle-info] Dspace - Two Instances Migrations
>
> Hi George,
>
> a few questions to make sure I totally understand what you're trying
> to
> accomplish:
> - you're trying to permanently move these items from one DSpace to
> another, right?
> - Are both DSpace installations running their own handle server?
> - Do you have any items left in the first repository, after this
> migration? e.g. will you keep using two handle prefixes in the end
> situation?
>
> Also copying your email to the DSpace-Tech mailing list. In case
> you're not subscribed there, you can find the info here:
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
> best regards,
>
> Bram Luyten
>
> --
>
> 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_medi
> um=email&utm_campaign=braml>
>
>
>
> On Fri, Aug 24, 2012 at 4:44 AM, George Rokkas
> <George.Rokkas@uts.edu.au <mailto:George.Rokkas@uts.edu.au>> wrote:
>
> Hey All,
>
> I'm new around here. I'm George and I'm the systems architect at
> University of Technology, Sydney Library.
>
> We currently have two Dspace instances running side by side and we
> want to bring 900 items from instance1 to instance 2. We've managed to
> work out how to do this via AIP export and import which assigns each
> item with a new handle. What I'm trying to find out is that if an item
> had the handle /2100/803 and now has /10453/17883. Can I get the
> original handle to redirect to the new one without having to do a
> redirect at the web server level.
>
> I'm really appreciative of any help I could get.
>
> Thank You
>
> George Rokkas
>
> UTS CRICOS Provider Code: 00099F
> DISCLAIMER: This email message and any accompanying attachments may
> contain confidential information.
> If you are not the intended recipient, do not read, use, disseminate,
> distribute or copy this message or attachments. If you have received
> this message in error, please notify the sender immediately and delete
> this message. Any views expressed in this message are those of the
> individual sender, except where the sender expressly, and with
> authority, states them to be the views of the University of Technology
> Sydney.
> Before opening any attachments, please check them for viruses and defects.
>
> Think. Green. Do.
>
> Please consider the environment before printing this email.
>
> UTS CRICOS Provider Code: 00099F
> DISCLAIMER: This email message and any accompanying attachments may
> contain confidential information.
> If you are not the intended recipient, do not read, use, disseminate,
> distribute or copy this message or attachments. If you have received
> this message in error, please notify the sender immediately and delete
> this message. Any views expressed in this message are those of the
> individual sender, except where the sender expressly, and with
> authority, states them to be the views of the University of Technology
> Sydney.
> Before opening any attachments, please check them for viruses and defects.
>
> Think. Green. Do.
>
> Please consider the environment before printing this email.
--
Scott Prater
Shared Development Group
General Library System
University of Wisconsin - Madison
prater@wisc.edu
5-5415
UTS CRICOS Provider Code: 00099F
DISCLAIMER: This email message and any accompanying attachments may contain confidential information.
If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or
attachments. If you have received this message in error, please notify the sender immediately and delete
this message. Any views expressed in this message are those of the individual sender, except where the
sender expressly, and with authority, states them to be the views of the University of Technology Sydney.
Before opening any attachments, please check them for viruses and defects.
Think. Green. Do.
Please consider the environment before printing this email.
_______________________________________________
Handle-Info mailing list
Handle-Info@cnri.reston.va.us
http://www.handle.net/mailman/listinfo/handle-info