Ticket #1800 (assigned defect)

Opened 4 months ago

Last modified 1 month ago

Problems with downloaded collection

Reported by: pjotr Assigned to: pjotr (accepted)
Priority: waiting Milestone:
Component: generic Version:
Keywords: Cc:
Time spent: Time remaining:
Time planned:

Description

I've downloaded the Collection from lemill.net and there seem to be some problems with it:

1. All links images for resources that have the default_SOMETHING.png are nit there, as these files are not added into the ZIP.

2. There are no links to /content section materials in collection. This might be because of the change in the structure (subsections). So these links should be made to work.

3. Do we change the structure of the collection ZIP to behave according to the new structure >>> add all the subsections there and mirror the new structure of LeMill /content section?

Change History

11/10/08 11:53:23 changed by pjotr

  • owner changed from anonymous to pjotr.
  • status changed from new to assigned.

11/10/08 14:54:46 changed by pjotr

(In [2684]) References #1800, this is starting to look better now, but still not there yet

11/10/08 15:13:44 changed by pjotr

A few more problematic places have been found while exploring the Collection download architecture.

4. It looks like most of the internal links get exterminated, and only shallow <a> text </a> elements are left. This should be changed, as some of these links might be needed.

5. (MIGHT NOT BE REALLY IMPORTANT) In addition to that it might be reasonable to switch any empty <a> tags with something else.

6. From now on we also show these collections that are added to that collection there, but it looks like these are just left alone at the moment. Something needs to be done with these.

6.1 (SIMPLE SOLUTION) We just ignore them and either exterminate that block from the page HTML or just set a class, that will get that one hidden (display:none >>> might just be what we need).

6.2 (NOT A SIMPLE SOLUTION) We somehow try to integrate these collections into the downloaded structure. But this will require some solution on "What is the better way to do that". NB! Try not to forget the situation >>> 1. Current collection has some collections >>> 2. At least one of these collections has the current collection in collections >>> Now this one can get us into a non-stop cycle of archive generation.

Summary >>> 4 and 5 can be easy to deal with (5 can be even ignored at all). 6 might turn out to be pretty tough, and we need to discuss it before making any progress in that direction.

12/02/08 12:05:35 changed by pjotr

  • priority changed from major to waiting.

Downloaded collections should now have most of the problems described here fixed.

As for the number issue number 6. These collections that are inside a collections are just set invisible. If there will be any good solution on how to deal with these - it might be implemented later.

Setting ticket to waiting. If no solution will be proposed - I will close the ticket in a few weeks.