Some DAM feature requests
I'm in the process of making the transition from LR to C1 Pro, but have used Aperture for most of the time in the past.
To enhance the DAM capabilities especially when preparing images for multiple stock agencies, I'd like to see the following being implemented to make hierarchical keywords more useful and flexible:
Last but not least (not directly keywords related):
Altogether it might seem like a lot but IMO should be doable without excessive effort by minor tweaking of the database model plus the corresponding UI additions and would instantly catapult C1 Pro to the very top amongst similar programs regarding asset management.
To enhance the DAM capabilities especially when preparing images for multiple stock agencies, I'd like to see the following being implemented to make hierarchical keywords more useful and flexible:
- Synonyms per each keyword which will be output when exporting (globally selectable on/off)
- Multi-lingual keywords: Synonyms tagged by languages (or in separate fields). On export, any combination of languages should be selectable to determine which keywords will be exported.
- Per each keyword it should be possible to choose if the complete path (the containing keywords and their synonyms as specified) is also exported.
Last but not least (not directly keywords related):
- User-defineable custom metadata fields (Text, Drop-down lists, numeric, boolean)
Altogether it might seem like a lot but IMO should be doable without excessive effort by minor tweaking of the database model plus the corresponding UI additions and would instantly catapult C1 Pro to the very top amongst similar programs regarding asset management.
0
-
I'm also making the move from LR.
(Sorry if this is going to be a bit databasey)
Synonyms are certainly useful, but it would be so much more powerful if these were context-aware, so specific classes of keyword could be included on specific outputs.
For example, when exporting for Instagram (probably the most commonly used output platform), it could be useful to include the tags of collaborators, whereas for my website I'd want their 'real' names. So this could involve separate taxonomy for 'people' with different attributes : name, instagram tag, website, role. The attributes to be applied on export could be managed through the process recipe.
Similarly - on a more global level - it would be nice to have (user defined) classes of keywords, which could be applied for specific output destinations - '#photoshoot' and '#studioshoot' are on most of my Instagram posts, but wouldn't necessarily be relevant on other output platforms. All this would save a lot of cut / copy / pasting.
Otherwise, I just miss stacking and ftp output ☹️0 -
After considering all aspects, I hate to say it but I will probably stay with LR for stock work (which is 90% for me) for now. Maybe I'll use C1 Pro 12 for a few RAW conversions or editing of some particularly critical images, but LR appears to be the more useful hub for now. It's far from perfect but its DAM feature set - in conjunction with 3rd party plug-ins which extend the database model - is just sufficient, while that of C1 appears to be just not quite sufficient. 0 -
GiovanniB wrote:
After considering all aspects, I hate to say it but I will probably stay with LR for stock work (which is 90% for me) for now. Maybe I'll use C1 Pro 12 for a few RAW conversions or editing of some particularly critical images, but LR appears to be the more useful hub for now. It's far from perfect but its DAM feature set - in conjunction with 3rd party plug-ins which extend the database model - is just sufficient, while that of C1 appears to be just not quite sufficient.
It could be useful to include the tags of collaborators, whereas for my website I'd want their 'real' names. So this could involve separate taxonomy for 'people' with different attributes : name, instagram tag, website, role. The attributes to be applied on export could be managed through the process recipe.
Similarly - on a more global level - it would be nice to have (user defined) classes of keywords, which could be applied for specific output destinations - '#photoshoot' and '#studioshoot' are on most of my Instagram posts, but wouldn't necessarily be relevant on other output platforms. All this would save a lot of cut / copy / pasting.0 -
For suggesting Enhancements your best option is to create a Support Case, start the Title of the case with "Enhancement Request:" and describe what you would like.
That allows the Phase development team to gather similar requests and consider them for development according to both utility and requests from users.
The way I read the requirement described here suggests that this goes well beyond the requirements of a typical RAW converter user and probably a long way in the realms of specialised library handling.
Presumably, since the word "Stock" was mentioned, you are all mainly looking at versions of finished images (in jpg, tiff or similar formats) rather than re-converting and re-releasing every time an image is requested.
If so I would assume that the need to involve C1 is somewhat peripheral to the idea of have a best in class Finished Images Library cataloguing application.
Are there no tools already out there that perform this function?0
Post is closed for comments.
Comments
4 comments