export doesn't distinguish a 'collections' export from a 'views' export

Bug #825311 reported by Stacey Walker
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mahara
Fix Released
Wishlist
Stacey Walker

Bug Description

Would be good if export distinguished whether a user was downloading collections or pages.

Currently, when you export a few pages as HTML you get collection information included and displayed on the index page as a standard format. This might be confusing to the user if they weren't expecting collection information as well.

I noticed this issue while trying to implement a PDF export a little better as I need the difference clear when creating a table of contents for combined page/collection exporting. :)

Changed in mahara:
importance: Undecided → Wishlist
status: New → Incomplete
status: Incomplete → Triaged
Revision history for this message
Stacey Walker (stacey) wrote :

I can also confirm that this is the same for leap2a exports.

Say I have a collection with 5 pages in it, but upon export I choose to only export one page in my leap2a package. When I import that later the collection information is recreated as well so I have a replica of the collection with the single page in it.

I think that if a user is wanting/expecting to export a single page that's all they should get and the collection information can be obtained by exporting a collection itself. Otherwise it seems slightly (not completely, but slightly) redundant having the two options at export.

Changed in mahara:
assignee: nobody → Stacey Walker (stacey)
Revision history for this message
Stacey Walker (stacey) wrote :

I am actually working on a fix for this anyway as it helps with the PDF export functionality, but would appreciate feedback/ideas if anyone has any.

Revision history for this message
François Marier (fmarier) wrote :

Good point. If you export just one view in a collection, you should ideally not get the collection info in the export.

Revision history for this message
Stacey Walker (stacey) wrote :

Awesome, good to know it's not intentional.

I've added a new const for stating that you're downloading a collection independently of the views (currently it doesn't distinguish) and I'm just looking at html export now to recognise the same difference. Leap2a afterwards.

Will try and get a patch into gerrit soon so it can be reviewed and hopefully added sooner rather than later

tags: added: collections export
Revision history for this message
Hugh Davenport (hugh-davenport) wrote :
Changed in mahara:
status: Triaged → In Progress
Changed in mahara:
milestone: none → 1.6.0
Melissa Draper (melissa)
Changed in mahara:
milestone: 1.6.0 → 1.7.0
Aaron Wells (u-aaronw)
Changed in mahara:
milestone: 1.7.0 → 1.8.0
Revision history for this message
Mahara Bot (dev-mahara) wrote : A change has been merged

Reviewed: https://reviews.mahara.org/1396
Committed: http://gitorious.org/mahara/mahara/commit/2980d23ed6b173cfed4a5c7bb096a49ada5b9e47
Submitter: Aaron Wells (<email address hidden>)
Branch: master

commit 2980d23ed6b173cfed4a5c7bb096a49ada5b9e47
Author: Stacey Walker <email address hidden>
Date: Mon Aug 15 09:56:47 2011 +0100

new const for exporting collections and views separately (bug #825311)

Change-Id: I1feebe2f977d76e0c090a725232ad936eafdd851
Signed-off-by: Stacey Walker <email address hidden>

Aaron Wells (u-aaronw)
Changed in mahara:
milestone: 1.8rc1 → 1.8.0
Aaron Wells (u-aaronw)
Changed in mahara:
milestone: 1.8.0 → 1.9.0
Revision history for this message
Aaron Wells (u-aaronw) wrote :

This one was actually released as part of 1.8.0, but we forgot to update its status.

Changed in mahara:
status: In Progress → Fix Released
milestone: 1.9.0 → 1.8.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.