Split voting methods on PollUnit categories

I have 3 categories in a Photo Contest PollUnit. I want to have all the members of my club be able to make submissions, and then vote on categories A and B; but use a jury method for judging category C. How could I accomplish this without making separate PollUnits?

It’s not possible to apply different voting rules within a single photo contest.
As a workaround, you could create a landing page and link two separate contests there. We understand that a landing page is not as straightforward as running just one contest, but it can help you achieve the same goal.

I don't want a landing page. I tried it and don't like it for the following reasons:

1. No link to return to the landing page so one must hit the back button up to 4 times depending on what you did in the PollUnit.
2. Url parameter values are not saved when PollUnits are on a landing page.
3. Cannot put a password on page instead of on each PollUnit so must enter password when accessing each PollUnit.

What would work, is if I could

1. Clone the PollUnit used for submissions for all 3 categories.
2. Delete category C in original PollUnit, and use it for membership voting.
3. Delete categories A & B in the cloned PollUnit and use it for jury voting.

The only reason I cannot do this now is that submission categories cannot be edited once submissions have been added. I don't see a reason why this should not be allowed. It's not much different from deleting individual submissions, just quicker. It makes more sense to me to prevent editing the submission categories once voting has started.

OK, I will add this as a feature request to our list and keep you updated once there is progress. Since this feature would mainly enable a workaround, I’m not sure how high it will be prioritized at the moment.

As an alternative, you could create one PollUnit only for collecting submissions. Afterwards, you can download the submissions and set up two new PollUnits for the different voting processes. This way everything stays consistent with the current feature set.

Hi Markus,
You call it a workaround, but I call it a simple solution that I'm guessing would be easy to implement. I might not be the only one interested in doing this, and being able to delete submission categories up to when voting starts. This could be useful for other reasons. Since I did not get a solution, I did another workaround. I embedded both the A&B PollUnit and the C PollUnit on a page on my site. This eliminates 2 of the problems I did not like about landing pages for navigation and a password. But it's still not as intuitive and easy to use as all 3 categories in one PollUnit.

Regarding your suggestion to download the submissions and set up two new PollUnits for voting. I'd have to upload those downloaded submissions to the new PollUnits, but then they will no longer have and data with them, correct? I can't use them without that.

I really understand your point. But we need at least a way for PollUnit admins to undo a deletion. You cannot imagine how often people accidentally delete a complete PollUnit with all data, despite a warning message and confirmation, and then we need to restore it from our backup. Deleting a complete category with all its data may lead to similar challenges, so we need to be very careful here.

Please also keep in mind that you are trying to build a photo contest with a feature set we currently do not offer. Your requirements and issues come from working around this. I’ve already added your request as a feature suggestion, and we’ll see if and when we can improve this.

Regarding your last question: if you upload images to a new PollUnit, no existing data is transferred with them. So yes, you would lose the original context like votes, comments, or participant information.