eprints_tech messages

From: Francis Jayakanth <franc AT ncsi.iisc.ernet.in>
Date: Wed, 1 Oct 2008 13:20:32 +0530 (IST)

*** ↵
http://www.eprints.org/tech.php/id/%3CEMEW-k908YV46891e40f842d1d80d0af8d1cb149de0-Pine.LNX.4.64.0810011309190.14627%40ncsi.iisc.ernet.in%3E
*** EPrints community wiki - http://wiki.eprints.org/

We also had same issue while migrating from 2.3.13.1 to EP3. This is what 
I did:

In EP3 'related_url' is same as 'altloc' of EP2. Before you create the 
eprints tables, add the field 'altloc' in the eprints_fields.pl file. This 
will ensure that the contents of 'altloc' is not lost while migrating. 
Later, you can trnasfer the contents of 'altloc' filed to related_url 
field by using the following SQL statement or retain the 'altloc' field 
itself:

insert into eprint.related_url (eprintid,pos,related_url_url) select 
eprintid,pos,eprint_altloc) from eprint_altloc

Hope this helps.

  - Francis


On Tue, 30 Sep 2008, Ranju Upadhyay wrote:

> In further digging , I found out that the particular item which lost its ↵
alternative location , was a conference paper in ep2. When we brought this item ↵
in to ep3, it lost its type (i.e. the item had no types assigned) .I wonder if ↵
that is the reason this item lost its altloc as well.Would anyone know what do ↵
I need to do make sure that items of all types in ep2 get their respective ↵
types assigned in ep3?Has anyone else come across similar ↵
problem?ThanksRanju,NUIM,Ireland.
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.