Project

General

Profile

Usability #2952

Repo/MyPublications: should be made sortable

Added by Anonymous over 9 years ago. Updated about 9 years ago.

Status:
Feature implemented
Priority:
Urgent
Assignee:
-
Target version:
Start date:
24/02/2011
Due date:
% Done:

0%

Estimated time:

Description

The My Publications list can be very long, so it should be possible to:
  • perform actions on multiple items (cf. also 2913)
  • sort the list on the various column headers so that a user can find what he is looking for
  • add a search function

Related issues

Related to Repository - Feature #2913: My Publications: actions on multiple objectsNew21/02/2011

Actions

History

#1

Updated by Sven Vanpoucke over 9 years ago

  • Project changed from 15 to Chamilo LCMS Connect
#2

Updated by Anonymous over 9 years ago

  • Priority changed from High to Urgent
#3

Updated by Stefaan Vanbillemont over 9 years ago

  • Project changed from Chamilo LCMS Connect to Repository
#4

Updated by Stefaan Vanbillemont over 9 years ago

  • Target version set to 2.1.0
#5

Updated by Anonymous about 9 years ago

  • Status changed from New to Rejected - Abandoned

Impossible to fix in the current code implementation.

Since the table is constructed in a weird way (not a 1-1 mapping of the database, but construction with multiple queries) you need the ID AND APPLICATION to make a remove.
On a row base these are provided and the deletion can be executed. Multiple selection: the selected ID's can be fetched but currently there is no way of getting the associated application. Even if we could get these, there is no easy way to link both ID's.

This should be handled when refactoring the entire MyPublications section and a better solution should be found.

#6

Updated by Anonymous about 9 years ago

also mentioned in #2913

#7

Updated by Anonymous about 9 years ago

The fact that something is difficult to solve, is no reason to reject a post. It should then simply be targeted to a later version.
Programmers logic should NEVER prevail. The user should be the king.

#8

Updated by Hans De Bisschop about 9 years ago

Jean-Marie Maes wrote:

The fact that something is difficult to solve, is no reason to reject a post. It should then simply be targeted to a later version.
Programmers logic should NEVER prevail. The user should be the king.

Logic by a developer is not necessarily developer logic. Just like logic by a user is not necessarily logic. Please keep things professional on the support website. That means:

  • Don't reject things because they are impossible now (just change it to version-less or a later version if available)
  • No cheap shots at developers. Users "might" be king, but mad absolute monarchs tend to be deposed
#9

Updated by Anonymous about 9 years ago

I simply rejected this issue because it is the same issue as 2913, that is linked to this one BUT still open. What use is an issue tracker if the same issue is going around multiple times? This creates the possibility that multiple developpers are working on the same issue, but a different logging of it.
Did not mean to offend anybody, nor deny the seriousness of the problem, but only tried to keep the tracker 'clean & tidy' by closing duplicates of the same issue.

#10

Updated by Hans De Bisschop about 9 years ago

Then mark it as a duplicate and close it, don't reject it. The result might be the asme, the implication if most certainly different.

#11

Updated by Hans De Bisschop about 9 years ago

  • Status changed from Rejected - Abandoned to Feature implemented
#12

Updated by Anonymous about 9 years ago

My apologies in that case, I did not find a status 'duplicate' so took the next (in my opinion) logic status in case of a duplicate that is still not solved.

Also available in: Atom PDF