allow users to perform or suggest data administration tasks

[maxlath]

tasks that currently require admin access:

Already integrated to the client interface:

• merge entities

Not integrated to the client yet:

• change entity type
• change entity fixed entities relations (ex: the work associated to an edition, cf Different books link to the same book #90)

Those tasks could be made visible to any user activating an "expert user" flag in user preferences, and after say 10 rightfully suggested task, this could unlock admin rights for this user.

[jum-s]

Which mecanism grants a user new rights on the plateform (ie. merging entities) ?

• by autority : every an admin (or a priviledged user) can unlock new rights to users at their own discretion.
• by review : a user can suggest 10 (or x) 'to-merge' entities, then a reviewer can unlock the new right for this user.
• by cooption : when 2 (or x) priviledged users approve unlocking a right a user, it unlocks this right for the user.

My opinion is that by autority can lead to some legacy problem, and by review seems time intensive to code (create the 'to-merge' state, organise reviewing process, display users waiting list) while cooption can be a first step toward a full review process with minimal features (approve a right to one friend, approved users list for each user).
I am curious for other possibilities of linkage mecanism

[maxlath]

another option would be something like MediaWiki autoconfirmed users, that is, users that automatically earn certain rights when meeting certain criteria. The right to merge could then be attributed to every users meeting those criteria, until proven not capable of not using this right correctly.

[thewholelifetolearn]

Is there already a possibility to suggest the merge of entities through the client interface? I didn't find any button.

[maxlath]

@thewholelifetolearn at the moment, there is no simple button to do that, people have been using the signal an error form or, for those aware of it, the inv-wd-merge pad. But making it easier to signal a merge or even to let trusted user do it directly is the plan, the question is which process should be used to assert a user is trusted

[thewholelifetolearn]

Perhaps, before implementing an automatic system to "upgrade" an user, there should be a system to suggest actions to an admin.
For example, in the same way as the "Feedback" form:

• add a "delete request" form on empty work or authors. The form should be pre-filled in with the page info. The user could just add a comment.
• add a "merge request" form for authors, works, editions, series. the form should be pre-filled in with the page info but the user must add the second entity to merge with. A comment can be added too.

Thereafter, an auto user upgrade system can be created.

[maxlath]

@Alamantus inventaire/inventaire-client#182

Enable Merging Records by Users

Since Inventaire has so many duplicate records from import processes and other things, I believe that there should be a process to allow users to either merge (with lots of confirmation that they know for 100% certain the records are the same) OR make it easy to submit "merge requests" to admins in a similar way to the "Report an Error" button.

I think that having this feature or something like it available to users will help streamline the process of cleaning up the database a lot.

[jum-s]

Instead of the admin: true user doc could store a "role": "admin" or "role": "data-admin"
no implementation in the foreseeable future seem to need roles with different access level of a view (such as librarian to access professional reviews, but not personal ones).

Another thing to have in mind : differentiate this role issue from the authorization policy mainly handled by the getUserFriends and findUserGroupsCoMembers today. Like above, no need to have different roles accessing different items so far.

[alexture]

Which mecanism grants a user new rights on the plateform (ie. merging entities) ?

* _by autority_ : every an admin (or a priviledged user) can unlock new rights to users at their own discretion.

* _by review_ : a user can suggest 10 (or x) 'to-merge' entities, then a reviewer can unlock the new right for this user.

* _by cooption_ : when 2 (or x) priviledged users approve unlocking a right a user, it unlocks this right for the user.

My opinion is that by autority can lead to some legacy problem, and by review seems time intensive to code (create the 'to-merge' state, organise reviewing process, display users waiting list) while cooption can be a first step toward a full review process with minimal features (approve a right to one friend, approved users list for each user).
I am curious for other possibilities of linkage mecanism

Feels to me like review would be the safest and most comfortable for everyone 😄

[maxlath]

Status update:

• introduce a dataadmin access level and the corresponding role, granting users with that role the right to perform actions such as merging entities Roles #425
• allow users to suggest tasks (see also replace reportPossibleDuplicate email tickets by a task document in database #410)