renderpci / dedalo Goto Github PK

Dédalo: Cultural Heritage & Oral History Management System

License: GNU Affero General Public License v3.0

PHP 36.41% JavaScript 45.93% CSS 0.85% HTML 14.23% Less 1.00% Python 0.05% Batchfile 0.01% Hack 0.02% Handlebars 0.01% Ruby 0.01% Makefile 0.16% Shell 0.94% C 0.37% M4 0.02%

nosql-database heritage digital-humanities graph-database oral-histories thesaurus openapi archeology ontology cultural-analytics

dedalo's Introduction

V6 transition state

ontology	state	use	interface	tools	comments	v5 compatibility until (dmy)
dd	production	100%	100%	100%	All definitions are ready	October 2024
rsc	production	100%	100%	100%	All definitions are ready	October 2024
hierarchy	production	100%	100%	100%	All definitions are ready	October 2024
ww	production	100%	100%	100%	All definitions are ready	October 2024
oh	production	100%	100%	100%	All definitions are ready	October 2024
numisdata	production	100%	100%	100%	All definitions are ready	30/04/2024
isad	production	100%	100%	100%	All definitions are ready	October 2024
ich	production	100%	100%	100%	All definitions are ready	October 2024
tch	beta	80%	90%	90%	Install and test it, but don't use in production	not compatible
tchi	production	100%	100%	100%	All definitions are ready	not compatible
dmm	beta	70%	60%	80%	Install and test it, but don't use in production	October 2024
mdcat	alpha	0%	0%	0%		October 2024

1. What is Dédalo?

Dédalo is a knowledge management system for tangible and intangible Cultural Heritage, Natural Heritage and Oral History and Memory.

Official Dédalo webpage

Dédalo is a Free and Open Source software based on a new paradigm of programming: developing objects with an ontology model. The ontology controls the app flow with the descriptors, related terms, no descriptors, TG, TE, etc. Objects are built with a MVC structure and are linked to the ontology. The database uses a NoSQL model, storing all data in JSONB (binary) format.

Dédalo uses the structured Ontology in order to:

Make the data structured (user data is stored without a fixed structure).
Build the programming objects during execution time.
Interpret the code and the data to translate it to multiple formats (RDF, JSON-LD, SQL, CSV, XML, Dublin Core, HTML, PDF, etc.).

The ontology can be modified, subsequently changing the data and the code. You can (1) develop new functionalities without changing the data and (2) alter the metadata independently of the code and the data.

Dédalo is based on a linked data model and uses a relative, multi-reference, universal locator. Such locator can find entities, sections, components, and tags. In other words, it can locate archives (in others entities), records, fields, and part of the fields (sub-field data).

Dédalo can use any language for its user interface and the managed data. It has a multi-thesaurus engine and can manage multiple resources and resolutions for video, image, pdf, notation scores, etc.

Dédalo has a geo-reference for cultural properties, interviews... with points, areas, paths... as well as an indexation and relational model of multiple data sources within the thesaurus.

Dédalo can handle and cut video in real time to find thematic fragments of interviews or cultural goods. 4K, 1080p, 720p, and 404p resolutions are supported.

2. Dédalo demo

Want to see Dédalo in action?

Dédalo demo

3. Who uses Dédalo?

Here are some projects that use Dédalo to manage their Cultural Heritage and/or Oral Archive:

Freie Universität Berlin
Moneda Ibérica catalog
Museu de Prehistòria de València
Memorial Democràtic
Mujer y Memoria (Woman and Memory - Mothers and daughters of the Spanish transition. An oral history project)
Arxiu de la Memòria Històrica de Paiporta Arxiu de la Memòria Històrica de Paiporta Delegación de Memoria Histórica de la Diputación de Valencia
Nuestra Memoria Archivo de historia oral
Lur Azpian, Desobiratze Goiztiarrak Nafarroan| Bajo tierra, Exhumaciones tempranas en Navarra (Underground Early exhumations in Navarra - Instituto Navarro de Memoria)
Museu de la Paraula (Archivo de la Memoria Oral Valenciana)
Collection of funds from MUVAET Museu Valencià d'Etnologia

4. Dependencies

4.1. Services required for the OS

PHP 8.3+
Apache 2.4.6+
PostgreSQL 16.1+
MySQL 5.6+ (NOT MANDATORY, only for publication).

4.2. Libraries required for Dédalo

flatpickr 4.6.3
geoip2 (!)
json-view
leaflet 1.9+
geoman 2.16.0
lessphp v0.4.0
d3
mocha 9.2.2
chai 4.3.3
nvd3 1.7.1
svgCanvas 7.2.1
pdfjs 1.1.1
pdfkit
tcpdf 6.2.5
ckeditor 5+
wexflow 1.2

4.3. Libraries required for the OS

FFmpeg 5.0+
FFprobe 2.6.1+ (part of FFmpeg)
qtfaststart 1.0 (qt-faststart executable. Usually of FFmpeg, but not always! Be careful!)
ImageMagick 6.9+
Xpdf command line tools 4.00.01+

5. Installation

5.1. Ready-to-use Virtual Machine for V5

Then, you can use our V5 ready-to-use Virtual Machine for development: Dedalo V5

5.2. Video-guide for V5 installation

Then, you can follow the steps in the V5 installation video (similar for V6): Dedalo V5 installation video on CentOS

5.3. Manual installation

