Next Memory Friday meeting to be held on 31 January 2024 at 13 h

More topics:

. Moving Component History to each field and highlight If ther are any comment

Hello!
@Alex @MercePB @Mariajobrador @Arancha

A quick review of the topics that were talked about at the Memory Friday Meeting:

• Alex explained the awards that were granted to Oroibidea and Moneda Ibérica: Well done!

• The number of registers made it difficult to look for "people under study" in the field where we used "people": We discussed different problems related:
  o The reason for incorrect filtering could be the error 502, which only impacts projects that use the Azure server.
  o Experimenting with AND and OR while searching: We came to the conclusion that we needed to reconsider it because switching to AND might make it harder to search than the current method.
  o Encourage users who complain to filter using the “link” method, likewise we actually do when linking people under study in affected people.

• Opening people to everyone (not related to projects). We weighed the advantages and disadvantages. We must take into account the consequences for those who aren't used to managing several projects.
  During the conversation, a concept came up that would be worth developing: adding a feature that allows you to view every “people under study” but only allows you to modify an individual once you've added them to your project. We all agreed that this is a significant shift and that we need to give it more careful consideration.

• Moving “Component History” to each field. We discovered throughout the conversation that the component history is, in fact, a field in the time machine. Therefore, we decided to keep the inspector's list of changes intact, but when someone comments, HIGHLIGHT the time machine in the field with a colour (as it is now implemented in the inspector).

• Alex explained to us that now TIME MACHINE has a feature to REVERSE massively a change made by error.