Catalog sets from Folder hierarchy
I'm quite new to Media Pro, so maybe I'm missing something. At the moment I manage my photo's collection with a directory structure (over 200 folders). I can access a specific collection with the catalog folders panel, but I also would like to (automatically) generate the Catalog Sets on basis of the directory structure. As far I know this isn't possible (yet). There is a script to generate Keywords from folders, but not a script for generating Catalog Sets.
Could somebody help me?
Could somebody help me?
0
-
I have the same issue. I'm finding there are only four Category Fields that allow me to "nest" subcategories. They are Cataloged Sets, Date Finder, Place Finder and Hierarchical Keywords . "Category", "Events" and of all things "People" do not allow "nesting". I can't nest "Family" under "People"? HuH? Nesting under "People" and the other two categories are VERY BASIC CATALOGING" requirements. Ha! Maybe they ran out of development money? 😂
Solution: I think Phase One should expand the nesting function to all three Category Fields above. Then the need for the obscure Category Field called "Catalog Sets" would virtually disappear (or just be used as an Exception Field for cataloging stuff that didn't fit anywhere else or for those photographers that already a bunch of Catalog Sets).0 -
[quote="NN635867731068942687UL" wrote:
Solution: I think Phase One should expand the nesting function to all three Category Fields above. Then the need for the obscure Category Field called "Catalog Sets" would virtually disappear (or just be used as an Exception Field for cataloging stuff that didn't fit anywhere else or for those photographers that already a bunch of Catalog Sets).
If we introduced nesting of the People field and the Events field then we would break with the common standards that most DAM programs use to handle such information - that would mean that if you were able to write hierarchies like Family>Inlaws, and Family>My Sister for instance, then when you opened that image in Bridge or Photo Mechanic or the likes, then you would not be able to search for these tags, they would not be readable by 3rd party programs. As it is now, the People field and the Events field follows IPTC-Extension spec to maximise interoperability.
Personally, I would nest Catalog Sets under Hierarchical Keywords. The reason is that Catalog Sets is a concept that is proprietary to Expression Media and Media Pro, so also here you cant be guaranteed that if you use Catalog Set tags on your images, that 3rd party programs will be able to read them. But if you put them inside Hierarchical Keywords, you are pretty sure that most 3rd party programs will, because most programs follow the <lightroom:hierarchicalSubject> format to make such information interoperable.[quote="NNN635737679259449027" wrote:
There is a script to generate Keywords from folders, but not a script for generating Catalog Sets.
Could somebody help me?
The scripting part of Media Pro is a way for super users to customise Media Pro to fit their own needs. I do not know where the community of Media Pro scripters are to be found, but I have noticed a user here called Daniel2 who has helped other users before, try to get in contact with him.0 -
Hi all,
Although I do not see the utility, it is possible to create sets from folders hierarchy.
You should specify if the hierarchy must be complete (from the root of volume) or partial and in this case what is the criteria to choice of departure.
I am currently very busy elsewhere, then wait a few days before delivery. 😉0 -
Searching the web indicates that there is some bug all the way back from iView days related to the creation of Catalog Sets. At lest for VB scripts on Windows platform. Not even the Media Pro default scripts "Copy from*.vbs" copy the Catalog Sets information to the target. 0 -
The scripting is such that leaving from the sale of iView to Microsoft in 2006.
Regarding the sets Yan did not have time to fix every bug before the sale.
Since nothing has changed.
The creation of sets by Applescript is complex but works.
However, obtaining the relationship between sets and items remains buggy.
I have no experience about VB and Javascript under windows.0 -
Et voila !
Sets_from_Paths.zip (16 kB)0 -
Well done Daniel. I wish I had a mac... 0 -
Pah
Thanks for your response. Complying with standards for maximum interoperability is important. So that's a good reason not to allow nesting under people etc. So now I know why but I'd like to carry it one step further. Since I don't use Bridge or the other program you mentioned. I don't know how a Bridge user would interact with a Media Pro Catalog (or a subset of a catalog) that I sent them with hierarchical keywords attached. I assume they would just "keyword search". But how would they know what keywords to search on? Would I have to send them an e-mail or text document with a list of keywords. Or would Bridge automatically display the keywords that I used?
Interoperability in the consumer sector is a low priority.... Probably higher in the business sector. That being said maybe Media Pro could allow nesting under "People" and "Categories" under special circumstances. Set on/off flags in an Options Section. Before using this Option Section there would be a disclaimer that nested categories in "other than Hierarchical Keywords" may not be be able to read by other media processing software (i.e. Bridge). If your application calls for interoperability, don't turn this feature on and concentrate on a robust keyword strategy". Now all us consumer guys can "nest away"! Oh, by the way, Cumulus arguably the worlds leader in Cataloging Software allows nesting "ANYWHERE". Don't cripple the great function of Media Pro just for commercial interoperability. Let us decide how to use it.0 -
Consumers and business users have one thing in common: they want to protect all the work they input into a digital asset management program. By entering and storing data into standardised fields your information can travel with the assets. You may not want to share metadata with other people however you will want the option to move your information from Media Pro to another DAM, maybe Cumulus?
Case in point, in the mid-ninites I wanted to migrate from Extensis Portfolio because they said they would never support camera raw formats (which they did ten years later!). I had several years of metadata carefully entered in Portfolio. I had to redo the info and I can tell you to this day I've yet to catch up with that data re-entry.
Sets is where hierarchical metadata should be used. When hierarchical keywords were introduced in Expression Media, Microsoft had issues about privacy and standards. They're workaround was to use the Adobe XMP namespace (used by Lightroom) for hierarchical keywords *and* the the legacy flat keyword. To this day it can cause issues with double entry of keywords and keywords losing their hierarchical position.0 -
[quote="NN635867731068942687UL" wrote:
Cumulus arguably the worlds leader in Cataloging Software allows nesting "ANYWHERE". Don't cripple the great function of Media Pro just for commercial interoperability. Let us decide how to use it.[quote="roberte" wrote:
Sets is where hierarchical metadata should be used. When hierarchical keywords were introduced in Expression Media, Microsoft had issues about privacy and standards. They're workaround was to use the Adobe XMP namespace (used by Lightroom) for hierarchical keywords *and* the the legacy flat keyword. To this day it can cause issues with double entry of keywords and keywords losing their hierarchical position.
Thanks for the comments. It's a challenge between increasing interoperability at the cost of reducing functionality, or increasing functionality at the cost of vendor lockin where users arent able to easily migrate their data with other programs. I'll forward it to the product manager.0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare