update to 4.9.0

This version change the component_filter that affect to all compoents.
take care to apply this update.

.gitignore

@@ -0,0 +1,58 @@
+#
+# DEDALO4 FOR PUBLIC GITHUB PUBLICATION
+
+
+# Ignore configuration files that may contain sensitive information.
+config4*
+config.php
+server_config_api.php
+json_config.php
+
+# various
+lib/*
+!lib/dedalo
+acc
+_acc
+des
+test
+install/import/hierarchy
+lib/dedalo/des/*
+str_data*
+lib/dedalo/diffusion/diffusion_index_ts_V40
+lib/dedalo/publication/client_api/v1/sample*
+
+# extras ignore all except common
+lib/*/extras/*
+!lib/*/extras/oh
+
+# Ignore paths that contain generated content.
+media/*
+media_test
+lib/*/backup/backups/*
+lib/*/backup/users
+lib/*/backup/backups_structure
+lib/*/backup/users
+temp
+write
+template_maps
+tpl
+lib/dedalo/publication/client_api/*/docu/ui/*
+lib/dedalo/tools/tool_layout_print/data/*
+lib/dedalo/tools/tool_layout_print/print_pdf/*
+
+# Ignore default text files
+robots.txt
+
+# Ignore some special files 
+koala-config.json
+.DS_Store
+.eslintrc
+.htaccess
+.htaccess~
+.htaccess~~
+.htaccess~~~
+*.log
+*.graffle
+*.data
+.smbdelete*
+*~

Readme.md

@@ -6,17 +6,18 @@
 
 Dédalo is a knowledge management system for Cultural Heritage (tangible and intangible), Natural Heritage and Oral History/Memory. 
 
-Dédalo is a Open Source software based in a new paradigm of programing: develop objects with a ontology model and control the app flow with the ontology descriptors, related terms, no descriptors, TG, TE, etc. The objects have a MVC structure linked to the ontology and the database is a NoSQL model. The data is stored in JSONB (binary).
+Dédalo is a Open Source software based in a new paradigm of programing: develop objects with a ontology model. The ontology control the app flow with the descriptors, related terms, no descriptors, TG, TE, etc. The objects are builded with a MVC structure and are linked to the ontology. The database use a NoSQL model, all data is stored in JSONB (binary).
 
-Dédalo use the structure Ontology for three things:
+Dédalo use the structured Ontology for three things:
 
 	1. Make the data structured. (user data is stored without fixed structure)
-	2. Do the programing objects in the execution time (in real time).
+	2. Build the programing objects in the execution time (in real time).
 	3. Interpret the code and the data and translate to multiple formats (RDF, JSON-LD, SQL, CSV, XML, Dublin Core, HTML, PDF, etc)
 
 The ontology can be changed in the time and this will change the data and the programing code; you can develop new functionalities without change the data, and you can change the metadata without change the code or the data.
 
-Dédalo is based in linked data model, and use a relative, multireference and universal locator. THe locator can find a entity, section, component, and tag. In other words, the locator can find, archives (in others entities), records, fields, and part of the fields (sub-field data).
+Dédalo is based in linked data model, and use a relative, multireference and universal locator. The locator can find:
+entity, section, component, and tag. In other words, the locator can find, archives (in others entities), records, fields, and part of the fields (sub-field data).
 
 Dédalo is a real multilingual app (Dédalo can use any language) in the interface and the managed data, has a multi-thesaurus engine and manage multiple resources and resolutions for video, image, pdf, notation scores, etc. 
 
@@ -35,7 +36,7 @@ Some projects using Dédalo to manage their Cultural Heritage or Oral Archive:
 <p><strong>Projects: </strong> 
 
 <p><a href="http://museoprehistoriavalencia.org/web_mupreva/?q=en" target="_blank">Museu de Prehistòria de València</a></p>	
-<p><a href="http://bancmemorial.gencat.cat/web/home/?&amp;lang=eng" target="_blank">Memorial Democràtic</a> (Banco audiovisual de la Memoria Colectiva)</p>
+<p><a href="http://bancmemorial.gencat.cat/web/home/?&amp;lang=eng" target="_blank">Memorial Democràtic</a> (Banco audiovisual de Memoria Colectiva)</p>
 <p><a href="http://www.mujerymemoria.org" target="_blank">Mujer y Memoria</a> (Woman and Memory - Mothers and daughters of the Spanish transition. An oral history project)</p>	
 <p><a href="http://memorialdemocratic.gencat.cat/ca/exposicions/expcicions_virtuals/catalunya_en_transicio/" target="_blank">
 	Catalonia in transition</a> (Transition in Catalonia - Memorial Democràtic)</p>
@@ -49,7 +50,7 @@ Some projects using Dédalo to manage their Cultural Heritage or Oral Archive:
 
 - PHP 7.0+
 - Apache 2.4.2+
-- Postgres 9.5+
+- Postgres 9.6+
 - MySQL 5.6+ (NOT REQUIRED, only if you want use it for publication)
 
 *libs required for the Dédalo*
@@ -96,8 +97,8 @@ Some projects using Dédalo to manage their Cultural Heritage or Oral Archive:
 6. Change the file /lib/dedalo/config/sample.config4_db.php with your DB configuration.
 7. Rename the /lib/dedalo/config/sample.config4_db.php to /lib/dedalo/config/config4_db.php.
 8. Run Dédalo into the browser. 
-9. Fix your root password (you can change only once), the default account is: root (this user is a superuser and only for development or debuger the application).
-10. Create one Administrator user account with all access to the system.(this user will be the administrator of the system)
+9. Fix your root password (you can change it only once), the default account is: root (this user is a superuser and only for development or debuger the application).
+10. Create one Administrator user account with all access to the system. This user will be the administrator of the system.
 11. Logout and login with the Administrator acount.
 12. Create Users and Projects as you need.
 Optional: Import the toponymy that you will need (Dédalo install DB will not provide specific toponymy by default anymore).
@@ -106,12 +107,12 @@ Optional: Import the toponymy that you will need (Dédalo install DB will not pr
 
 *Please read the "Updates.md" file for specific notes, procedures, etc, of the versions.*
 
-Dédalo have three updates procedures:
+Dédalo have three main updates procedures:
 
 1. Update the code files (php, js, css, html, etc)
 	-  Make 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 (/lib/dedalo/config4.php and /lib/dedalo/config4_db.php) is not possible change it automatically because are the configuration specific of the users. If you don't change the config files, Dédalo will require the new "define" variables and will stop the app.
+	-  You will need see the new config files and put the changes into your own config files (/lib/dedalo/config4.php and /lib/dedalo/config4_db.php) is not possible change this files automatically because are the configuration files and 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.
 
 2. Update the ontology structure with the sections, components, list, etc
 	-  Do the first update step
@@ -132,7 +133,7 @@ Dédalo have three updates procedures:
 
 **IMPORT TOPONYMY**
 
-1. first create the toponymy into the Hierarchy menu into THesaurus:
+1. first create the toponymy into the Hierarchy menu into Thesaurus:
 	-  Login in Dédalo
 	-  Go to "Thesaurus -> Hierarchy" section
 	-  Find the country that you want import
@@ -168,26 +169,26 @@ Dédalo in the server part is tested into the next Operating Systems:
 - CentOS 6.5 (deprecated update as soon as possible), 6.6, 7.1
 - Red Hat Enterprise Linux 6.5 (deprecated update as soon as possible), 6.6, 7.1
 - Debian 8.7
-- MacOsX 10.8 (deprecated update as soon as possible), 10.9, 10.10+
+- MacOsX 10.9 (deprecated update as soon as possible), 10.10, 10.11+
 
 All other Linux will be compatible but we don't test it.
 
-Windows: is possible that Dédalo can run, but NO TESTED.
+Windows: is possible that Dédalo can run, but we NO TESTED.
 
 **USE**
 
 Dédalo version 4, is only certificated and proved into the webkit browsers (Chrome, Safari,...). 
-Firefox situation: Is possible use Firefox, but not in production, this version of Dédalo(V4.7+) is compatible, but we need feedback from the users, please comment your experience. 
+Firefox situation: This version of Dédalo(V4.8+) is full compatible, and can be used in production, but we need more feedback from the users, please comment your experience. 
 
 Browser	|	Version |	certificated
 --------- | --------- | ---------
 Chrome	|	60+ | YES - recomended
 Chrome	|	50+ | Deprecated (Please update as soon as posible)	 
 Chrome	|	0 to 50 | NO	 
-Safari	|	9+ | YES
-Safari	|	7 to 8 | Deprecated (Please update as soon as posible)
-Safari	|	0 to 6 | NO	
-Firefox	|	49+ | The compatibility now is complete, but we need feedback to resolve issues in the diary work with Firefox (15-09-2017), please test it and comment it.
+Safari	|	9+ | YES;Safari has a conflict with the users section with the pw component and the browser autofill. USE IT WITH CARE.
+Safari	|	8 | Deprecated (Please update as soon as posible)
+Safari	|	0 to 7 | NO	
+Firefox	|	50+ | The compatibility now is complete, but we need feedback to resolve issues in the diary work with Firefox (28-03-2018), please test it and comment it.
 Firefox	|	40-49 | NO
 Firefox	|	0-40 | NO
 EDGE	| All 	| For us NO, we don't test it. But, is possible that Dédalo run fine in the last versions, because Microsoft say that EDGE is ECMA and HTML5 standards compatible. But we insist that we don't test it.

Updates.md

@@ -1,5 +1,40 @@
 **UPDATES AND CHANGES**
 
+*Ver 4.9.0 - 14-05-2018
+Today we introduce the update of the V4 to 4.9.0
+
+This update fixed some issues and bugs for the V4.8.4
+
+This version change the format of the component_filter, named project inside the records. This version ends the transition of the all component_relations to new model and apply the new search version.
+
+The component_filter chang the format from the traditional object {"1":"2"} to the normalized locator [{"section_id":"1", "section_tipo":"dd153"}].
+
+And the new relation model add to the locator the new two propieties "from_component_tipo" with the tipo of the compoment that has the information and the "type" with the normalized type relation: 
+	[{"type":"dd675","section_id":"1","section_tipo":"dd153","from_component_tipo":"mdcat1487"}]
+
+This version fix some issues in the search and close the beta situation with the new search model. 
+
+The next step will be the addaptation of our model to the SQL/JSON:2016 that will be implemented in postgres this year.
+
+
+*Ver 4.8.4 - 28-03-2018
+Today we introduce the update of the V4 to 4.8.4
+
+This update fixed some issues and bugs for the V4.8.3
+
+This version implement the new search to the thesaurus context. The new filter do joins between main secion to sections that has relations and we uptade the concept to build joins with multiple sections to multiple sections. The concept is that the user need search between multiple main sections, for ex: toponymy that the main sections can be: Spain, France, Italy, etc... es1, fr1, it1, etc... Normally the components of this sections will be the same, like term component, that is because the thesarurs, normally, is builded like virtual sections of the "real" thesaurus section.
+
+We introduce into the JSON_QUERY_OBJECT the propertie "section", one array of main sections. If this array is configurated with more that 1 section, the joins will be named with "mix" in the main path (first section_tipo in normal position). And will be builded the WHERE clause with all sections of the array.
+
+Limitations of the search: today the search can use ONLY one matrix table for the main sections, for ex: 
+	- matrix_hierarchy for sections es1, fr1, it1, etc
+but is not possible use two matrix tables for the main sections, for ex:
+	- matrix_hierarchy for es1,fr1,it1, etc
+	- matrix_languages for lg1
+This limitation is only for MAIN sections (the first position of the path), not for the relations (second or more deep positions in the path), that can be in multiple tables:
+	- matrix for oh1 and relations with matrix_list, matrix_hierarchy, matrix_langs, etc
+This limitation is not a problem and we don't change it for now. 
+
 *Ver 4.8.3 - 03-03-2018
 Today we introduce the update of the V4 to 4.8.3
 

info.php

@@ -0,0 +1,3 @@
+<?php 
+#echo phpinfo();
+?>

lib/dedalo/area/class.area.php

@@ -36,7 +36,7 @@ function __construct($tipo, $modo='list') {
 		# common load tesauro data of current obj
 		parent::load_structure_data();
 
-		#dump($this,'this');
+		return true;
 	}
 
 	# define tipo