permissions: allow moderators to read emails #107
Conversation
kpsherva
force-pushed
the
user-moderation
branch
from
e5d25f9
to
856e467
Compare
resource: expose search all users endpoint
kpsherva
force-pushed
the
user-moderation
branch
from
856e467
to
6c183e2
Compare
| @@ -1,23 +1,46 @@ | |||
| { | |||
| "settings": { | |||
There was a problem hiding this comment.
this analyzer is needed to extract email domains to multifield: email.domain (see mapping of the email field)
| }, | ||
| "analyzer": { | ||
| "email": { | ||
| "tokenizer": "uax_url_email", |
There was a problem hiding this comment.
this tokenizer for the email is needed to keep the email as one token, otherwise ES creates many tokens on the email and can be confusing when searching - we learned that from user feedback in ILS (check ES docs)
| "type": "text" | ||
| "type": "text", | ||
| "fields": { | ||
| "keyword": { |
| "links": {"avatar": avatar}, | ||
| "links": resolved_dict.get("links"), | ||
| "blocked_at": resolved_dict.get("blocked_at"), | ||
| "verified_at": resolved_dict.get("verified_at"), |
There was a problem hiding this comment.
to be confirmed if we can expand those fields - they are added to the field_permission_dump, but this might not be enough
There was a problem hiding this comment.
My hunch is that if we're using email as above, this goes through the service and gets properly filtered, in which case any attribute would be good.
kpsherva
force-pushed
the
user-moderation
branch
3 times, most recently
from
d0d87d0
to
f0fd0af
Compare
search: add user facets
kpsherva
force-pushed
the
user-moderation
branch
from
f0fd0af
to
9b42e83
Compare
FAQ