See the Mailing Lists Page for how to subscribe and unsubscribe.
eprints_tech messages
Please note: this page shows emails that have been sent to the eprints_tech mailing list. Some of these may be spam emails we have failed to filter.
Re: [EP-tech] different fieldnames in different versions...contd
From: Ranju Upadhyay <Ranju.Upadhyay AT nuim.ie>
Date: Wed, 01 Oct 2008 15:50:49 +0100
| Threading: | ↑ Re: [EP-tech] different fieldnames in different versions...contd from franc AT ncsi.iisc.ernet.in • This Message |
This is a multi-part message in MIME format. Hi Francis,Thanks for the suggestion.I added a field a called altloc which was ↵ had multiple key on and had a field called altloc (I think unless a filed has ↵ multiple key on, it does not create a separate table).This created a table ↵ called eprint_altloc_altloc on erasing the existing eprints on 3 , however on ↵ importing the eprints through import command, the table did not get any data in ↵ it :-(.So this approach didn't work for me.instead I wrote a sql script to get ↵ the data out of archive_altloc table in the old version in a file and inserted ↵ it into "eprint_related_url_url" table in ep3.This definately brought ↵ in all the altlocs but the value of "type" remains unassigned as ↵ there is no such column called type in "archive_altloc".Looks like ↵ this is something one has to do manually!Just thought about sharing it to the ↵ list!ThanksRanjuNUIM,Ireland.----- Original Message -----From: Francis ↵ Jayakanth <franc AT ncsi.iisc.ernet.in>Date: Wednesday, October 1, 2008 ↵ 8:42 amSubject: Re: [EP-tech] different fieldnames in different ↵ versions...contdTo: "EPrints.org Technical List" <eprints-tech AT ↵ ecs.soton.ac.uk>> *** 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.>ATTACHMENT: message.html!
[index] [prev] [next] [options] [help]




