- UID
- 20
- Online time
- Hours
- Posts
- Reg time
- 24-8-2017
- Last login
- 1-1-1970
|
Editado por Pedro_P en 17-9-2018 09:41 AM
Hi... There are several observations that can be made at your suggestion, which, as such, is interesting, but presents some difficulties to implement it.
In principle, the suggested search methods, in particular the search through google (although with its limitations) allows the search within the threads, users can search within the thread of requests by writing in quotation marks the "title of the request thread "and the name of the author of the book they are looking for.
The threads that contain books in response to a request made by a user, in addition to the thank you, carry a message that indicates the year/ the request number/ the number of the response of the user who shared the book. In that way it is easier to recognize when a thread is shared as a result of a previous request and also to know who originated that request.
There are several problems with the creation of individual and separate request threads within the section, in principle the duplication of requests, the risk of increasing the number of duplicate threads is greater, this would also generate a reload of work to check that each thread If the application has been written correctly, it is easier to review those details within the request thread.
Users who request a book are instructed to first use the suggested search methods to search for the book they want, unfortunately many users post their requests regardless of that prior search.
For now it is not possible to make changes to the system, because that would mean changing the code itself and that is not something that can be done overnight, in addition the system has its own limitations that hinder the rapid implementation of some changes like the ones you suggested.
Certainly, trying to make the requests method better and more manageable for users is a good purpose, but the work and time of the Moderator must also be considered. Consolidating all requests in a single thread, facilitate the work of handling requests, avoiding the flooding the section with individual requests (duplicate and/or repetitive) and scattered and allows a better management of the section as a whole.
Ideally, all users should follow the rules and recommendations indicated at the beginning of the requests thread, fortunately the vast majority do take into account these indications.
Up to now, the method of consolidating all the requests in a single thread, has shown in practice, to have more advantages than disadvantages, both for the users and for the tasks of moderation of the section. Certainly, the disadvantages should not be ignored and rather try as much as possible to mitigate or eliminate them, however, if something, despite everything, works, it is best not to touch it.
Anyway, we will include some additional indications that allow users a better and easy use of the request thread.
Thanks for sharing your ideas on this.
|
Rate
-
Number of participants 1 | Money +10 |
Collapse
Reason
|
subscraxme
| + 10 |
Thanks for taking the time to give such a detailed reply. I understand the constraints of the system, but one also need to do forward thinking. Anyways, keep this in your dev teams list of things to do and you can decide on the priority when you take up t |
View Rating Log
|