Upgrade Dedalo v3 to latest version

pricua

Hi,

We would like to upgrade a Dedalo installation that we have on a fairly old version (version 3) to the most recent version of Dedalo, so that we can keep all the information without having to re-enter it from scratch.

As is logical and normal, since it is such an old version there is no documentation on the subject. We think that we will have to upgrade progressively, first to version 4, then to v5 and finally to v6, but the truth is that we don't know where to start.

At first the folder structure is very different as well as the database, since in v3 mysql is used and from v4 onwards it starts using postgres, with a completely different structure and tables.

We understand that the most complex thing will be to make the jump from v3 to v4 and from there it should be "easier" to get to v6.

Could you guide us through this process?

Thanks!

Alex

Uffff

Yes, the v3 is old world and the last version of classical SQL model in Dédalo and this version si totally obsolete. v4 was the first implementation of a NoSQL model with an ontology and the model is totally different. In those times the change was done manually and it was updated and implemented in the projects that they wont. As community we stop support it long time ago ( +/-15 years ) and we are now focusing on the NoSQL model..

The good news is that v5 can handle the v4 updates and you can use it to update your data from v3 to v5 without install the v4.
The bad news is that the transform needs to be done manually.

And maybe you will need to work in different ways: some data can handle by importing csv files, some could be transformed using a scripts...

The main data as People, Interviews, Audiovisuals, etc. can be imported using the csv import tool.
For example, for People data, you can create a csv with the MySQL informant table and map into the ontology definition, something as:

name ---> rsc85
surname ---> rsc86

etc.

And you can create a csv file with v5 format and you can import it using the import tool in administration.

section_id	rsc85	rsc86
1	{"lg-nolan":"John"}	{"lg-nolan":"Silver"}

But the thesaurus data could be complicated in this way, so, I remember that we create a script to update it in v4.5, and maybe the most easy way is run it using the original tables. So, you will need to create the SQL tables in your PostgreSQL as:

jer_es
jer_ts
jer_on
desctiptors
etc. (you can find some other tables jer_xx)

and run the updates scripts to pass the v4.5 and finally join the result with the imported data as previous People example.

And the most complicated steps could be the indexations. I remember that this part as hard... maybe the most easy way could be to create a locator with the two indexation tables, and import it in the thesaurus as csv file.

I don't remember the v3 columns but I remember that this information was storage in two tables... and you need to combine it to create the indexation locator as:

section_id	hierarchy40
1	[{"type":"dd96","tag_id":"1","section_id":"2","section_tipo":"rsc167","component_tipo":"rsc36","section_top_id":"1","section_top_tipo":"oh1","from_component_tipo":"hierarchy40"}]

And import it into the correct section_tipo as on1, ts1, etc.

I hope it helps you.
And good look.

Best