Then, install Dédalo manually [following this instruction(https://dedalo.dev/docs/install/#installation)], the process to install is:

Download Dédalo and place it under the httpdocs directory of the web server.
Create a database in PostgreSQL named dedalo_xx (you can change the xx as you please).
Rename [...]/dedalo/config/sample.config.php to [...]/dedalo/config/config.php.
Modify [...]/dedalo/config/config.php as you need. Usually, this involves the DEDALO_ENTITY string and the OS library paths.
Rename [...]/dedalo/config/sample.config_db.php to [...]/dedalo/config/config_db.php.
Modify [...]/dedalo/config/config_db.php with your database configuration.
Rename [...]/dedalo/config/sample.config_core.php to [...]/dedalo/config/config_core.php.
Rename [...]/dedalo/config/sample.config_areas.php to [...]/dedalo/config/config_areas.php.
Open Dédalo in the browser.
Follow the instructions.
Once the installation process is done, log in and head to the Development Area. There, update the Ontology and register all tools.
Create an admin user.
Log out and log in with the admin user.
Create Users and Projects as you need.

!!! warning "Updating a Beta or RC version to final version" If you are using Dédalo v6 beta or Release Candidate, you will need to refresh the cache control. Opening the web browser console and deleting the browser cache and browser indexed_DB to update it with final definitions.

6. Update

Please read the "Updates.md" file for specific notes, procedures, etc, of the versions.

You can follow the instruction to update here. In a nutshell, Dédalo has three main updates procedures:

Update the code files (php, js, css, html, etc.)
- Create a backup of all files.
- Download the new files and change the files in your server.
- You will need see the new config files and put the changes into your own config files (/dedalo/config/config.php and /dedalo/config/config_db.php) is not possible change this files automatically because are the configuration files and it has specific pw and paths of the users. If you don't change the config files, Dédalo will require the new "define" variables and will stop the app.
Update the ontology structure with the sections, components, list, etc.
- Do the first update step
- Log-in with any "developer" user.
- You will see an indication, an "orange" or "red" box, to the left of menu (red box, if you have the debugger active) a "grey" sub-menu with your server configuration, and a new "Development" menu, press it to go to the "admin utils" page.
- Locate the "Update Ontology" panel and press the "Update Dédalo ontology to the latest version" button, if all go well you will see a "green" alert.
- Log-out and log-in with a normal admin user.
Update the data in your installation
- Do the first and second update steps
- Log-in with any "developer" user.
- You will see an indication, an "orange" or "red" box, to the left of menu (red box, if you have the debugger active) a "grey" sub-menu with your server configuration, and a new "Development" menu, press it to go to the "admin utils" page.
- Locate the "Update Data" panel. If your data version is different that the "code files" version, Dédalo will show that you need update, press the «update» link and wait for notifications.
- If all go well you will see a report with the changes.
- Reload the page 'Administration Tools'. Sometimes, if the update differs in several versions, you will need to update the data to each of the intermediate versions (v6.0.9 pass from v6.0.9 to -> v6.0.10, v6.0.10 to -> v6.0.11, etc) when the data and "code files" are in the same version, Dédalo will show that is consistent and stop the upgrade process.
- Log-out and log-in with normal admin user.
- Optional: in the inventory pages (OH, PCI, etc) press the "Update Cache" into the list of the sections for update some changes into the components (this task force to update all components with the new model no 1 to 1), and will apply the changes to the data into the databases.

7. Importing toponymy

Create the toponymy into the Hierarchy menu into Thesaurus:
- Log in into Dédalo
- Go to the "Thesaurus -> Hierarchy" section
- Find the country that you want import
- Edit the country
- Change the "active" field to "Yes"
- Press the "Generate" button
The toponymy is ready for import the data in SQL.
- Log out from Dédalo
- Go to: /dedalo/install/import/hierarchy
- Select the hierarchies to be imported with the postgreSQL copy command, similar to:
  - psql dedalo4_XXX -U YYY -p 5432 -h localhost -c "\copy matrix_hierarchy(section_id, section_tipo, datos) from es1.copy "
  - XXX: the name of your installation
  - YYY: the name of your user
- You can list all exported tables and change the "es1.copy" to the hierarchies that you want import
- When you are import the toponymy data, you will need change the counters of the tables that you were imported.
- Login to Dédalo with developer user
- Go to the "administration tool" and see the:
  - DEDALO COUNTERS STATE
- You will see the diferences and Dédalo show the SQL command to apply into the postgreSQL, similar to this:
  - UPDATE "matrix_counter" SET dato = 75845 WHERE tipo = 'es1';
- This command will change the counters to the new imported values in SQL
- Change the profiles to access users to the new hierarchy.
Done! you new hierarchy was imported and ready to use.

8. Server system

The backend of Dédalo is tested in:

Ubuntu Server 22.04 LTS or 20.04 LTS
Debian 11.0+
MacOs X 12.0+
CentOS, Fedora and RedHat situation. We are no longer testing Dédalo in RedHat/CenOS/Fedora model since the CentOS project focus was shifted. The main OS to test Dédalo will be Ubuntu. RedHat/CentOS/Fedora will become part of the "all other Linux that we do not test" category.

CentOS blog

Any other Linux will probably be compatible, but we offer NO GUARANTEES.

Windows: Dédalo might run, but we HAVE NOT TESTED IT.

9. Compatible browsers

Dédalo version V6+ is only tested in chromium and webkit browsers (Chrome, Safari, Edge 77+, ...).

Browser	Version	Compatible with Dédalo
Chrome	115+	YES - recommended
Chrome	100 to 114	Deprecated (Please update as soon as possible)
Chrome	0 to 100	NO
Safari	16.4+	YES
Safari	16.3	Deprecated (Please update as soon as possible)
Safari	0 to 15	NO
Firefox	115+	YES
Firefox	100 to 114	Deprecated (Please update as soon as possible)
Firefox	0-99	NO
EDGE	115+	YES
EDGE	100 to 114	Deprecated (Please update as soon as possible)
EDGE	0 to 100	NO
IExplorer	All	NO

dedalo's People

Contributors

Stargazers

Watchers

Forkers

devpacdd lucas-ubm alex-render louveal pricua ritmele

dedalo's Issues

Make additional Geonames countries available for Greek project

Update to V.5.8.2

We are having problems updating to version 5.8.2 (from version 5.7.72). Specifically in the step "update data version: 5.6.1 -> 5.6.2", where checks and updates the values of table 'matrix_activity'.

After more than 12 hours the process ends without reporting any errors and the update is not performed.

Is there a log where the process is being recorded or where the result can be checked?

In the release notes you state:
This update review all the activity data and could be a long process, it can take some hours or days (if you have more than 30.000.000 records in activity).

In our case, the matrix_activity table has more than 45,000,000 records.

Have you tried to update on an installation with so much data? Do I have to do any special configuration in apache or postgres for the process to work?

Thanks in advance!

Problema en el volcado de la BBDD durante la instalación de Dédalo

Hola Alex,

Estoy intentando instalar Dédalo en local sobre xampp y ya tengo Postgre SQL instalado, he creado la base de datos dedalo4_elprattvvideoteca, pero al hacer el restore de la base de datos de Dédalo con PgAdmin4, me da este error:

C:\Program Files\PostgreSQL\11\bin\pg_restore.exe --host "localhost" --port "5432" --username "postgres" --no-password --dbname "dedalo4_elprattvvideoteca" --verbose "C:\xampp\htdocs\dedalo\install\db\DEDALO~1.BAC"

Resultado:

pg_restore: conectando a la base de datos para reestablecimiento
pg_restore: creando EXTENSION �plpgsql�
pg_restore: creando COMMENT �EXTENSION plpgsql�
pg_restore: creando EXTENSION �pg_trgm�
pg_restore: creando COMMENT �EXTENSION pg_trgm�
pg_restore: creando EXTENSION �unaccent�
pg_restore: creando COMMENT �EXTENSION unaccent�
pg_restore: creando TYPE �public.sino�
pg_restore: [archiver (bd)] Error durante PROCESAMIENTO DE TABLA DE CONTENIDOS:
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 687; 1247 2179229 TYPE sino paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TYPE public.sino OWNER TO paco;

pg_restore: creando FUNCTION �public.check_array_component(boolean, jsonb)�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 301; 1255 2179233 FUNCTION check_array_component(boolean, jsonb) paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER FUNCTION public.check_array_component(condition boolean, component_path jsonb) OWNER TO paco;

pg_restore: creando FUNCTION �public.count_estimate(text)�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 302; 1255 2179234 FUNCTION count_estimate(text) paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER FUNCTION public.count_estimate(query text) OWNER TO paco;

pg_restore: creando FUNCTION �public.f_unaccent(text)�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 303; 1255 2179235 FUNCTION f_unaccent(text) paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER FUNCTION public.f_unaccent(text) OWNER TO paco;

pg_restore: creando TABLE �public.jer_dd�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 198; 1259 2179236 TABLE jer_dd paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.jer_dd OWNER TO paco;

pg_restore: creando SEQUENCE �public.jer_dd_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 199; 1259 2179242 SEQUENCE jer_dd_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.jer_dd_id_seq OWNER TO paco;

pg_restore: creando SEQUENCE OWNED BY �public.jer_dd_id_seq�
pg_restore: creando TABLE �public.main_dd�
pg_restore: creando SEQUENCE �public.main_dd_id_seq�
pg_restore: creando SEQUENCE OWNED BY �public.main_dd_id_seq�
pg_restore: creando SEQUENCE �public.matrix_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 200; 1259 2179249 SEQUENCE matrix_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 201; 1259 2179251 TABLE matrix paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_activities_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 202; 1259 2179258 SEQUENCE matrix_activities_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_activities_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_activities�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 203; 1259 2179260 TABLE matrix_activities paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_activities OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_activity_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 204; 1259 2179267 SEQUENCE matrix_activity_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_activity_id_seq OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_activity_section_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 205; 1259 2179269 SEQUENCE matrix_activity_section_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_activity_section_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_activity�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 206; 1259 2179271 TABLE matrix_activity paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_activity OWNER TO paco;

pg_restore: creando TABLE �public.matrix_counter�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 207; 1259 2179281 TABLE matrix_counter paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_counter OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_counter_dd_id_seq�
pg_restore: creando TABLE �public.matrix_counter_dd�
pg_restore: creando SEQUENCE �public.matrix_counter_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 208; 1259 2179296 SEQUENCE matrix_counter_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_counter_id_seq OWNER TO paco;

pg_restore: creando SEQUENCE OWNED BY �public.matrix_counter_id_seq�
pg_restore: creando SEQUENCE �public.matrix_dataframe_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 209; 1259 2179298 SEQUENCE matrix_dataframe_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_dataframe_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_dataframe�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 210; 1259 2179300 TABLE matrix_dataframe paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_dataframe OWNER TO paco;

pg_restore: creando TABLE �public.matrix_dd�
pg_restore: creando SEQUENCE �public.matrix_dd_id_seq�
pg_restore: creando SEQUENCE OWNED BY �public.matrix_dd_id_seq�
pg_restore: creando SEQUENCE �public.matrix_descriptors_dd_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 211; 1259 2179315 SEQUENCE matrix_descriptors_dd_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_descriptors_dd_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_descriptors_dd�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 212; 1259 2179317 TABLE matrix_descriptors_dd paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_descriptors_dd OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_hierarchy_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 213; 1259 2179324 SEQUENCE matrix_hierarchy_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_hierarchy_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_hierarchy�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 214; 1259 2179326 TABLE matrix_hierarchy paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_hierarchy OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_hierarchy_main_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 215; 1259 2179333 SEQUENCE matrix_hierarchy_main_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_hierarchy_main_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_hierarchy_main�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 216; 1259 2179335 TABLE matrix_hierarchy_main paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_hierarchy_main OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_indexations_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 217; 1259 2179342 SEQUENCE matrix_indexations_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_indexations_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_indexations�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 218; 1259 2179344 TABLE matrix_indexations paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_indexations OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_langs_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 219; 1259 2179351 SEQUENCE matrix_langs_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_langs_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_langs�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 220; 1259 2179353 TABLE matrix_langs paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_langs OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_layout_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 221; 1259 2179360 SEQUENCE matrix_layout_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_layout_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_layout�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 222; 1259 2179362 TABLE matrix_layout paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_layout OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_layout_dd_id_seq�
pg_restore: creando TABLE �public.matrix_layout_dd�
pg_restore: creando SEQUENCE �public.matrix_list_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 223; 1259 2179378 SEQUENCE matrix_list_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_list_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_list�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 224; 1259 2179380 TABLE matrix_list paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_list OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_notes_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 225; 1259 2179387 SEQUENCE matrix_notes_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_notes_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_notes�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 226; 1259 2179389 TABLE matrix_notes paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_notes OWNER TO paco;

pg_restore: creando TABLE �public.matrix_notifications�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 227; 1259 2179396 TABLE matrix_notifications paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_notifications OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_notifications_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 228; 1259 2179402 SEQUENCE matrix_notifications_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_notifications_id_seq OWNER TO paco;

pg_restore: creando SEQUENCE OWNED BY �public.matrix_notifications_id_seq�
pg_restore: creando TABLE �public.matrix_profiles�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 229; 1259 2179404 TABLE matrix_profiles paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_profiles OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_profiles_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 230; 1259 2179410 SEQUENCE matrix_profiles_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_profiles_id_seq OWNER TO paco;

pg_restore: creando SEQUENCE OWNED BY �public.matrix_profiles_id_seq�
pg_restore: creando TABLE �public.matrix_projects�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 231; 1259 2179412 TABLE matrix_projects paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_projects OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_projects_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 232; 1259 2179418 SEQUENCE matrix_projects_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_projects_id_seq OWNER TO paco;

pg_restore: creando SEQUENCE OWNED BY �public.matrix_projects_id_seq�
pg_restore: creando TABLE �public.matrix_stat�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 233; 1259 2179420 TABLE matrix_stat paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_stat OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_stat_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 234; 1259 2179426 SEQUENCE matrix_stat_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_stat_id_seq OWNER TO paco;

pg_restore: creando SEQUENCE OWNED BY �public.matrix_stat_id_seq�
pg_restore: creando SEQUENCE �public.matrix_structurations_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 235; 1259 2179428 SEQUENCE matrix_structurations_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_structurations_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_structurations�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 236; 1259 2179430 TABLE matrix_structurations paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_structurations OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_test_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 237; 1259 2179437 SEQUENCE matrix_test_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_test_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_test�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 238; 1259 2179439 TABLE matrix_test paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_test OWNER TO paco;

pg_restore: creando TABLE �public.matrix_time_machine�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 239; 1259 2179446 TABLE matrix_time_machine paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_time_machine OWNER TO paco;

pg_restore: creando SEQUENCE �public.matrix_time_machine_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 240; 1259 2179452 SEQUENCE matrix_time_machine_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_time_machine_id_seq OWNER TO paco;

pg_restore: creando SEQUENCE OWNED BY �public.matrix_time_machine_id_seq�
pg_restore: creando TABLE �public.matrix_updates�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 241; 1259 2179454 TABLE matrix_updates paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_updates OWNER TO paco;

pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 242; 1259 2179460 SEQUENCE matrix_updates_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_updates_id_seq OWNER TO paco;

pg_restore: creando SEQUENCE OWNED BY �public.matrix_updates_id_seq�
pg_restore: creando SEQUENCE �public.matrix_users_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 243; 1259 2179462 SEQUENCE matrix_users_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_users_id_seq OWNER TO paco;

pg_restore: creando TABLE �public.matrix_users�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 244; 1259 2179464 TABLE matrix_users paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.matrix_users OWNER TO paco;

pg_restore: creando TABLE �public.relations�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 245; 1259 2179471 TABLE relations paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.relations OWNER TO paco;

pg_restore: creando SEQUENCE �public.relations_id_seq�
pg_restore: [archiver (bd)] Error en entrada de la tabla de contenidos 246; 1259 2179477 SEQUENCE relations_id_seq paco
pg_restore: [archiver (bd)] could not execute query: ERROR: no existe el rol «paco»
La orden era: ALTER TABLE public.relations_id_seq OWNER TO paco;

pg_restore: creando SEQUENCE OWNED BY �public.relations_id_seq�
pg_restore: creando DEFAULT �public.jer_dd id�
pg_restore: creando DEFAULT �public.main_dd id�
pg_restore: creando DEFAULT �public.matrix_counter id�
pg_restore: creando DEFAULT �public.matrix_dd id�
pg_restore: creando DEFAULT �public.matrix_notifications id�
pg_restore: creando DEFAULT �public.matrix_profiles id�
pg_restore: creando DEFAULT �public.matrix_projects id�
pg_restore: creando DEFAULT �public.matrix_stat id�
pg_restore: creando DEFAULT �public.matrix_time_machine id�
pg_restore: creando DEFAULT �public.matrix_updates id�
pg_restore: creando DEFAULT �public.relations id�
pg_restore: procesando datos de la tabla �public.jer_dd�
pg_restore: procesando datos de la tabla �public.main_dd�
pg_restore: procesando datos de la tabla �public.matrix�
pg_restore: procesando datos de la tabla �public.matrix_activities�
pg_restore: procesando datos de la tabla �public.matrix_activity�
pg_restore: procesando datos de la tabla �public.matrix_counter�
pg_restore: procesando datos de la tabla �public.matrix_counter_dd�
pg_restore: procesando datos de la tabla �public.matrix_dataframe�
pg_restore: procesando datos de la tabla �public.matrix_dd�
pg_restore: procesando datos de la tabla �public.matrix_descriptors_dd�
pg_restore: procesando datos de la tabla �public.matrix_hierarchy�
pg_restore: procesando datos de la tabla �public.matrix_hierarchy_main�
pg_restore: procesando datos de la tabla �public.matrix_indexations�
pg_restore: procesando datos de la tabla �public.matrix_langs�
pg_restore: procesando datos de la tabla �public.matrix_layout�
pg_restore: procesando datos de la tabla �public.matrix_layout_dd�
pg_restore: procesando datos de la tabla �public.matrix_list�
pg_restore: procesando datos de la tabla �public.matrix_notes�
pg_restore: procesando datos de la tabla �public.matrix_notifications�
pg_restore: procesando datos de la tabla �public.matrix_profiles�
pg_restore: procesando datos de la tabla �public.matrix_projects�
pg_restore: procesando datos de la tabla �public.matrix_stat�
pg_restore: procesando datos de la tabla �public.matrix_structurations�
pg_restore: procesando datos de la tabla �public.matrix_test�
pg_restore: procesando datos de la tabla �public.matrix_time_machine�
pg_restore: procesando datos de la tabla �public.matrix_updates�
pg_restore: procesando datos de la tabla �public.matrix_users�
pg_restore: procesando datos de la tabla �public.relations�
pg_restore: ejecutando SEQUENCE SET jer_dd_id_seq
pg_restore: ejecutando SEQUENCE SET main_dd_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_activities_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_activity_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_activity_section_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_counter_dd_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_counter_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_dataframe_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_dd_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_descriptors_dd_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_hierarchy_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_hierarchy_main_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_indexations_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_langs_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_layout_dd_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_layout_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_list_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_notes_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_notifications_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_profiles_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_projects_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_stat_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_structurations_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_test_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_time_machine_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_updates_id_seq
pg_restore: ejecutando SEQUENCE SET matrix_users_id_seq
pg_restore: ejecutando SEQUENCE SET relations_id_seq
pg_restore: creando CONSTRAINT �public.jer_dd jer_dd_id�
pg_restore: creando CONSTRAINT �public.matrix_activities matrix_activities_pkey�
pg_restore: creando CONSTRAINT �public.matrix_activities matrix_activities_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_activity matrix_activity_id_primary�
pg_restore: creando CONSTRAINT �public.matrix_counter_dd matrix_counter_dd_id�
pg_restore: creando CONSTRAINT �public.matrix_counter_dd matrix_counter_dd_tipo_unique�
pg_restore: creando CONSTRAINT �public.matrix_counter matrix_counter_id�
pg_restore: creando CONSTRAINT �public.matrix_counter matrix_counter_tipo_unique�
pg_restore: creando CONSTRAINT �public.matrix_dataframe matrix_dataframe_pkey�
pg_restore: creando CONSTRAINT �public.matrix_dataframe matrix_dataframe_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_dd matrix_dd_id�
pg_restore: creando CONSTRAINT �public.matrix_dd matrix_dd_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_descriptors_dd matrix_descriptors_dd_id�
pg_restore: creando CONSTRAINT �public.matrix_hierarchy_main matrix_hierarchy_main_pkey�
pg_restore: creando CONSTRAINT �public.matrix_hierarchy_main matrix_hierarchy_main_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_hierarchy matrix_hierarchy_pkey�
pg_restore: creando CONSTRAINT �public.matrix_hierarchy matrix_hierarchy_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix matrix_id�
pg_restore: creando CONSTRAINT �public.matrix_indexations matrix_indexations_pkey�
pg_restore: creando CONSTRAINT �public.matrix_indexations matrix_indexations_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_langs matrix_langs_pkey�
pg_restore: creando CONSTRAINT �public.matrix_langs matrix_langs_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_layout_dd matrix_layout_dd_pkey�
pg_restore: creando CONSTRAINT �public.matrix_layout_dd matrix_layout_dd_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_layout matrix_layout_pkey�
pg_restore: creando CONSTRAINT �public.matrix_layout matrix_layout_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_list matrix_list_pkey�
pg_restore: creando CONSTRAINT �public.matrix_list matrix_list_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_notes matrix_notes_pkey�
pg_restore: creando CONSTRAINT �public.matrix_notes matrix_notes_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_notifications matrix_notifications_id�
pg_restore: creando CONSTRAINT �public.matrix_profiles matrix_profiles_pkey�
pg_restore: creando CONSTRAINT �public.matrix_profiles matrix_profiles_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_projects matrix_projects_id�
pg_restore: creando CONSTRAINT �public.matrix_projects matrix_projects_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix matrix_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_stat matrix_stat_pkey�
pg_restore: creando CONSTRAINT �public.matrix_structurations matrix_structurations_pkey�
pg_restore: creando CONSTRAINT �public.matrix_structurations matrix_structurations_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_test matrix_test_pkey�
pg_restore: creando CONSTRAINT �public.matrix_test matrix_test_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_time_machine matrix_time_machine_id�
pg_restore: creando CONSTRAINT �public.matrix_updates matrix_updates_id�
pg_restore: creando CONSTRAINT �public.matrix_users matrix_users_pkey�
pg_restore: creando CONSTRAINT �public.matrix_users matrix_users_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.relations relations_all_constraint�
pg_restore: creando CONSTRAINT �public.relations relations_id�
pg_restore: creando CONSTRAINT �public.jer_dd terminoID_unique�
pg_restore: creando CONSTRAINT �public.main_dd tld�
pg_restore: creando INDEX �public.jer_dd_esdescriptor�
pg_restore: creando INDEX �public.jer_dd_esmodelo�
pg_restore: creando INDEX �public.jer_dd_modelo�
pg_restore: creando INDEX �public.jer_dd_norden�
pg_restore: creando INDEX �public.jer_dd_parent�
pg_restore: creando INDEX �public.jer_dd_parent_esdescriptor_norden�
pg_restore: creando INDEX �public.jer_dd_relaciones�
pg_restore: creando INDEX �public.jer_dd_terminoid�
pg_restore: creando INDEX �public.jer_dd_traducible�
pg_restore: creando INDEX �public.jer_dd_usableindex�
pg_restore: creando INDEX �public.jer_dd_visible�
pg_restore: creando INDEX �public.matrix_activities_datos_gin�
pg_restore: creando INDEX �public.matrix_activities_id_idx�
pg_restore: creando INDEX �public.matrix_activities_relations_idx�
pg_restore: creando INDEX �public.matrix_activities_section_id�
pg_restore: creando INDEX �public.matrix_activities_section_tipo�
pg_restore: creando INDEX �public.matrix_activities_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_activity_date_btree�
pg_restore: creando INDEX �public.matrix_activity_datos_gin�
pg_restore: creando INDEX �public.matrix_activity_id_btree�
pg_restore: creando INDEX �public.matrix_activity_order_section_id_desc�
pg_restore: creando INDEX �public.matrix_activity_relations_idx�
pg_restore: creando INDEX �public.matrix_activity_section_id�
pg_restore: creando INDEX �public.matrix_activity_section_tipo�
pg_restore: creando INDEX �public.matrix_activity_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_counter_dd_parent�
pg_restore: creando INDEX �public.matrix_counter_parent�
pg_restore: creando INDEX �public.matrix_counter_tipo�
pg_restore: creando INDEX �public.matrix_dataframe_datos_idx�
pg_restore: creando INDEX �public.matrix_dataframe_id_desc_idx�
pg_restore: creando INDEX �public.matrix_dataframe_id_idx�
pg_restore: creando INDEX �public.matrix_dataframe_relations_idx�
pg_restore: creando INDEX �public.matrix_dataframe_section_id_idx�
pg_restore: creando INDEX �public.matrix_dataframe_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_datos_gin�
pg_restore: creando INDEX �public.matrix_dd_gin�
pg_restore: creando INDEX �public.matrix_dd_relations_idx�
pg_restore: creando CONSTRAINT �public.matrix_activities matrix_activities_pkey�
pg_restore: creando CONSTRAINT �public.matrix_activities matrix_activities_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_activity matrix_activity_id_primary�
pg_restore: creando CONSTRAINT �public.matrix_counter_dd matrix_counter_dd_id�
pg_restore: creando CONSTRAINT �public.matrix_counter_dd matrix_counter_dd_tipo_unique�
pg_restore: creando CONSTRAINT �public.matrix_counter matrix_counter_id�
pg_restore: creando CONSTRAINT �public.matrix_counter matrix_counter_tipo_unique�
pg_restore: creando CONSTRAINT �public.matrix_dataframe matrix_dataframe_pkey�
pg_restore: creando CONSTRAINT �public.matrix_dataframe matrix_dataframe_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_dd matrix_dd_id�
pg_restore: creando CONSTRAINT �public.matrix_dd matrix_dd_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_descriptors_dd matrix_descriptors_dd_id�
pg_restore: creando CONSTRAINT �public.matrix_hierarchy_main matrix_hierarchy_main_pkey�
pg_restore: creando CONSTRAINT �public.matrix_hierarchy_main matrix_hierarchy_main_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_hierarchy matrix_hierarchy_pkey�
pg_restore: creando CONSTRAINT �public.matrix_hierarchy matrix_hierarchy_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix matrix_id�
pg_restore: creando CONSTRAINT �public.matrix_indexations matrix_indexations_pkey�
pg_restore: creando CONSTRAINT �public.matrix_indexations matrix_indexations_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_langs matrix_langs_pkey�
pg_restore: creando CONSTRAINT �public.matrix_langs matrix_langs_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_layout_dd matrix_layout_dd_pkey�
pg_restore: creando CONSTRAINT �public.matrix_layout_dd matrix_layout_dd_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_layout matrix_layout_pkey�
pg_restore: creando CONSTRAINT �public.matrix_layout matrix_layout_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_list matrix_list_pkey�
pg_restore: creando CONSTRAINT �public.matrix_list matrix_list_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_notes matrix_notes_pkey�
pg_restore: creando CONSTRAINT �public.matrix_notes matrix_notes_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_notifications matrix_notifications_id�
pg_restore: creando CONSTRAINT �public.matrix_profiles matrix_profiles_pkey�
pg_restore: creando CONSTRAINT �public.matrix_profiles matrix_profiles_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_projects matrix_projects_id�
pg_restore: creando CONSTRAINT �public.matrix_projects matrix_projects_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix matrix_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.matrix_stat matrix_stat_pkey�
pg_restore: creando CONSTRAINT �public.matrix_structurations matrix_structurations_pkey�
pg_restore: creando CONSTRAINT �public.matrix_structurations matrix_structurations_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_test matrix_test_pkey�
pg_restore: creando CONSTRAINT �public.matrix_test matrix_test_section_id_section_tipo_key�
pg_restore: creando CONSTRAINT �public.matrix_time_machine matrix_time_machine_id�
pg_restore: creando CONSTRAINT �public.matrix_updates matrix_updates_id�
pg_restore: creando CONSTRAINT �public.matrix_users matrix_users_pkey�
pg_restore: creando CONSTRAINT �public.matrix_users matrix_users_section_id_section_tipo�
pg_restore: creando CONSTRAINT �public.relations relations_all_constraint�
pg_restore: creando CONSTRAINT �public.relations relations_id�
pg_restore: creando CONSTRAINT �public.jer_dd terminoID_unique�
pg_restore: creando CONSTRAINT �public.main_dd tld�
pg_restore: creando INDEX �public.jer_dd_esdescriptor�
pg_restore: creando INDEX �public.jer_dd_esmodelo�
pg_restore: creando INDEX �public.jer_dd_modelo�
pg_restore: creando INDEX �public.jer_dd_norden�
pg_restore: creando INDEX �public.jer_dd_parent�
pg_restore: creando INDEX �public.jer_dd_parent_esdescriptor_norden�
pg_restore: creando INDEX �public.jer_dd_relaciones�
pg_restore: creando INDEX �public.jer_dd_terminoid�
pg_restore: creando INDEX �public.jer_dd_traducible�
pg_restore: creando INDEX �public.jer_dd_usableindex�
pg_restore: creando INDEX �public.jer_dd_visible�
pg_restore: creando INDEX �public.matrix_activities_datos_gin�
pg_restore: creando INDEX �public.matrix_activities_id_idx�
pg_restore: creando INDEX �public.matrix_activities_relations_idx�
pg_restore: creando INDEX �public.matrix_activities_section_id�
pg_restore: creando INDEX �public.matrix_activities_section_tipo�
pg_restore: creando INDEX �public.matrix_activities_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_activity_date_btree�
pg_restore: creando INDEX �public.matrix_activity_datos_gin�
pg_restore: creando INDEX �public.matrix_activity_id_btree�
pg_restore: creando INDEX �public.matrix_activity_order_section_id_desc�
pg_restore: creando INDEX �public.matrix_activity_relations_idx�
pg_restore: creando INDEX �public.matrix_activity_section_id�
pg_restore: creando INDEX �public.matrix_activity_section_tipo�
pg_restore: creando INDEX �public.matrix_activity_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_counter_dd_parent�
pg_restore: creando INDEX �public.matrix_counter_parent�
pg_restore: creando INDEX �public.matrix_counter_tipo�
pg_restore: creando INDEX �public.matrix_dataframe_datos_idx�
pg_restore: creando INDEX �public.matrix_dataframe_id_desc_idx�
pg_restore: creando INDEX �public.matrix_dataframe_id_idx�
pg_restore: creando INDEX �public.matrix_dataframe_relations_idx�
pg_restore: creando INDEX �public.matrix_dataframe_section_id_idx�
pg_restore: creando INDEX �public.matrix_dataframe_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_datos_gin�
pg_restore: creando INDEX �public.matrix_dd_gin�
pg_restore: creando INDEX �public.matrix_dd_relations_idx�
pg_restore: creando INDEX �public.matrix_dd_section_tipo�
pg_restore: creando INDEX �public.matrix_dd_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_descriptors_dd_lang�
pg_restore: creando INDEX �public.matrix_descriptors_dd_parent�
pg_restore: creando INDEX �public.matrix_descriptors_dd_parent_tipo_lang�
pg_restore: creando INDEX �public.matrix_descriptors_dd_tipo�
pg_restore: creando INDEX �public.matrix_hierarchy63_geonames_id_gin_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_datos_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_id_desc_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_datos_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_id_desc_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_relations_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_section_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_relations_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_section_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_term_hierarchy25_idx�
pg_restore: creando INDEX �public.matrix_id_index�
pg_restore: creando INDEX �public.matrix_indexations_datos_idx�
pg_restore: creando INDEX �public.matrix_indexations_id_desc_idx�
pg_restore: creando INDEX �public.matrix_indexations_id_idx�
pg_restore: creando INDEX �public.matrix_indexations_relations_idx�
pg_restore: creando INDEX �public.matrix_indexations_section_id_idx�
pg_restore: creando INDEX �public.matrix_indexations_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_indexations_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_langs_datos_idx�
pg_restore: creando INDEX �public.matrix_langs_hierarchy41_code_gin_idx�
pg_restore: creando INDEX �public.matrix_langs_id_desc_idx�
pg_restore: creando INDEX �public.matrix_langs_id_idx�
pg_restore: creando INDEX �public.matrix_langs_section_id_idx�
pg_restore: creando INDEX �public.matrix_langs_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_langs_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_layout_dd_relations_idx�
pg_restore: creando INDEX �public.matrix_layout_main_relations_idx�
pg_restore: creando INDEX �public.matrix_layout_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_list_datos_gin�
pg_restore: creando INDEX �public.matrix_list_relations_idx�
pg_restore: creando INDEX �public.matrix_list_section_id�
pg_restore: creando INDEX �public.matrix_list_section_tipo�
pg_restore: creando INDEX �public.matrix_list_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_notes_datos_idx�
pg_restore: creando INDEX �public.matrix_notes_id_desc_idx�
pg_restore: creando INDEX �public.matrix_notes_id_idx�
pg_restore: creando INDEX �public.matrix_notes_relations_idx�
pg_restore: creando INDEX �public.matrix_notes_section_id_idx�
pg_restore: creando INDEX �public.matrix_notes_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_notes_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_order_id_asc�
pg_restore: creando INDEX �public.matrix_order_id_desc�
pg_restore: creando INDEX �public.matrix_profiles_datos_gin�
pg_restore: creando INDEX �public.matrix_profiles_relations_idx�
pg_restore: creando INDEX �public.matrix_profiles_section_id�
pg_restore: creando INDEX �public.matrix_profiles_section_tipo�
pg_restore: creando INDEX �public.matrix_profiles_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_projects_datos_gin�
pg_restore: creando INDEX �public.matrix_projects_relations_idx�
pg_restore: creando INDEX �public.matrix_projects_section_id�
pg_restore: creando INDEX �public.matrix_projects_section_tipo�
pg_restore: creando INDEX �public.matrix_projects_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_relations_idx�
pg_restore: creando INDEX �public.matrix_rsc24�
pg_restore: creando INDEX �public.matrix_rsc25�
pg_restore: creando INDEX �public.matrix_rsc90�
pg_restore: creando INDEX �public.matrix_section_id�
pg_restore: creando INDEX �public.matrix_section_tipo�
pg_restore: creando INDEX �public.matrix_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_stat_datos_idx�
pg_restore: creando INDEX �public.matrix_stat_expr_idx2�
pg_restore: creando INDEX �public.matrix_stat_expr_idx3�
pg_restore: creando INDEX �public.matrix_stat_expr_idx4�
pg_restore: creando INDEX �public.matrix_stat_id_expr_expr1_idx�
pg_restore: creando INDEX �public.matrix_stat_id_expr_expr1_idx1�
pg_restore: creando INDEX �public.matrix_stat_id_idx�
pg_restore: creando INDEX �public.matrix_structurations_datos_idx�
pg_restore: creando INDEX �public.matrix_structurations_id_desc_idx�
pg_restore: creando INDEX �public.matrix_structurations_id_idx�
pg_restore: creando INDEX �public.matrix_structurations_relations_idx�
pg_restore: creando INDEX �public.matrix_structurations_section_id_idx�
pg_restore: creando INDEX �public.matrix_structurations_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_structurations_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_test_datos_idx�
pg_restore: creando INDEX �public.matrix_test_expr_idx�
pg_restore: creando INDEX �public.matrix_test_expr_idx1�
pg_restore: creando INDEX �public.matrix_test_expr_idx2�
pg_restore: creando INDEX �public.matrix_test_expr_idx3�
pg_restore: creando INDEX �public.matrix_test_expr_idx4�
pg_restore: creando INDEX �public.matrix_test_id_idx�
pg_restore: creando INDEX �public.matrix_test_id_idx1�
pg_restore: creando INDEX �public.matrix_test_section_id_idx�
pg_restore: creando INDEX �public.matrix_dd_section_tipo�
pg_restore: creando INDEX �public.matrix_dd_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_descriptors_dd_lang�
pg_restore: creando INDEX �public.matrix_descriptors_dd_parent�
pg_restore: creando INDEX �public.matrix_descriptors_dd_parent_tipo_lang�
pg_restore: creando INDEX �public.matrix_descriptors_dd_tipo�
pg_restore: creando INDEX �public.matrix_hierarchy63_geonames_id_gin_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_datos_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_id_desc_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_datos_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_id_desc_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_relations_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_section_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_main_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_relations_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_section_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_hierarchy_term_hierarchy25_idx�
pg_restore: creando INDEX �public.matrix_id_index�
pg_restore: creando INDEX �public.matrix_indexations_datos_idx�
pg_restore: creando INDEX �public.matrix_indexations_id_desc_idx�
pg_restore: creando INDEX �public.matrix_indexations_id_idx�
pg_restore: creando INDEX �public.matrix_indexations_relations_idx�
pg_restore: creando INDEX �public.matrix_indexations_section_id_idx�
pg_restore: creando INDEX �public.matrix_indexations_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_indexations_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_langs_datos_idx�
pg_restore: creando INDEX �public.matrix_langs_hierarchy41_code_gin_idx�
pg_restore: creando INDEX �public.matrix_langs_id_desc_idx�
pg_restore: creando INDEX �public.matrix_langs_id_idx�
pg_restore: creando INDEX �public.matrix_langs_section_id_idx�
pg_restore: creando INDEX �public.matrix_langs_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_langs_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_layout_dd_relations_idx�
pg_restore: creando INDEX �public.matrix_layout_main_relations_idx�
pg_restore: creando INDEX �public.matrix_layout_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_list_datos_gin�
pg_restore: creando INDEX �public.matrix_list_relations_idx�
pg_restore: creando INDEX �public.matrix_list_section_id�
pg_restore: creando INDEX �public.matrix_list_section_tipo�
pg_restore: creando INDEX �public.matrix_list_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_notes_datos_idx�
pg_restore: creando INDEX �public.matrix_notes_id_desc_idx�
pg_restore: creando INDEX �public.matrix_notes_id_idx�
pg_restore: creando INDEX �public.matrix_notes_relations_idx�
pg_restore: creando INDEX �public.matrix_notes_section_id_idx�
pg_restore: creando INDEX �public.matrix_notes_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_notes_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_order_id_asc�
pg_restore: creando INDEX �public.matrix_order_id_desc�
pg_restore: creando INDEX �public.matrix_profiles_datos_gin�
pg_restore: creando INDEX �public.matrix_profiles_relations_idx�
pg_restore: creando INDEX �public.matrix_profiles_section_id�
pg_restore: creando INDEX �public.matrix_profiles_section_tipo�
pg_restore: creando INDEX �public.matrix_profiles_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_projects_datos_gin�
pg_restore: creando INDEX �public.matrix_projects_relations_idx�
pg_restore: creando INDEX �public.matrix_projects_section_id�
pg_restore: creando INDEX �public.matrix_projects_section_tipo�
pg_restore: creando INDEX �public.matrix_projects_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_relations_idx�
pg_restore: creando INDEX �public.matrix_rsc24�
pg_restore: creando INDEX �public.matrix_rsc25�
pg_restore: creando INDEX �public.matrix_rsc90�
pg_restore: creando INDEX �public.matrix_section_id�
pg_restore: creando INDEX �public.matrix_section_tipo�
pg_restore: creando INDEX �public.matrix_section_tipo_section_id�
pg_restore: creando INDEX �public.matrix_stat_datos_idx�
pg_restore: creando INDEX �public.matrix_stat_expr_idx2�
pg_restore: creando INDEX �public.matrix_stat_expr_idx3�
pg_restore: creando INDEX �public.matrix_stat_expr_idx4�
pg_restore: creando INDEX �public.matrix_stat_id_expr_expr1_idx�
pg_restore: creando INDEX �public.matrix_stat_id_expr_expr1_idx1�
pg_restore: creando INDEX �public.matrix_stat_id_idx�
pg_restore: creando INDEX �public.matrix_structurations_datos_idx�
pg_restore: creando INDEX �public.matrix_structurations_id_desc_idx�
pg_restore: creando INDEX �public.matrix_structurations_id_idx�
pg_restore: creando INDEX �public.matrix_structurations_relations_idx�
pg_restore: creando INDEX �public.matrix_structurations_section_id_idx�
pg_restore: creando INDEX �public.matrix_structurations_section_tipo_idx�
pg_restore: creando INDEX �public.matrix_structurations_section_tipo_section_id_idx�
pg_restore: creando INDEX �public.matrix_test_datos_idx�
pg_restore: creando INDEX �public.matrix_test_expr_idx�
pg_restore: creando INDEX �public.matrix_test_expr_idx1�
pg_restore: creando INDEX �public.matrix_test_expr_idx2�
pg_restore: creando INDEX �public.matrix_test_expr_idx3�
pg_restore: creando INDEX �public.matrix_test_expr_idx4�
pg_restore: creando INDEX �public.matrix_test_id_idx�
pg_restore: creando INDEX �public.matrix_test_id_idx1�
pg_restore: creando INDEX �public.matrix_test_section_id_idx�
pg_restore: creando INDEX �public.matrix_time_machine_id_matrix�
pg_restore: creando INDEX �public.matrix_time_machine_lang�
pg_restore: creando INDEX �public.matrix_time_machine_section_id�
pg_restore: creando INDEX �public.matrix_time_machine_section_tipo�
pg_restore: creando INDEX �public.matrix_time_machine_state�
pg_restore: creando INDEX �public.matrix_time_machine_timestamp�
pg_restore: creando INDEX �public.matrix_time_machine_tipo�
pg_restore: creando INDEX �public.matrix_time_machine_userID�
pg_restore: creando INDEX �public.matrix_users_datos_gin�
pg_restore: creando INDEX �public.matrix_users_relations_idx�
pg_restore: creando INDEX �public.matrix_users_section_id�
pg_restore: creando INDEX �public.matrix_users_section_tipo�
pg_restore: creando INDEX �public.matrix_users_section_tipo_section_id�
pg_restore: creando INDEX �public.relations_from_component_tipo�
pg_restore: creando INDEX �public.relations_section_id�
pg_restore: creando INDEX �public.relations_section_tipo�
pg_restore: creando INDEX �public.relations_section_tipo_section_id�
pg_restore: creando INDEX �public.relations_target_section_id�
pg_restore: creando INDEX �public.relations_target_section_id_section_id�
pg_restore: creando INDEX �public.relations_target_section_tipo�
pg_restore: creando INDEX �public.relations_target_section_tipo_section_tipo�
pg_restore: creando INDEX �public.relations_target_section_tipo_target_section_id�
PRECAUCI�N: errores ignorados durante la recuperaci�n: 53
pg_restore: creando INDEX �public.matrix_time_machine_id_matrix�
pg_restore: creando INDEX �public.matrix_time_machine_lang�
pg_restore: creando INDEX �public.matrix_time_machine_section_id�
pg_restore: creando INDEX �public.matrix_time_machine_section_tipo�
pg_restore: creando INDEX �public.matrix_time_machine_state�
pg_restore: creando INDEX �public.matrix_time_machine_timestamp�
pg_restore: creando INDEX �public.matrix_time_machine_tipo�
pg_restore: creando INDEX �public.matrix_time_machine_userID�
pg_restore: creando INDEX �public.matrix_users_datos_gin�
pg_restore: creando INDEX �public.matrix_users_relations_idx�
pg_restore: creando INDEX �public.matrix_users_section_id�
pg_restore: creando INDEX �public.matrix_users_section_tipo�
pg_restore: creando INDEX �public.matrix_users_section_tipo_section_id�
pg_restore: creando INDEX �public.relations_from_component_tipo�
pg_restore: creando INDEX �public.relations_section_id�
pg_restore: creando INDEX �public.relations_section_tipo�
pg_restore: creando INDEX �public.relations_section_tipo_section_id�
pg_restore: creando INDEX �public.relations_target_section_id�
pg_restore: creando INDEX �public.relations_target_section_id_section_id�
pg_restore: creando INDEX �public.relations_target_section_tipo�
pg_restore: creando INDEX �public.relations_target_section_tipo_section_tipo�
pg_restore: creando INDEX �public.relations_target_section_tipo_target_section_id�
PRECAUCI�N: errores ignorados durante la recuperaci�n: 53

¿Me podrías echar una mano?

Muchas gracias

Backup Path

Hello, I'm a new user from Valencia, and when I'm restoring the DB I write /install/db/dedalo4_install.backup

I don't know why but it doesn't work. I hope you can help me. Thanks.

Automatic Translation of Interviews

The "Automatic Translation" option in the "Interview Translation" tool does not work for us. The "Copy to destination" option does work and copies the content of the "Source language" box into the "Target language" box, but the "Automatic translation" option after a waiting time ends without adding any content in "Target language" and without returning any error in the logs or in the console.

This functionality had previously been used successfully in more than 60 interviews.

The value of DEDALO_TRANSLATOR_URL was 'http://babel.antropolis.net/babel/'. We have updated it to 'http://babel.antropolis.net/babel_engine/' (as in the sample.config4.php file) but the behavior is the same.

We have also tried a "clean" installation of Dedalo with the same result.

We see that in the demo of https://dedalo.render.es/dedalo it does work correctly so it seems that there is something that escapes us. Maybe the url of the translation tool could have been changed or something like that.

Let's see if you can give us some light...

Thanks in advance

No chance to set admin's password

After installing JQuery and Bootstrap and running Dédalo into the Browser, it requests me a username and a password, so I have no chance to set the admin's one (as it is said in the installation procedure instructions).

Portuguese Translation

Greetings,

I'm opening this issue as a representative of Universidade Lusíada.
We would like to use your application but in order to do so, we needed to translate dedalo to Portuguese (Portugal).
Could you guide us through the process? What do we need to do?

Best regards,
José Nobre

Thesaurus: Rename NA into SN (?) like Scope note

Instead of too many abbreviations, maybe simply write: scope | observations | code

Update ontology json file

The json file with the ontology (dedalo/install/import/ontology/json_file/structure.json.zip) is dated 07-07-2021. Could you update it to the latest version of the ontology to be able to import it into Dedalo?

Thank you so much

Print templates error

Dear All,

This issue is related to the #38. We still experience some issues with the print templates:
When we try to print, Dedalo returns one error “Sorry. Error was found on render pdf file. See the log for more info “.

You can found the log and the capture of the error screen attached to this ticket.

print_error
Error plantillas impresion Dedalo.txt

Also, we can’t delete any template. There isn’t any button or command to do it.

Thanks a lot for your time. Regards.

Errors with precompiled software in Dedalo 5.8.3n

When I log for the first time with de admin user, I get errors with three software libraries that are alredy precompiled in Dedalo.
Yo can see the errors in the atached pdf

ERRORS LOGIN ADMIN.pdf

We have another problem with the backup and trying to update de structure. The backup is 0.0 Bytes

Help, please.
Thank you very much.

Thesaurus issue

Hi,

We have experienced a problem whe we try to create a new term in the Thesaurus.

We get this message:

DUMP
Caller: /lib/dedalo/common/class.common.php
Line: 316
Inside method: get_matrix_table_from_tipo
name: debug_backtrace() ++
value: Array
(
[0] => Array
(
[file] => /opt/aplicacionesweb/institutomemoria/web/dedalo/lib/dedalo/search/class.search_development2.php
[line] => 113
[function] => get_matrix_table_from_tipo
[class] => common
[type] => ::
[args] => Array
(
[0] => hierarchy2
)

"_info": "ar_target_section_tipo is calculated in class as prefix. 2 for each virtual section",
"css": {
".wrap_component": {
"mixin": [
".vertical"
],
"style": {
"width": "24%"
}
}
}
}
[prefijo:protected] => hierarchy
[filtroTerminos:protected] =>
[ID:protected] => hierarchy27
[strTableName:protected] => jer_dd
[arRelationMap] => Array
(
[terminoID] => terminoID
[parent] => parent
[modelo] => modelo
[esmodelo] => esmodelo
[esdescriptor] => esdescriptor
[visible] => visible
[norden] => norden
[tld] => tld
[traducible] => traducible
[relaciones] => relaciones
[propiedades] => propiedades
)

SELECT DISTINCT ON (hi20.section_id) hi20.section_id,
hi20.section_tipo
FROM matrix_hierarchy AS hi20
WHERE hi20.id in (
SELECT DISTINCT ON(hi20.section_id,hi20.section_tipo) hi20.id FROM matrix_hierarchy AS hi20
WHERE (hi20.section_tipo='hierarchy20')
ORDER BY hi20.section_id ASC --allow_sub_select_by_id=true
LIMIT 1 OFFSET 1
)
ORDER BY hi20.section_id ASC
LIMIT 1;

)
type: array
Caller2: /opt/aplicacionesweb/institutomemoria/web/dedalo/lib/dedalo/search/class.search_development2.php
Function: set_up [Line: 67]

DEBUG_LOG [DEBUG] search_development2::parse_search_query_object SQL QUERY: -- Search Without order SELECT DISTINCT ON (hi20.section_id) hi20.section_id, hi20.section_tipo FROM matrix_hierarchy AS hi20 WHERE hi20.id in ( SELECT DISTINCT ON(hi20.section_id,hi20.section_tipo) hi20.id FROM matrix_hierarchy AS hi20 WHERE (hi20.section_tipo='hierarchy20') ORDER BY hi20.section_id ASC --allow_sub_select_by_id=true LIMIT 1 OFFSET 1 ) ORDER BY hi20.section_id ASC LIMIT 1;
DEBUG_LOG [DEBUG] search_development2::parse_search_query_object SQL QUERY: -- Search Without order SELECT DISTINCT ON (dd64.section_id) dd64.section_id, dd64.section_tipo, dd64.datos#>>'{components,dd62,valor_list}' as dd62 FROM matrix_dd AS dd64 WHERE (dd64.section_tipo='dd64') ORDER BY dd64.section_id ASC -- allow_sub_select_by_id=false ;
Ops.. [Exception] Error Processing Request. Not use component tipo (hierarchy2) to calculate matrix_table. Use always section_tipo
Exception Object
(
[message:protected] => Error Processing Request. Not use component tipo (hierarchy2) to calculate matrix_table. Use always section_tipo
[string:Exception:private] =>
[code:protected] => 1
[file:protected] => /opt/aplicacionesweb/institutomemoria/web/dedalo/lib/dedalo/common/class.common.php
[line:protected] => 318
[trace:Exception:private] => Array
(
[0] => Array
(
[file] => /opt/aplicacionesweb/institutomemoria/web/dedalo/lib/dedalo/search/class.search_development2.php
[line] => 113
[function] => get_matrix_table_from_tipo
[class] => common
[type] => ::
[args] => Array
(
[0] => hierarchy2
)

)
Home Back Sorry, an error was found

Regards,

Problem with upddate to version 5.7.3

Hi,

We are trying to upgrade a Dedalo installation from version 5.5.37 to version 5.7.3.

Previously we had already successfully updated this same installation.

We have replaced the files on disk and added the new variables to the config file and when accessing Dedalo it already indicates that it is version 5.7.3.

Then we have updated the data version to 5.6.0, checking that the new properties column of type jsonb has been correctly added to the jer_dd table.

But the last part of updating the structure is failing us. The files are downloaded correctly in the directory lib/dedalo/backup/backups_structure/ srt_download but an error is occurring with the import of the file dedalo4_development_str.custom.backup

We have tried to manually launch the pg_restore command from command line and we get the following error "pg_restore: [archiver] unsupported version (1.14) in the file header"

Investigating the error it seems that it is because the file has been generated with a later version of PostgreSQL.

On the server we have version 10.16 installed. Is there any way to import the file into pgsql 10 or is this version of pgsql no longer valid for the latest version of Dedalo?

Or it may be that we need to carry out a previous configuration step?

I don't know if a similar case has happened to you or has been reported to you.

I hope you can help us with this

Numisdata ontology in Dédalo

Hi Alex,
After Manuel's instructions about Numisdata yesterday, we have one question that we hope you can help us with. We succeeded in installing the Numisdata ontology in Dédalo, but it still looks a bit different from the TEST version we worked in yesterday. We can still see much more of the 'normal' Dédalo environment. For example, under 'catalogue' we still have to click through 'cultural' > 'material' > 'moveable heritage' etc. before getting to the parts of Numisdata that are relevant to us (mints, types, archive etc.). In the TEST version, these show up immediately when clicking 'catalogue':

How do we change this? I hope you can help us with this!

All best,
Marleen (also on behalf of Ivan)

Getting database connection error

Hello,

This is the error

I ask for help because I don´t know whats wrong this time. I only know I'm close to the solution.
Please, thanks for any comment.

pgsql-socket

During the installation of Dédalo, what do you mean by /var/pgsql-socket/ in sample.config4_db.php?

Problems with first change of admin password.

After running Dedalo into the browser I directly get the login page for Dedalo. I haven't been asked to change the admin password so I don't know which password to use.

Can't enter to root user on Dédalo 4.0.23

I've already set the "root" password but, when I try to log in it says that my password is already configured but it doesn't let me log in.

PDFjs - viewer_dedalo.html

When PDF is open, Dedalo use dedalo_viewer.html
Ex:
http://192.168.1.221/dedalo/lib/pdfjs/web/dedalo_viewer.html?pdf_url=/dedalo/media/pdf/standar/rsc165_rsc245_1.pdf?t=1464793022

Is this viewer_dedalo.html a modification of viewer.html?

Duplicate code on sample.config4.php

Duplicate code in sample.config4.php:

redefined variables on lines 180:192

SLOW_QUERY_MS
DEDALO_BACKUP_ON_LOGIN
DEDALO_BACKUP_TIME_RANGE

Defined on lines 104:115

Linking the images to other tables

Working on a project using Dedalo, I realized that, even if I get an image inside one of the other tables such as hoards or lfindspots, there's nothing linking said image to the other data, not even the image's section_id. Is this a problem related to configuration, something I haven't seen, or something else entirely?

Example below:

This findspot has an image attached with ID 2510.

There's no field with said ID here in the location table.

And the image doesn't have any linking to the findspot either.

Github updates and Entity structure

Hi,

We are new developers of Render in Valencia.

We are in doubt whether we can update code directly on Github or if all updates are done via pull request.

Once this is resolved, we also have the doubt if the changes that we are making in the structure of the different entities that we manage and that only affect the Database, without modifying any Dedalo source code file, should be reflected in Github in the dd_copy.sql file of install/import/hierarchy/dd_sql.gz that we have seen that includes information on the structure of different entities that we manage but that we cannot generate because it also contains information on entities that we do not manage. In the event that this file has to be modified, how would we do it? Do we have to tell you what we are modifying so that you reflect it?

And finally, once Dedalo is installed and the DB found in install/db/dedalo4_install.backup is restored, is it possible to load the structure of a certain entity, such as mupreva or muvaet, to display its menus and custom tabs? Or for this it would be necessary to restore the copy of the DB of that specific entity?

Thanks in advance

Install and test Dédalo 4 : success config but no access to main page

I've been trying to install Dedalo 4 on debian 11.3 with the configuration mentioned in the doc, after configuring the 3 files config4.php, config4_areas.php and config4_db.php.
I opened on the browser the url "http:/ /192.168.1.33/dedalo5/lib/dedalo/install/" and it gives:
Installation help
Installation info: https://dedalo.dev/v5
Config info: https://dedalo.dev/v5_config
Test setup
Configuration test passed for entity: dedalo

Install Dédalo DDBB
Install DDBB source file: /var/www/html/dedalo5/install/db/dedalo4_install.pgsql.gz
DB Config:
DEDALO_HOSTNAME_CONN: localhost
DEDALO_DB_PORT_CONN: 5432
DEDALO_SOCKET_CONN:
DEDALO_DATABASE_CONN: dedalo_db
DEDALO_USERNAME_CONN: dedalo_user

But the Main url "http://192.168.1.33/dedalo5/lib/dedalo/main/?t=dd242" does not display anything (This page does not work)

Thank you for helping.

Update to 5.8.2 - Language problem

After updating to version 5.8.2 the API is not providing the contents in Valencian language.

Acces Dedalo 6

Hi,

We would like to start testing version 6 in order to test the correct functioning of new features in this version.

We have updated a Dédalo installation to version 6 beta and when trying to access an incorrect user/password error is appearing.

With this same username/password we can access the same installation with Dédalo 5 without any problem.

Has any modification been made in terms of access, password encryption,...? Or is it necessary to make an update on the BBDD to be able to use Dédalo 6?

Thanks

Subtitle sync

Dear all,

we're working with Dédalo v6 in an oral history archive. For this project we have created a kind of exhibtion that shows very concret exceprts of interviews in 3 different languages.

We're using subtitles in the excerpts, but some times there is a small time delay between audiovisual play and subtitles starting.

Is it possible to refine?

"Informants" Tool slow

This tool currently is very slow for Damian and Anna Maria. It works for me. But it stops Damian, even when I made him Administrator. His other internet works. He uses Chrome.

Add a "Translated" field in the "Audiovisual/Process" area

Menu with valid permissions not shown

Hi,
We have a problem with area_activity. All user profile in our instalation have the correct permissión but the menu item is not showned.

Help wanted, thank you very much.

Tools in Dedalo 6

Hi,

I wanted to ask you a question about the tools in Dedalo 6.

The fact is that we have a tool that we use in different ontologies to carry out the massive import of images and their association to elements of a section (tool_import_images). When updating to Dedalo 6 this tool has stopped working.

The same goes for other tools like tool_import_bibtex and tool_import_zotero from the generic rsc205 section.

We have seen that Dedalo 6 incorporates a new Tools section. We understand that the tools in this new section will have to be created or registered, but we don't quite understand how it works. Could you explain a bit about the process to create a new tool, in this case the image import tool?

We have also heard rumors that in Dedalo 6 everything was going to be unified to a single importer. Will it also be used for the massive import of images or will we have to keep the tool we currently use?

Thanks

Function array() error in new update

.../dedalo-4/lib/dedalo/area/class.area.php

[02/06/16 16:58:27] dd_error::captureShutdown Ops.. [Fatal Error] Call to undefined function arra()

Array
(
    [type] => 1
    [message] => Call to undefined function arra()
    [file] => /opt/dedalo-4/lib/dedalo/area/class.area.php
    [line] => 178
)

Change function arra() to array()

Import Toponomy problem

Hi,

We need to import 36 toponomies to our installation and I get a problem in the first attempt with de1. See capture below.

Help wanted, please!

DEDALO_PREFIX_TIPOS need 'ich'

At line 250
define('DEDALO_PREFIX_TIPOS', serialize( array('dd','rsc','oh') ));
change to
define('DEDALO_PREFIX_TIPOS', serialize( array('dd','rsc','oh','ich') ));
if not

Exception Object
(
[message:protected] => Error Processing Request. parent wrong tipo 'ich1'
[string:Exception:private] =>
[code:protected] => 1
[file:protected] => /opt/dedalo-4/lib/dedalo/db/class.RecordObj_descriptors_dd.php
[line:protected] => 37
[trace:Exception:private] => Array

Update to V.5.6.0

A problem the remove the main dd tld in the _dd tables.

In the V5.6.0 update. If you update the ontology before you has the code installed, is possible loose the main ontology (dd tld) into 'jer_dd' and 'matrix_descriptors_dd' tables.

Does Dédalo have 'templates' depending on the collection?

Hi,

I use Omeka to manage heritage collections and depending on the collection I use one template or another. That is, a heritage collection differs from a scientific-technical collection and therefore the required fields are different in both.

As I see, there is only one template. I know that fields can be added or removed in the only template that exists but it is not what I am looking for.

The question is if we can use different templates in Dédalo depending on the collection.

Thanks.

Print Templates

Dear all,

Recently, we updated Dedalo to the version 5.7.77 of the product.
After that, the custom print templates add option is missing.

We already reviewed the privileges of the role and everything about that is OK.

Parámetros configuración carga de ficheros

Hola,

Estamos teniendo problemas con la configuración del Sistema a la hora de poder cargar imágenes, videos, … Nos muestra un límite de 2MB.
Por favor, ¿podrías indicarnos qué parámetros tenemos que configurar para aumentar esa limitación?

Hemos subido el valor en upload_max_filesize del php.ini pero parece que no tiene efecto.

Un saludo y gracias por la ayuda

Issues installing Dedalo: Failed opening config_auto.php

I've been trying to install Dedalo in an Ubuntu 20.04 Virtual Machine, and after finally being able to set the Apache server, and adjusting the php and Apache configurations, I'm getting this error when I open the website through my web browser:

Ops.. [Fatal Error] include(): Failed opening '/var/www/html/dedalo/lib/dedalo/config/config_auto.php' for inclusion (include_path='.:/usr/share/php')

I've checked the files in that folder, and there's no config_auto.php. Is there something I'm missing, or is it a different kind of error?
Thank you.

Some users don't see the Thesaurus terms

for example Damian, who is Adminstrator - I see it, however.

Dedalo

Hi ! I am begginner with Dedalo i installed it recently , but i didn't understand from where can i start using it ! for example how can i create a template ?
If anybody have a tutorial or a documentation explaining this i will be grateful !!
Thanx

Create templates Issue

In the version of Dédalo 5.7.77 03-07-2021, with DB PGSQL 11.9 we detected an error that makes the option to create print templates disappear when printing. The log shows nothing significant. User permissions to create templates have been reviewed and are correct.

Server(s) infrastructure for a Dedalo installation and a nice front web

Hello

We have an installation of Dedalo in a physical dedicated server for the data of a numismatic archaeology project.

We are developing a nice web/smartphone front end so anyone can check the contents that are marked as public in the Dedalo installation.

We are wondering what it the best choice:

Using the same physical dedicated server both for the Dedalo installation and the web. It seems a good idea from the performance point of view (all the data in the same machine).
Leaving Dedalo as the only service in its server and using another (probably virtualized) server for the web. It seems better from a security point of view.

Thanks in advance for your help!

Publications (rsc205) - Import from marc21

Hi,

We are having problems using the marc21 import from the publications tab (rsc205)

We hadn't used it yet so we don't know if it ever worked or never really worked.

We have tested it in several Dedalo installations, even in a new and clean installation, copying the pear/FILE/MARC.php library, but the error occurs in all of them.

If we try to import the whole file with the mrc extension we get an error when importing.

If we modify the mrc file and leave only one record ( tag), the import does finish correctly but a new record is created in publications (rsc205) without any information, with all fields blank.

We were also going to test the version you have at https://dedalo.render.es/dedalo to see if it worked there but we have seen that the import from marc21 does not appear. There are only the options to import Zotero and BIBtex.

We also have evidence that a long time ago in a Dedalo project in Barcelona it was being used correctly.

Is it still working? Do I need to do any additional configuration to make it work?

Thanks and regards

double space when delete one annotation within a word in the transcription

When I insert a note within a word

and then delete it afterwards,
a space remains:

"ERR_TOO_MANY_REDIRECTS" executing Dedalo v5.8.3 for the first time

Hi,
We can't set de root password at this point (image below) when set de web browser direction at https://dedalo.wondercoins.es/lib/dedalo/install/index.php

We've got the same kind of error when access to https://dedalo.wondercoins.es/index.php

We ask for your help. Thanks for any comment.

Import Toponomy final step

First I create the toponymy into the Hierarchy menu into Thesaurus. Then I import the data in postgres database (dz1.copy file)
But now I can´t find de "Dedalo Counters State" in the administration tool to update the counters (maybe I'm blind)
Sorry, can you show me where is that?

Thank you very much!

As always, best regards.

Getting fatal error almost finishing installation of DEDALO v5.8.3

Hi,
This is the error we get in the web browser trying to finish Dedalo installation:

I think our server configuration is completed but I'm not sure after this.
We ask for help. Thanks for any comment.

How to change RAM requirements used by PHP and PostgreSQL in the virtual machine for developers.

When I changed the RAM requirements (from 8GB to 4GB) used by PHP and PostgreSQL in the virtual machine for developers
(see https://dedalo.dev/v5#dd1100_1890), I lost access to the Dédalo interface used to manage heritage data (http://localhost/dedalo):

Ops.. [Exception] Error. Could not connect to database (52).

I just changed the /etc/postgresql/14/main/postgresql.conf file.

I don't know if the PHP /etc/security/limits.conf file should also be modified.

Help, please.
Thank you very much.

Hide fields from the filters section

Hi,
I want to ask you a question.
I am working on a section in which I have hidden some fields to a certain profile.
When users with the assigned profile access they do not see the fields, so far so good.
On the other hand, I have realized that in the Filters section these fields do continue to appear.
Is there a way that these fields do not appear in the filters either, adding some property or similar, without having to delete the field?

Thanks

renderpci / dedalo Goto Github PK

dedalo's Introduction

V6 transition state

1. What is Dédalo?

2. Dédalo demo

3. Who uses Dédalo?

4. Dependencies

4.1. Services required for the OS

4.2. Libraries required for Dédalo

4.3. Libraries required for the OS

5. Installation

5.1. Ready-to-use Virtual Machine for V5

5.2. Video-guide for V5 installation

5.3. Manual installation

6. Update

7. Importing toponymy

8. Server system

9. Compatible browsers

dedalo's People

Contributors

Stargazers

Watchers

Forkers

dedalo's Issues

Recommend Projects

Recommend Topics

Recommend Org