hello,
it´s fabulous to have a script for exporting / importing your catalog structure, as it potentially saves a lot of work and takes away need to re-enter/-type whole keyword-hierarchies.
the most obvious use for my set-up is to use it to keep db-metadata-vocabularies in sync. this is not only good for sanity, orientation etc. but also for 'external' uses of the keyword ontologies created with PS. while I use different PS-libs for different photo-sets (again for cognitive managing but also to keep them to workable size), in the 'outside' world there is just 'the keyword' – and it helps to have them coherent there too
the problem I encounter with the export/import-script for the catalog-structure is that the import of a catalog-structure from another db seems to wipe out the existing structure of a db.
– question thus: would it be possible/feasible to get a way to use the scriper to *fuse* imported catalog-structure with existing one?
thx for considering! (and/or feedback how to achieve it with existing onboard functions)
syncing catalog ontologies btw catalogs – scripter question
Re: syncing catalog ontologies btw catalogs – scripter question
It's a script. Download the script and make changes yourself.
My hunch is to search in the code CleanupPropsInParentNotInProps remove the calls at line 206 and line 248. Haven't tested it but maybe worth a try
My hunch is to search in the code CleanupPropsInParentNotInProps remove the calls at line 206 and line 248. Haven't tested it but maybe worth a try
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: syncing catalog ontologies btw catalogs – scripter question
hey Hert,
thx for that. of course you´re right.
I guess my sub-intent was to see whether there are ppl out there that might have dealt with it; besides, me thinking it is generally a sensible way to approach DB-management, and raising that as ppl around PS seem to go for multi-DB-use often.
but I also appreciate the pointer. while I am not a coder/scripter (and probably never will be), I do often try to find my way + 'hack' things where feasible. so, I will try. and report back to the community.
best! oliver
thx for that. of course you´re right.
I guess my sub-intent was to see whether there are ppl out there that might have dealt with it; besides, me thinking it is generally a sensible way to approach DB-management, and raising that as ppl around PS seem to go for multi-DB-use often.
but I also appreciate the pointer. while I am not a coder/scripter (and probably never will be), I do often try to find my way + 'hack' things where feasible. so, I will try. and report back to the community.
best! oliver
Re: syncing catalog ontologies btw catalogs – scripter question
hey Hert + everybody interested,
I tested a little - and removing lines 176-206 + 262-70 first seemed to do the job.
– then I found that action would import only top-level category labels, but not any children (empty labels?)
– will maybe try again later fiddling with it, being layperson about scripts.
in the meantime: if anyone from the community finds an adapted script in his/her library, I am of course happy about that.
best! oliver
I tested a little - and removing lines 176-206 + 262-70 first seemed to do the job.
– then I found that action would import only top-level category labels, but not any children (empty labels?)
– will maybe try again later fiddling with it, being layperson about scripts.
in the meantime: if anyone from the community finds an adapted script in his/her library, I am of course happy about that.
best! oliver