Karl Lehtonen
My feedback
8 results found
-
5 votes
An error occurred while saving the comment Karl Lehtonen supported this idea · -
25 votesKarl Lehtonen supported this idea ·
-
30 votes
An error occurred while saving the comment Karl Lehtonen commentedwe have had so many issues with this, and found it to be a poorly implemented concept over all. would love the option in import profiles to retain existing suppression status.
Karl Lehtonen supported this idea · -
34 votesKarl Lehtonen supported this idea ·
-
32 votesKarl Lehtonen supported this idea ·
-
44 votesKarl Lehtonen supported this idea ·
-
44 votesKarl Lehtonen supported this idea ·
-
61 votesDana Moshkovits responded
Clarification was provided regarding the functionality requested – which is not to delete portfolios but rather detaching portfolios from the collection and setting them as standalone portfolios.
Re-opening the idea.An error occurred while saving the comment Karl Lehtonen commentedi'd like to suggest an approach to this idea.
if we could run a job on a portfolio managed set to disassociate members of that set from their collection, rendering those portfolios standalone - so that they can then be identifiable as standalone (eg via repository search "is standalone"), or can simply be filed into an alternate collection - certainly valuable with publishers merging, demerging and moving content rights around. again, probably only applicable to local portfolios where local staff take into account applicable parser parameters or simply use static URLs. thanks for suggesting - i would very much like to see this implemented. :)
Karl Lehtonen supported this idea ·
this would be very nice!