@Alex @MercePB @Mariajobrador @Marta Perpiñán @Gael Proupin Cantelar
Hi All,
Here is a summary of what we discussed on last meeting (sorry for the delay).
Memory Friday Meeting Summary (27th March 2026)
Session Recording:
All agreed to record the session for future reference.
Data Frames on Fields ("Birth town," "Residence town," "Place of death"):
Alex explained that data frames are already implemented for links and demonstrated how it works in TCH (objects). However, this cannot be applied to literal text fields, which is a key change planned for version 7 of Dedalo.
Regarding uncertainty linked to a thesaurus of causes: The Numismatics project has established primary and secondary causes of uncertainty, and everyone agreed this thesaurus could be valuable for other projects. So, we kindly request @Manuel Gozalbes to share it with everyone.
Alex also showed that the system is customizable for each project.
It was agreed that this could be implemented in the fields "Birth town," "Residence town," and "Place of death." The discussion about linking residence town to a time range was postponed.
Uncertainty Use in Oral History:
Mariajo raised a question about whether uncertainty could be used for indexing interviews. Usually, if someone speaks about another person, the latter is indexed. If only one other person is quoted, it is linked but not indexed. After some discussion it was considered that introducing uncertainty at this level may not be necessary at this stage.
Exporting Problem:
An issue was raised about the exporting window sometimes changing the order in an apparently illogical way. Demonstrations were made, but the problem is difficult to pinpoint as it occurs inconsistently. It was agreed to conduct further research to identify the precise actions and sequence that cause the problem.
Selecting Changed Records:
To continue the request for the ability to filter records that a user is working on, it was agreed that simply filtering by users who changed fields is insufficient, as this does not prevent users from "spying" on others’ edits. The preferred solution is to filter by changes made only by the current user. However, this is more complex than it appears, so the issue was postponed for later discussion.
See you in next meeting!
