Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[User Management] Sorting #12597

Closed
LukasReschke opened this issue Dec 4, 2014 · 2 comments
Closed

[User Management] Sorting #12597

LukasReschke opened this issue Dec 4, 2014 · 2 comments

Comments

@LukasReschke
Copy link
Member

LukasReschke commented Dec 4, 2014

As an admin, I want to be able to sort alphabetically and then get to the letter I want (such as C), which then shows me the users that begin with C. I need to manage hundreds of users within the ownCloud authentication system, or to manage attributes for a few users in a 20,000 user installation that uses an external authorization server, and lazy loading is not working.

Acceptance Criteria:
See #11852

Remarks by Engineering:

A heads up on the "going to C": What we would need to do is to filter with C,
but without the wild card in front of it (opposite to the current mechanism.
We cannot load everything until we reach C. Why? Think about 500.000 LDAP
users.

We would not be able to use established methods, but create new one's for the
user backends. First, because as stated before we automatically insert
wildcards. But then also: in LDAP you can search in several attributes, but in
this case we must only search the display name attribute. This is not a
problem, but to have it in mind when implementing.

The problem however is to do this on the user name. Not for local users, but
for LDAP, because they are only created "on-the-fly" (they are persistent and
ownCloud-specific, not necessarily identical to values in LDAP because we
avoid collisions by creating other names. Also, the rules for the user name
creation can be changed by the admin but apply only to newly fetched users).
When the default UUID attribute is used therefore, sorting does not make much
sense anyway. Maybe just searching for that attribute is a good enough
solution. Needs more investigations.

@MorrisJobke
Copy link
Contributor

I planned something similiar for the music app. This is called virtual scrolling.

@MorrisJobke MorrisJobke removed this from the 8.0-current milestone Dec 9, 2014
@MorrisJobke MorrisJobke mentioned this issue Dec 22, 2014
27 tasks
@MorrisJobke MorrisJobke added this to the 8.1-next milestone Dec 22, 2014
@DeepDiver1975 DeepDiver1975 modified the milestones: 8.1-current, 8.2-next Mar 2, 2015
@DeepDiver1975 DeepDiver1975 modified the milestones: 8.2-next, backlog Jul 3, 2015
@butonic
Copy link
Member

butonic commented Apr 26, 2017

@DeepDiver1975 closed with account table?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants