Help for migrate data from 2.4 to 2.6

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Help for migrate data from 2.4 to 2.6

Leonardo Arias-Alemán

We just made a clean installation of the 2.6, and we want to migrate the contents that we have in the 2.4. We see that there were changes in the structure of some things.

Do you know "how" I have to do this data migration?

 

 

LEONARDO ARIAS-ALEMÁN

Investigador Laboratorio de Servicios de Información - LabSIS
Teléfono: (+57) (+5) 4328600 ext: 364,
Celular: (+57) 300814557

Dirección: Calle 25 # 2 – 55, Playa Salguero, Rodadero, Santa Marta, Magdalena (Colombia)
E-mail: [hidden email]

cid:c3a16bf833684492a6fb476743ee9ccb04ecde29@zimbra

 No me imprimas si no es necesario. Protejamos el medio ambiente

 

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si recibe este mensaje por error, favor de notificarlo al remitente de inmediato y desecharlo de su sistema.

 

 

 


_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Help for migrate data from 2.4 to 2.6

Simo D
Hi, geonode 2.6 ships migrations for 2.4 dbs. After having made a backup of your 2.4 db, you can plug it into geonode 2.6 and launch $geonode migrate --fake-initial, this will add new tables and migrate existing table adding the new fields. Manual porting must be done for keywords as geonode 2.6 is using a brand new table called Hierarchical keywords and the script does not move them from the old to new table.

hope this helps

2017-06-06 15:17 GMT+02:00 Leonardo Arias-Alemán <[hidden email]>:

We just made a clean installation of the 2.6, and we want to migrate the contents that we have in the 2.4. We see that there were changes in the structure of some things.

Do you know "how" I have to do this data migration?

 

 

LEONARDO ARIAS-ALEMÁN

Investigador Laboratorio de Servicios de Información - LabSIS
Teléfono: (+57) (+5) 4328600 ext: 364,
Celular: (+57) 300814557

Dirección: Calle 25 # 2 – 55, Playa Salguero, Rodadero, Santa Marta, Magdalena (Colombia)
E-mail: [hidden email]

cid:c3a16bf833684492a6fb476743ee9ccb04ecde29@zimbra

 No me imprimas si no es necesario. Protejamos el medio ambiente

 

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si recibe este mensaje por error, favor de notificarlo al remitente de inmediato y desecharlo de su sistema.

 

 

 


_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users




--
Simone 

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Help for migrate data from 2.4 to 2.6

isralopez
Hi everybody, talking about the keywords migration, it is only as simple as copy the old table content
to the new one? 

And I don't find the way of create new keywords in 2.6, the only way is through the admin interface, I think
Before you can create it only typing a new one in the metadata form, now I can't find another way than
the admin.

Need your help, thanks.

2017-06-07 1:54 GMT-05:00 Simone Dalmasso <[hidden email]>:
Hi, geonode 2.6 ships migrations for 2.4 dbs. After having made a backup of your 2.4 db, you can plug it into geonode 2.6 and launch $geonode migrate --fake-initial, this will add new tables and migrate existing table adding the new fields. Manual porting must be done for keywords as geonode 2.6 is using a brand new table called Hierarchical keywords and the script does not move them from the old to new table.

hope this helps

2017-06-06 15:17 GMT+02:00 Leonardo Arias-Alemán <[hidden email]>:

We just made a clean installation of the 2.6, and we want to migrate the contents that we have in the 2.4. We see that there were changes in the structure of some things.

Do you know "how" I have to do this data migration?

 

 

LEONARDO ARIAS-ALEMÁN

Investigador Laboratorio de Servicios de Información - LabSIS
Teléfono: (+57) (+5) 4328600 ext: 364,
Celular: (+57) 300814557

Dirección: Calle 25 # 2 – 55, Playa Salguero, Rodadero, Santa Marta, Magdalena (Colombia)
E-mail: [hidden email]

cid:c3a16bf833684492a6fb476743ee9ccb04ecde29@zimbra

 No me imprimas si no es necesario. Protejamos el medio ambiente

 

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si recibe este mensaje por error, favor de notificarlo al remitente de inmediato y desecharlo de su sistema.

 

 

 


_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users




--
Simone 

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users



_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Help for migrate data from 2.4 to 2.6

simone balbo-2
Hi everybody,

I'm facing the same situation with keywords migration. 
@Israel did you solve it?

I was thinking about:
  • accessing the django shell in the old GeoNode 2.4 site and store the "layer.keywords_list()" (a list of strings), together with the layer id, into a text file.
  • moving the file to the new GeoNode 2.6 site
  • accessing the django shell in the new GeoNode 2.6 site and for every single layer:
    • gather the respective keywords from the text file
    • add each keyword with "layer.keywords.add('<keyword>')" 
