Hi Tibor, Thanks for the explanation on the installation. We have successfully installed 0.99. We also tried the demo site, and everything looks fine. Now it is time for us to migrate all the data from 0.71 to 0.99. We decided to take the approach that gets all the XMLs for all the documents from the 0.71 by "wget -O z.xml http://xxx/...of=xm"; and then bibupload all "z.xml" to the 0.99. We have tested one "z.xml" and it works.
The question left is how to upload the file, e.g., the pdf file, for each record. Basically we have to download each full-text pdf file from the 0.71 site and then submit it as new file for the corresponding record in 0.99. We noticed that we have to create a new action "SRV - Submit New File" for each document type. However, it seems not obvious to do this in 0.99. First, the Websubmit how-to seems not up-to-date. (Somehow it is same as 0.71?) Second, the 0.99 demo site seems to also miss a SRV action template so that we have to do it from scratch. We have spend some time on this but not successful. Could you please provide some hint on how we can submit a pdf file for a record that we import from 0.71? What are the steps to create a submit new file page? Is there any way so that we do this in batch? Many thanks! Best, Qiang On Thu, Apr 23, 2009 at 2:14 AM, Tibor Simko <[email protected]> wrote: Hi Qiang: On Thu, 23 Apr 2009, Qiang Wei wrote: > To see what happened, we first used apt-show-versions to check the > mysqldb version, it showed "python2.3-mysqldb/oldstable uptodate > 1.2.1c2-1". We then went to the mysqldb site, got version 1.2.1_p2 and > then manually installed it. However, running configure script still > shows the same error message: 0.9.2 detected. If you want to install MySQLdb from the upstream tarball, then be sure to remove the Debian package first: $ sudo dpkg --purge python2.3-mysqldb and install the upstream tarball only afterwards. > We finally decided to install a workable 0.99 ASAP instead of > debugging 0.71. Okay. Then you should check your table charset to see if it was defined as UTF-8 in the past. If it was not, then you will have to convert your tables to UTF-8, otherwise you would have problems with accented letters. To inspect your current table charset, do something like: $ echo "SHOW CREATE TABLE collection\G;" | /opt/cds-invenio/bin/dbexec If you need to convert tables to UTF-8, then I can advise you how later. P.S. (Another option could be to dump your records from your v0.7.1 instance in the MARCXML format and bibupload them into a clean fresh v0.99.1 install from scratch. This may be convenient if you don't have very many records. But you would have to copy user and baskets and download stats and other tables afterwards into the new site anyway, if you want to preserve that history... depending on your setup.) Best regards -- Tibor Simko ** CERN Document Server ** <http://cds.cern.ch/> __________________________________________________________________ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/
