The upload process you are talking about was implemented in cpgNG. But unfortunately cpgNG is dead now.
Hi Abbas,
I think I something similar to what I am proposing a few years ago (2006?). It is one of those mass upload scripts I was considering but it was only available in Windows format. I am a Mac user so I was not able to try it, if indeed it was exactly as I wanted
I am curious: Why did cpgNG die? Is there any replacement project?
I agree that the upload process could need a re-code using an Ajax-driven interface.
I agree Joachim. I do not know much about scripting, but I use a Joomla Extension Ajax Shoutbox, and the loading is quite fast. It is being used as a chat place for a group that I helped prepare a webpage for.
But, apart from the speed of upload, streamlining of the entry of data would be even more critical. This will require separation of the common information (to be provided once for a group of photos) from the specific information (unique for each image).
Right now, this set of information is requested (one photo at a time) in the middle of the CPG upload process -- the most time-consuming process -- so that it becomes the bottleneck during the upload process.
A key aspect of my proposal above therefore (even if it is not really technical) is to remove this bottleneck in the upload process, and perform this after the upload. This step anyway should be lumped with the "Edit File" process.
Another time saver in my proposal is to have a preliminary step in the "Edit File" process -- to provide in a "single form" the common information associated with a group of photos (see above for list of these common information).
Why is this critical and a very great time saver?
Sometimes we make mistakes, or want to add more or edit the existing common information. [I do this a lot with the tags.] The amount of time spent in correcting the common mistake, adding more or editing the common information would be proportional to the number of photos that belong to a group -- consider what this process will consume for 10 photos,..., 100 photos, ..., 1,000 photos, ..., 10,000 photos, etc.; and the amount of time spent becomes staggering with more photos. Think of repeating that in case you decide to add more or edit more, for the same set of photos.
In contrast, the amount of time spent -- irregardless of the number of photos -- will be the same if the common information is provided in one single step. A simple PHP scripting would then be used to populate each photo with these common information.
The above is just for a specific group of photos. Think of hierarchical grouping of photos, and the same may be applied.
The specific information, like the title, obviously will be unique, so that such type of information must be in separate form, unique for each image.
A third key feature, is that in the Edit File process -- the common information and the specific information must always be treated separate -- so that the edit of one would not affect the other.
Cornelio