Meeting notes

Meeting technical possibilities & constraints

Agenda / outcome: understand what's possible + feedback on proposa Date: Sept 5, 22 Participants: Sofie MNordine BittichJudith Straetemans

OP Constraint in the future

• Privacy of belonging to an eredienst; name of eredienst should not be seen in Personen module

• Decision of Veronique

• In Person module

• One idea; create 2 databases

• Unscoped and unclear what the solution is & we don't need to take this into account for now

Technical constraints

• If there's a person WITHOUT position --> would not show up in search in the idea of 2 levels of information. This should NOT be the case as every Person need to have a position .

• Potential matches IS possible

• Judith to create JIRA tickets

Meeting to define next steps

Agenda / outcome: understand next steps for avoiding duplicates for Erediensten in de Module Personen Date: Aug 23, 22 Participants: Sofie MSaska Pallayova Nordine BittichJudith Straetemans

List of data (excel)

• Assumptions why some people don't have a bestuurs label; people that are inactive are not listed under a bestuur?

Missing data:

• Who added the people?

• Date when the person was added

• Inactive/active positions

• Positions

Context

• Position created before person takes time to change due to need for refactoring. You create a position —> there’s a delay in the position created

• Search

  • Search in 1 field; we would need to list out all the usecases, but its doable. Reason why we once did it differently besides issing requirements is unclear. Keep in mind usecase "what if last name is same as first name"

• Handling duplicated manually; we can generate a report that pulls duplicates & migrate it.

  • History of change

  • We can create a dashboard who was created by whom

• Onboarding / education of people new to OP (editors)

  • Request of roles is requested + we can contact them

Decisions made;

• We leverage this data & assume it’s true and start optimising based on it.

• Scope - Avoiding duplicates is only for erediensten (for OCMW's etc we'd need to look into the automatic import which is a different issue)

• Usertesting; add the other users to the testing

• POC to revert positions & start from name/first name (person) —> check if we can do it in an innovation sprint

Next steps;

• Split up Search & Userflow as different tickets & features to focus on

• Judith to spar with Saska on userflow first & search next

• Weekly updates to Nordine & Sofie

Demo meeting Fuzzy Search Sept 22

All designs are possible, except positions (see below) + the overview; Issue with overview to group positions by people because of the way it’s indexed (by position). This means 1 person can have 2 positions on 2 different pages.

• Can we change the pagination?

  • NO, we load 25 positions in the back-end

  • Solutions

    • Stop showing defaults if there is no filters or search so there is no load needed --> agreed this is the best solution

    • HACK it in the back-end

• Prevent search to not show auto suggestion

  • Should go to Appuniversum to fix —> will be pinged to Dieter/Sam

  • If it takes too long we will find our solution

• Position pages;

  • Not everyone has the right to see all positions.

  • People WITHOUT the rights should still be able to see the name so they don't create duplicate people --> this might create duplicate positions

To update:

• Search field always needs to be full name

• Name header needs to be 1 color + positions in another one

• 2 tables for visual separation