People transformation plan

Alex

As we discourse by long time, People needs changes and those changes are very important in Dédalo. We have a consensus about the merge sections People and People under study.
This change requires a transition plan and we want to do it before the ontology change, previously tagged as version 6.3.0.

Therefore, the first step is change our version planing. The next version will change the People model and the ontology change will be introduced in v6.4.

v6.3.0 ----> People changes
v6.4.0 ----> Ontology changes

The one moth plan:

Update the ontology to include the rsc197 as optional section in every People field in the ontology.

This change has been done into the ontology:

Dédalo 2024-12-01T00:00:00+01:00 Benimamet

Task to do: Update your installation and test if your fields can handle the People under study data in the same way than other People. For example, Authorship and responsibility field in Publications will get the possibility to get data from People under study.

Please report if you find any field that will need change to get it (test if you can choose or not People under study)

The process was done: 09-12-2024

The v6.3.0 will move all your People data rsc194 into People under study data rsc197.

This update is scheduled for the week of 09-12-2024. Please test it previously to be implemented in Production.

Note: at this point If you want to continue using two different sections for People you can follow the optional step defined in the last part of this topic.

Change permissions to remove access to People section.

We will need to maintain People section for compatibility of previous versions. And before remove this section, you have to change the permissions to remove the possibility of any user create and link data from People

The process was done: 31-12-2024

Remove the People section from ontology and rename the People under study

The compatibility will be removed in the last 2024 ontology, therefore any ontology >31-12-2024 will not include it. So, plan your update tasks previously. If you don't update your installation in those time frame, you will not be able to apply any ontology changes in your 6.2.9 version and you will lost access to your People data (you will change it, but in a complicated way).

The last ontology publication in 2024 was: Dédalo 2024-12-31T00:00:00+01:00 Benimamet
The process is currently on hold here

Review publication changes and web space.

The new People configuration will be change the publication schema, if you are publishing People rsc194 you will need re-publication your data and change the web programming to use the new configuration.

See the specific information of your catalogue tld below this topic.

Optional step

If you want to continue using two different sections for People you can create your own node with local tld and point it to rsc75 in the same way that rsc194 does. When you have this local node, you can create a 'move_tld' definition as:

[
	{"old":"rsc194" ,"new": "mytld1"  ,"type":"section" ,"perform":["replace_tipo"] ,"info": "Old People section => New local people section"}
]

Save as json file into the base->transform_definition_files and run it in administration panel.

Finally you will need to change the component calls to this new section. using your local tld instead the standard tld. You will need to mantain this new ontology nodes by your own.

Eulàlia Mesalles

Thank you for the information.

In publications I've found a field that may be personas and does not have people under study:
Other people

Hope this helps, Thank you!

Alex

Eulàlia Mesalles

Thanks a lot!. It helps.

The field that you point is a portal and the link to People is inside, so you need to create a record to check the People link

😉

Best

Alex

Changes in publication ontology of numisdata tld.

Numisdata ontology uses People rsc194 in two situations:

as authors of publications and the records.
for collection data of coins.

The main tipo is: numisdata58. It create a table named other_people with the definition of numisdata50 used for People under study data and named people and fill it with the People rsc194 data. So, the columns are compatible between tables.

numisdata58 === numisdata50
other_people === people

With the new situation, the Peoplersc194 id's will be changed with new ones at the end of People under studyrsc197. So, if you have 1580 records in People under study the person with section_id = 1 in People will be moved to section_id = 1581 in People under study and it will be identified as Moved from People in Typologyrsc449 field.

The numisdata web template use the table other_peoplenumisdata58 to search Authors in bibliography/publications, with the new situation, all people will go to the common table peoplenumisdata50 and the search need to discriminate people in publications from any other people as authorities, designers, issuers, etc.

So, right now, is added the typology in the new publication schema in the ontology:

Dédalo 2024-12-07T13:09:29+01:00 Benimamet

And you will need to change your data according this new situation.

Things to do for publications / bibliography:

Identify it as "Authors" or, "Publication authors" or something like that, and re-publish your data. It will use to filter the authors in publication web. It could be optional if you don't want filter people and the website will use all people, but it could be noisy.
change the template to call to peoplenumisdata50 instead other_peoplenumisdata58
Other way could be use the publications table to filter the authors, but the issue could be separate the authors because in publications all authors of a publication are joined in the columns : authorsrsc690 and authors_datarsc691, authors_name rsc734, authors_surnamersc735, etc.

Things to do for coins:

coinsnumisdata1036 table use other_peolplenumisdata58 table for the collectionnumisdata1063, but in those cases is compatible because it can call both tables at same time, so, you can publish your data and the resolution will be resolved directly.

Please comment when you have change your data with this new situation, and we remove the table other_people from the ontology.

I hope it will clear.

Best

PaCo

Alex Other way could be use the publications table to filter the authors, but the issue could be separate the authors because in publications all authors of a publication are joined in the columns : authorsrsc690 and authors_datarsc691, authors_name rsc734, authors_surnamersc735, etc.

We have taken the decision to implement the third option in the numisdata web template because don't implies changes into the publication schema and the current public data is compatible.

The template has been changed to get the autocomplete list directly from the publication table and the authors column, being careful how to handle cases with multiple authors, they are separated by |, so that duplicates in the list can be split and removed.

You can get the changes in the templete code at GITHUB commit

Alex

Hi!

We are closing this transformation plan. The deadline is now complete and there is only one task left on the calendar; remove the People section and rename People under Study as People.

We decided delay a little bit this last task because some projects are not updated and the ontology needs to be backwards compatible. Therefore, we will close the ontology update way to the 6.3.0 and the next version 6.4.0 will not be backwards compatible.

The last compatible version with People section will release in 2024-01-15, If you don't update your project you will not be able to update the ontology.

Best