Move Pictures form one Album to another Move Pictures form one Album to another
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Move Pictures form one Album to another

Started by than, April 11, 2005, 08:33:31 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

than

Hey Folks,

some of my users asked me about moving Pictures form on album to another.
I think it must be possible with Coppermine. There are so much Functions implemented (it´s great) but I´ve never found the right one for moving pictures.
Can anyone help me?

Thx for answer.


P.S. Great Tool. The Best Picture Gallery I saw at the time.

Joachim Müller


michelfontaine

What does your answer mean? This is not an support question! The missing feature is very important for many users i think.

Mic.

OmegaGOD

The missing feature is not missing. You can move pictures from one album to another in CPG. This thread belongs in the CPG support section and not in reature request.

Solution: http://coppermine.sourceforge.net/manual.php#edit_pics
Under where it says album, select the album you want your picture to be moved to.


--OmegaGOD
Please do not PM me with support questions. Please read the manual and then if posting questions please place them in the proper sub-boards.

zhangweiwu

#4
I see this kind of question and answer too many times, sadly.

Too many times an user ask a developer 'why no xxx function? can we expect this funciton in next version?', 'why cannot I xxx? Will it be available if I upgrade?"
And the developer answer 'the function is already there, it's under tools menu, go to fitler submenu, find transparence tools, go to ..... and because the funciton is there, we don't have to do anything, the next version will be the same'.

The real problem, to many developers might see it as, is not the lack of function, but the lack of effective way to make easy user experience (or effective information for user to find the function). Why a user should think and analyse and discover 'move image' function is under 'album edit'? Is it an effective way to test user's IQ and if s/he is not quanlified to use coppermine, s/he should be given "NO SUPPORT" answer? When a user see an album s/he can easily image "Oh, I can move images in this album by editing this album", but very frequently the user have this wish when they see the images themselfs. There is only one thing for the developer to do to solve this RFE: to add this on 'displayimage.php' or 'editOnePic' this one single line:

<p>If you wish to move many pictures from one album to another, please try <a href="editpics.php?album=3">Edit This Album</a>.</p>

If you BS what I said, why not advertise "CopperMine is for users with IQ (the kind of IQ we defined) above 150?" This saves lots of trouble posting messages like "NO SUPPORT". You can make it simpler: "NO IQ", which is much shorter.

I maybe a bit angry today but what I said is true. I have been customer support for a long time and I had enough when I pass customer support issue to developers and they say "users should learn to ...".

Nibbler

I don't think reading the manual is too much to ask.

Tranz

Yeah, it would not look very pretty to incorporate what is already in the manual into the UI. However, 1.4 does include help icons that link to the related section of the manual.

<tongue in cheek>I do try to drop my IQ but sometimes I fail. :\'( </tongue in cheek>

Tranz

Quote from: zhangweiwu on April 24, 2005, 06:09:28 AM
I see this kind of question and answer too many times, sadly.

Too many times an user ask a developer 'why no xxx function? can we expect this funciton in next version?', 'why cannot I xxx? Will it be available if I upgrade?"
And the developer answer 'the function is already there, it's under tools menu, go to fitler submenu, find transparence tools, go to ..... and because the funciton is there, we don't have to do anything, the next version will be the same'.

The real problem, to many developers might see it as, is not the lack of function, but the lack of effective way to make easy user experience (or effective information for user to find the function). Why a user should think and analyse and discover 'move image' function is under 'album edit'? Is it an effective way to test user's IQ and if s/he is not quanlified to use coppermine, s/he should be given "NO SUPPORT" answer? When a user see an album s/he can easily image "Oh, I can move images in this album by editing this album", but very frequently the user have this wish when they see the images themselfs. There is only one thing for the developer to do to solve this RFE: to add this on 'displayimage.php' or 'editOnePic' this one single line:

<p>If you wish to move many pictures from one album to another, please try <a href="editpics.php?album=3">Edit This Album</a>.</p>

If you BS what I said, why not advertise "CopperMine is for users with IQ (the kind of IQ we defined) above 150?" This saves lots of trouble posting messages like "NO SUPPORT". You can make it simpler: "NO IQ", which is much shorter.