Is there any quicker/easier way forward?

Best,

Simone


On 24 August 2017 at 03:17, Israel López <[hidden email]> wrote:
Hi everybody, talking about the keywords migration, it is only as simple as copy the old table content
to the new one? 

And I don't find the way of create new keywords in 2.6, the only way is through the admin interface, I think
Before you can create it only typing a new one in the metadata form, now I can't find another way than
the admin.

Need your help, thanks.

2017-06-07 1:54 GMT-05:00 Simone Dalmasso <[hidden email]>:
Hi, geonode 2.6 ships migrations for 2.4 dbs. After having made a backup of your 2.4 db, you can plug it into geonode 2.6 and launch $geonode migrate --fake-initial, this will add new tables and migrate existing table adding the new fields. Manual porting must be done for keywords as geonode 2.6 is using a brand new table called Hierarchical keywords and the script does not move them from the old to new table.

hope this helps

2017-06-06 15:17 GMT+02:00 Leonardo Arias-Alemán <[hidden email]>:

We just made a clean installation of the 2.6, and we want to migrate the contents that we have in the 2.4. We see that there were changes in the structure of some things.

Do you know "how" I have to do this data migration?

 

 

LEONARDO ARIAS-ALEMÁN

Investigador Laboratorio de Servicios de Información - LabSIS
Teléfono: (+57) (+5) 4328600 ext: 364,
Celular: (+57) 300814557

Dirección: Calle 25 # 2 – 55, Playa Salguero, Rodadero, Santa Marta, Magdalena (Colombia)
E-mail: [hidden email]

cid:c3a16bf833684492a6fb476743ee9ccb04ecde29@zimbra

 No me imprimas si no es necesario. Protejamos el medio ambiente

 

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si recibe este mensaje por error, favor de notificarlo al remitente de inmediato y desecharlo de su sistema.

 

 

 


_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users




--
Simone 

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users



_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users




_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Help for migrate data from 2.4 to 2.6

isralopez
Hi Simone, unfortunately I haven't solve this problem, I was working on another thing and I haven't time
for fix it, today I found your mail and I'm gonna work on this these days. 

Hope find a solution soon, because we depend on keywords a lot for our data.

2017-09-21 14:21 GMT-05:00 simone balbo <[hidden email]>:
Hi everybody,

I'm facing the same situation with keywords migration. 
@Israel did you solve it?

I was thinking about:
  • accessing the django shell in the old GeoNode 2.4 site and store the "layer.keywords_list()" (a list of strings), together with the layer id, into a text file.
  • moving the file to the new GeoNode 2.6 site
  • accessing the django shell in the new GeoNode 2.6 site and for every single layer:
    • gather the respective keywords from the text file
    • add each keyword with "layer.keywords.add('<keyword>')" 
Is there any quicker/easier way forward?

Best,

Simone


On 24 August 2017 at 03:17, Israel López <[hidden email]> wrote:
Hi everybody, talking about the keywords migration, it is only as simple as copy the old table content
to the new one? 

And I don't find the way of create new keywords in 2.6, the only way is through the admin interface, I think
Before you can create it only typing a new one in the metadata form, now I can't find another way than
the admin.

Need your help, thanks.

2017-06-07 1:54 GMT-05:00 Simone Dalmasso <[hidden email]>:
Hi, geonode 2.6 ships migrations for 2.4 dbs. After having made a backup of your 2.4 db, you can plug it into geonode 2.6 and launch $geonode migrate --fake-initial, this will add new tables and migrate existing table adding the new fields. Manual porting must be done for keywords as geonode 2.6 is using a brand new table called Hierarchical keywords and the script does not move them from the old to new table.

hope this helps

2017-06-06 15:17 GMT+02:00 Leonardo Arias-Alemán <[hidden email]>:

We just made a clean installation of the 2.6, and we want to migrate the contents that we have in the 2.4. We see that there were changes in the structure of some things.

Do you know "how" I have to do this data migration?

 

 

LEONARDO ARIAS-ALEMÁN

Investigador Laboratorio de Servicios de Información - LabSIS
Teléfono: (+57) (+5) 4328600 ext: 364,
Celular: (+57) 300814557

Dirección: Calle 25 # 2 – 55, Playa Salguero, Rodadero, Santa Marta, Magdalena (Colombia)
E-mail: [hidden email]

cid:c3a16bf833684492a6fb476743ee9ccb04ecde29@zimbra

 No me imprimas si no es necesario. Protejamos el medio ambiente

 

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si recibe este mensaje por error, favor de notificarlo al remitente de inmediato y desecharlo de su sistema.

 

 

 


_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users




--
Simone 

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users



_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users





_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users