Piotr Banaszkiewicz

This sounds like an extension to bulk-add persons interface, unless you want an entirely separate interface for that. Please let me know.

Hi @Talishask and @maneesha - the matching criteria are defined in `CommonRequest.host()` as below: ``` person.personal = request.personal AND person.family = request.family AND person.email = request.email ``` A single match...

Hi @Talishask > Could we do something that is a case by case basis, like: > > * If email (primary or secondary) and personal and family match = Matched...

@maneesha I don't think `title` or `URL` are used. I think you can remove them from both UI and database. Once you remove the fields and apply the migration, you...

@Talishask I can rework the search results page so that it looks like option 1 or like option 2 (both are feasible). I can even create a mixup (first tab...

@maneesha: yes, it's possible, but it requires adding a relationship.

I'll move this after email automation project is merged. This project adds support for Redis which should be very helpful in checking websites metadata.

Possible ref: #1195

Is it currently possible to again roll over an already rolled over membership? If yes, then this is an issue because it's not supported by the database design. We only...

Wouldn't it be simpler to produce an administrative job (script) to find all unconnected memberships from consecutive years and then connect them? And then leverage mechanisms preventing multiple roll overs?...