I maybe a bit angry today but what I said is true. I have been customer support for a long time and I had enough when I pass customer support issue to developers and they say "users should learn to ...".
It's a bit silly to criticize the high IQs of the dev team considering many scripts out there would not exist without high IQs.

And demanding those with high IQs to always relate to having lower IQs is a bit harsh. Do you demand those with lower IQs to act smarter than they are?  ??? I do try to think how average people would perceive things but to do it all the time would take time from other things. Or gasp! Maybe my brain will get used to it and I won't be smart anymore. :o :P

OmegaGOD

Quote from: zhangweiwu on April 24, 2005, 06:09:28 AM
s/he should be given "NO SUPPORT" answer?

If you BS what I said, why not advertise "CopperMine is for users with IQ (the kind of IQ we defined) above 150?" This saves lots of trouble posting messages like "NO SUPPORT". You can make it simpler: "NO IQ", which is much shorter.

The whole idea is that this sub-board is a feature request board; therefore, no support questions will be answered here. As GauGau's link, http://forum.coppermine-gallery.net/index.php?topic=15866.0 pointed out,

Quote from: TranzNDance on March 15, 2005, 07:18:19 AM
This board is for suggesting features for future versions of coppermine.

How do you decide the difference between a support and feature request?

Consider these:
- you want an answer now, rather than a future version
- the solution mostly benefits yourself, rather than most other users

If either/both are true, that means you want support, so post in the support board corresponding to the topic.

Thank you for your cooperation.

If users would either read the manual or search the support board first, they would find that 95% of their support questions would probably be answered. Also, following the rules about where to post and what to do before posting would benefit both the users and our support team.

--OmegaGOD
Please do not PM me with support questions. Please read the manual and then if posting questions please place them in the proper sub-boards.

zhangweiwu

It's a useless argument. I try to convince the project providing a short cutlink to let users find where to move more then one pictures from one album to another at once, and I consdier this a usability feature, and feeling interested to see messages follows up, and still nobody take about this particular request itself (will it be valid request?)

If people keep thinking the help for novince user is useless of your high IQ, and you consider every visitor to my gallery site needs to read manual (not only the administrator, consider on my site there are 20+ people with right to move images here and there), then I will shut up.

On the otherside, being able to design a "software for use" require even higher IQ because that request the designer try to make tasks simple.


Tranz

Look, when it comes to advanced features and power, simplicity often has to be sacrificed.

Take my car for example. It has GPS navigation, dual climate control, XM-satellite radio in addition to the regular audio stuff. If, like in a regular more simple car, there were buttons to correspond to every single command available to control the systems, my car would look like an airplane cockpit. Instead, there are a few buttons. Some for common commands, and the rest that point to menus of commands that show up on the On-Screen Display.

Without reading the manual, a person would not be able to make sense of the system. It also has voice command that controls all of the above system. That also requires reading the manual to know the commands the system would understand since it is not like a human being that could understand anything you say.

Would I prefer a more simple system? Heck no. I love my GPS navigation and XM satellite radio and climate control. I don't even mind sitting in horrible traffic sometimes because I enjoy the time in my car.

However, this car is not for everybody. It's not for those who are intimidated by technology, by those who require one-to-one ratio between buttons and commands, or who refuse to read the manual. But should the manufacturer dumb down the system and sacrifice the advanced features? I don't think so. There are plenty of other cars to choose from.

Anyway, try to consider the analogy between the gallery and the car.

Joachim Müller

Quote from: zhangweiwu on April 25, 2005, 03:58:54 PM
will it be valid request?
I guess this thread won't be marked at all (neither "invalid" nor "valid" nor "turned down"). It's some of those vague suggestions that say "improve usability". You have to understand how development works here: usually the project manager does not assign certain features to individual developers, but the developers go through the list of feature requests and then pick a feature they would like to see in the core code as well. Then the dev goes ahead and codes it.
That's all there is: those are just "requests", and "valid requests" just means that someone from the dev team thinks that the idea is not too bad and should be kept in mind. But there is no guarantee that a certain feature will ever be implemented. If you desparately need a feature, you should code it (or hire someone to do this for you). This is how we (the current dev team members) started in the first place: we contributed to the community by posting hacks or giving support, and after a while we joined the team.
Let's end this discussion now please, as this thread already shows tendencies to turn into a flame war. Let's not start an actual flame...

Joachim