Hi,
I am trying to understanding the difference between Portfolios and normal Catalog labels, but am not seeing anything stand out.
1. If I created a "Projects" label and had sub-labels under it for various projects where images where used, is this essentially equivalent to a portfolio?
2. Is the main advantage of a portfolio that portfolio names are not treated as keywords (i.e. they do not get synced as meta-data)?
If anyone is leveraging Portfolios the way they are designed to be used, please share a workflow example.
Thanks
Difference between a Portfolio and Catalog Label
Re: Difference between a Portfolio and Catalog Label
Hi
I use Portfolios to "collect" images for publishing to our family web site.
The hierarchy of the portfolio is like the structure of the web site, and the images are added based on ratings but also "just because" we want to put them up.
Also the Highest Level of the portfolios are YEAR - whereas the Highest Level of my Categories are TYPE (e.g Birthdays) with years under theme (Birthdays->2012->Mike's Birthday)
I sort of use portfolios as a "final" bucket to throw the images into after I have geo tagged, face tagged, labeled, rated, colored, deleted, edited, etc...
Hope that helps
MikeP
I use Portfolios to "collect" images for publishing to our family web site.
The hierarchy of the portfolio is like the structure of the web site, and the images are added based on ratings but also "just because" we want to put them up.
Also the Highest Level of the portfolios are YEAR - whereas the Highest Level of my Categories are TYPE (e.g Birthdays) with years under theme (Birthdays->2012->Mike's Birthday)
I sort of use portfolios as a "final" bucket to throw the images into after I have geo tagged, face tagged, labeled, rated, colored, deleted, edited, etc...
Hope that helps
MikeP
Re: Difference between a Portfolio and Catalog Label
In idi I use (used to use 
) portfolios in a similar way to MikeP. I used them, quite literally, as a portfolio - to hold the photos that I want to show to others/look back on as a photo album/publish to the web/make a photobook out of. So only the best pictures go in the portfolio, and with only the best one selected from any "near-duplicates" (the curse of the digital age - for me at least - more self-discipline needed on the shutter button!)
My portfolios generally have a similar structure to my catalog labels. So I have one top level portfolio folder for holidays, one for weekends away with a group of friends over many years, one for family events, etc. Within these is a folder per event. This pretty much corresponds to my "events" folder under catalog labels, though not every event label has a portfolio equivalent, and my event labels tend to be much finer grained (for example I might break a holiday down into days or sub-events but within the portfolio I wish all the images to be viewed as a group)
The images in the portfolios
- I keep an offsite copy of;
- are used to generate web sites using idi templates or
- are used for bulk upload to a photo-sharing site or
- are used to make a CD for subsequent printing at a shop that has printing facilities or
- are used to order a photobook
Hope this helps. Probably all a bit redundant now wrt idi but I think the workflow principles are sound. But I could probably achieve the same thing with catalog labels. IIRC the portfolio labels aren't written to the file like the catalog labels are though I may have misremembered that.
) portfolios in a similar way to MikeP. I used them, quite literally, as a portfolio - to hold the photos that I want to show to others/look back on as a photo album/publish to the web/make a photobook out of. So only the best pictures go in the portfolio, and with only the best one selected from any "near-duplicates" (the curse of the digital age - for me at least - more self-discipline needed on the shutter button!)My portfolios generally have a similar structure to my catalog labels. So I have one top level portfolio folder for holidays, one for weekends away with a group of friends over many years, one for family events, etc. Within these is a folder per event. This pretty much corresponds to my "events" folder under catalog labels, though not every event label has a portfolio equivalent, and my event labels tend to be much finer grained (for example I might break a holiday down into days or sub-events but within the portfolio I wish all the images to be viewed as a group)
The images in the portfolios
- I keep an offsite copy of;
- are used to generate web sites using idi templates or
- are used for bulk upload to a photo-sharing site or
- are used to make a CD for subsequent printing at a shop that has printing facilities or
- are used to order a photobook
Hope this helps. Probably all a bit redundant now wrt idi but I think the workflow principles are sound. But I could probably achieve the same thing with catalog labels. IIRC the portfolio labels aren't written to the file like the catalog labels are though I may have misremembered that.
Re: Difference between a Portfolio and Catalog Label
This is all identical in PSU, so your information is very up-to-date. The only difference would be that in a PSU you'd typically use a Photo Sharing site or use a 3rd party tool to generate HTML pages for your photos.snowman1 wrote:Probably all a bit redundant now wrt idi but I think the workflow principles are sound.
Hert
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: Difference between a Portfolio and Catalog Label
Except its a mission get the images into the portfoliosThis is all identical in PSU
Re: Difference between a Portfolio and Catalog Label
I would collect images in the Image Basket (Shift+B) then drag/drop those to a portfolio or cut/paste to a portfolio.mphillips wrote:Except its a mission get the images into the portfolios
Hert
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: Difference between a Portfolio and Catalog Label
I confess I never found my "perfect" way!
- Sometimes I do it like Hert says; one-click so that's nice
- sometimes I move all the decent-rated images (say 3* plus) and then go into the portfolio and delete the ones I didn't want (such as near-duplicates); this is ok as you've quickly removed the non-starters and can see what's left and pare them down to sub-set you're pleased with; but the deletion is a bit clunky.
- sometimes I'd select the ones I wanted by either "hearting" them, or by using a colour flag (all effectively one-click operations) and transfer those. The advantage of this over shift-B is that you can see an overview of what thumbs you've chosen and easily pick up if you have too many similar ones etc; however it does require that you aren't using the heart or any of the colours for anything else.
All these approaches work reasonably well.
If using shift-b or heartr/colour then it's a good idea to filter your thumbs first so you only see the good ones (say 3* plus)
- Sometimes I do it like Hert says; one-click so that's nice
- sometimes I move all the decent-rated images (say 3* plus) and then go into the portfolio and delete the ones I didn't want (such as near-duplicates); this is ok as you've quickly removed the non-starters and can see what's left and pare them down to sub-set you're pleased with; but the deletion is a bit clunky.
- sometimes I'd select the ones I wanted by either "hearting" them, or by using a colour flag (all effectively one-click operations) and transfer those. The advantage of this over shift-B is that you can see an overview of what thumbs you've chosen and easily pick up if you have too many similar ones etc; however it does require that you aren't using the heart or any of the colours for anything else.
All these approaches work reasonably well.
If using shift-b or heartr/colour then it's a good idea to filter your thumbs first so you only see the good ones (say 3* plus)