Karl Lehtonen
My feedback
10 results found
-
39 votes
Karl Lehtonen
supported this idea
·
-
8 votes
Karl Lehtonen
supported this idea
·
-
6 votes
Karl Lehtonen
shared this idea
·
-
28 votes
Karl Lehtonen
supported this idea
·
-
25 votes
Karl Lehtonen
supported this idea
·
-
34 votes
Karl Lehtonen
supported this idea
·
-
35 votes
Karl Lehtonen
supported this idea
·
-
44 votes
Karl Lehtonen
supported this idea
·
-
45 votes
Karl Lehtonen
supported this idea
·
-
62 votes
Dana 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
supported this idea
·
i'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. :)