Màxim Colls

Great, thanks @NilHomedes for all the feedback. There's one little caveat in this issue. There's lot of flexibility on how Authorization Handlers store the form metadata. That logic is defined...

Regarding: > they would like to have the option to filter between process and components. Do you think we can add this to the AC? and > in fact the...

> Is it possible to differentiate who has been verified only to vote in the proposal component? Does the authorization handler save this data? I'd say that we don't have...

> In this case the columns would be the following: > User Hash > date_of_birth > postal_code > scope_name > scope_id > scope_code > gender @NilHomedes What are the scope...

> https://github.com/AjuntamentdeBarcelona/decidim-barcelona/issues/548#issuecomment-2392955899 I'm assuming that these scope columns were added when we thought that verifications were associated to a component, but it seems that they are not. The columns I'm...

> I was suggesting User Hash as a way to have a unique identifier for each verification in an anonymous way Do you want an identifier that is _impossible_ to...

> Yes, for privacy reasons, we do not want the identity of the verified persons to be known. This is essential to preserve participants privacy. Then, what it's going to...

@furilo ready to review in staging. I also assigned it to @entantoencuanto, but I still have to work on fixing and adding specs.

@NilHomedes got it, looks like we have a conflict in staging with another feature. I'll work on it. BTW, what do you mean by "The cell of the draggable icon...

@NilHomedes Fixed the comments in this review: https://github.com/decidim/decidim/pull/13074#pullrequestreview-2159063369 The problem was with a copule of invalid components. There was some components with scopes enabled but without any scope selected. Because...