bugSELF Platform - Bugs: bug #22385, The user clicking on an LO's title...


bug #22385: The user clicking on an LO's title gets to an arbitrary version, instead of being able to choose

Submitted by:  Federico Heinz <fheinz>
Submitted on:  Thu 21 Feb 2008 11:01:49 PM UTC  
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Need Info
Privacy:  Public Assigned to:  None
Open/Closed:  Open

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Sun 23 Mar 2008 01:59:09 PM UTC, comment #4:

The answer is: do NOT show the history of the document while viewing the content. We reviewed Niyam's suggestion for this, and it doesn't work.

Also, taking the user to the "latest version" when she hasn't made a choice yet is the worst possible decision. For one, because the "latest" version (I assume "latest" here is a temporal concept, since the tree-like structure of the history does not provide for any other interpretation) is the one that is least likely to have received any review... after all, it is the latest one.

We also need to make the users aware of the history feature, so they can use it correctly. Skipping the history view works against this goal.

You are correct: in order for the user to view the history, she has to go to the history view. This is correct, and intended. The history view is also the view to which the user arrives when she clicks on a title she has found using search or browse.

Federico Heinz <fheinz>
Sat 22 Mar 2008 04:01:28 PM UTC, comment #3:

I am not contesting the need for showing the versions. The point that we have to settle is whether to indicate other versions while viewing a version or not.

By searching, if the user found an object, we can make her go to the particular version, or if the user has a version in her bookshelf, she will not go to the latest.

the mechanism that we have implemented takes to the latest only in case when the user did not choose.

Since, we have removed the versions now at the bottom of the view, without going to the compare view, it is not possible for the user to know the history. best way to inform the user is to provide an indication on the view page itself.

Nagarjuna G. <nagarjun>
Project Administrator
Sat 22 Mar 2008 01:41:55 PM UTC, comment #2:

Let me clarify: there are two use cases:

1) the user clicks on an LO's title she has found by searching or browsing
2) the user clicks on an LO's title that is in her bookshelf, or included in a composite LO.

In the first case, the user has just stumbled upon the title. She still has no idea about the LO's contents beyond what the title tells her, and no idea about the document's version history. Showing her the "latest version" here has one drawback, and one impossibility. The drawback is that by choosing a version for her, we are precisely reinstating the Wikipedia problem of having one designated "front" page for the title, and changefests will ensue. The drawback is that in the SELF platform, there is no such thing as the "latest version"! So, in this case, when the user clicks on the title, she should be taken to the hostory view of the LO, not directly to its contents.

In the second case, however, someone (the user in the case of the Bookshelf, or the author of the composite LO --- which can be the same or another user) already has reviewed the change history, and latched onto a specific version of the LO, so we must take her directly to that version, and not to the history view. Both the Bookshelf and the composite LO, however, should warn the user about the presence of descendants of each LO in them, so the user can choose whether she wants to upgrade the reference to a new version, and to which.

Was this a better descri[tion?

Federico Heinz <fheinz>
Sat 22 Mar 2008 09:04:30 AM UTC, comment #1:

If I understand correctly, each time a user clicks on the lessonsview (left side pane) we are showing the latest version on the right side. Instead you want the system to show all the versions of the object, so that he can choose.

This is confusing. So far we never discussed this. If we all feel it should be done this way, then we can do that. This means a serious change in the UI design.

This situation confirms that Niyam's suggestion to show versions on the same page is more closer to what we wanted. We were working on that design, and we were asked not to show the versions on the same page.

Keeping the latest version as it, isnt it enough to show a link to the others versions of the LO at the bottom, as per Niyam's disign. Why doesn't this take care of the issue raised.

Nagarjuna G. <nagarjun>
Project Administrator
Thu 21 Feb 2008 11:01:49 PM UTC, original submission:

When a user is looking at the lessons that are present in a collection and clicks on the title of one of them, the system takes him to some version of the LO (presumably the latest?). This is not the expected behaviour: the system cannot know in advance which version the user wants to work on.

Instead, the user should be taken to the versions screen, where he can choose on which version he wants to work, or which version he wants to add to his bookshelf.

The user should only arrive to a specific version of an LO either through the bookshelf or the versions screen.

Federico Heinz <fheinz>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by nagarjun (Posted a comment)
  • -email is unavailable- added by fheinz (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-03-22 nagarjun StatusNone => Need Info

    Back to the top

    Powered by Savane 3.3