FORUMS: list search recent posts

Best practices to share catalog data?

COW Forums : Square Box CatDV

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
Joe Marler
Best practices to share catalog data?
on Dec 13, 2010 at 11:45:17 pm

My team is initially planning to have two CatDV Pro licenses (stand alone, not workgroup). One will ingest and tag the material, and the other will edit. However they are geographically separated, although both have broadband internet access. Both sites will have the original full-res material on local hard disk.

What files must be transported to convey the tagged catalog data, markers, subclips and edit proxies from one site to another? How does the receiving site connect to those files?

Are there any other issues or considerations for this workflow?


Return to posts index

Rolf Howarth
Re: Best practices to share catalog data?
on Dec 14, 2010 at 8:59:31 pm

You can copy the .cdv catalog files from one machine to another, and set up equivalent file paths (Preferences > Media Search Paths > Original Media) to enable CatDV to find the file if the path is different on the two machines. The best solution of course is to use the CatDV Server, as it's designed specifically to support multi-user operation :-)



Return to posts index

bryson jones
Re: Best practices to share catalog data?
on Dec 16, 2010 at 1:16:12 am

Let me speak to the big gotcha.

First, yes, the server makes life much easier. That's all there is to it.

Now, onto the info.

The big one is that the layout doesn't travel with the catalog. Think about it... it's a big deal.

The "User Fields" are programmable and usually are kept with the production group so that when I log in my system sets up the fields and views that I need. So if I have user field #1 (USER1) as my "shoot location" and it's in the first panel of my details panel, it'll show up there, labeled as such. The server manages this so that every one's metadata maps to the same place.

If the other guy has "Shoot Date" in his rig as USER1, and it's on the third page of his layout, when I send him my catalogs and he opens them, he's going to see my "shoot locations" on his third page of details and they will be labeled "Shoot Date" because that what he calls field "USER1".

Let's say, that he now sets Shoot Location as USER5. and you call USER5 "City"

If he adds some locations to some clips and you add some locations to clips on your end and then you merge them, the data will be mixed and really jacked up in that catalog. City will mix with Shoot Location and Shoot Date and Shoot Location will get mixed and it will make a mess of your neat metadata.

Basically, you have to make sure that no one edits their settings on one side unless you both do it the same way. Add a couple more systems and a great thing that saved you time is suddenly a huge pain in the butt. You have to edit each machine's settings by hand and make sure they all match.

There's a clear path and use for both versions. CatDV, when used multi-user has a server to manage users and settings. It works like a charm when used as intended. That's the supported multi-user config.

If you use it as standalone it is a troublesome thing to run multiple CatDV seats without the server sharing catalogs. Hence the name "Standalone". One seat.

However, you can do it. You can also run naked through a cactus farm.

In both cases, be very careful. ;)

bryson

bryson "at" hidefcowboy.com

hidefcowboy.com


Return to posts index


Marvin Holdman
Re: Best practices to share catalog data?
on Dec 17, 2010 at 4:38:37 pm

Not such a huge deal actually. You can copy your preference files to move those user fields from one deployment of the client software to another. You might need to re-license it once the preference file is copied, but the setup is transportable in that manner.

We used to do this for 6 machines when we were using the Workgroup Server. A little clunky, but doable.

Marvin Holdman
Production Manager
Tourist Network
8317 Front Beach Rd, Suite 23
Panama City Beach, Fl
phone 850-234-2773 ext. 128
cell 850-585-9667
skype username - vidmarv


Return to posts index

Alex Hay
Re: Best practices to share catalog data?
on Feb 2, 2011 at 1:18:59 pm

Hi Marvin,

I was just wondering which preference files you copy across to maintain the same user metadata fields, custom views, picklists etc.

Just playing around with the Workgroup Server demo and having to generate the custom fields manually on each machine would be way to time-consuming. Seem like this is handled in the Enterprise model but I'm hoping it's at least manageable in the workgroup version!

Regards,

Alex
Firecracker Films


Return to posts index

scott tupper
Re: Best practices to share catalog data?
on May 25, 2011 at 4:10:33 pm

Can someone please answer Alex's question? I to am playing with the standalone demo and needed to transfer to a different system and would like to carry over my Details Panels.



Return to posts index


Rolf Howarth
Re: Best practices to share catalog data?
on May 25, 2011 at 4:14:45 pm

You can copy a preferences file from one machine to another but will need to re-enter your license code (from the original email) after doing so. This method is appropriate for propagating an initial setup to other machines but isn't suitable for automatically keeping preferences in sync that different users might be updating - for that you need the Enterprise server.



Return to posts index

scott tupper
Re: Best practices to share catalog data?
on May 25, 2011 at 4:53:34 pm

Exactly what we will be looking to do and will be working with Matt on that.
In the interim can you please tell me where this prefs file lives?
Thanks



Return to posts index

scott tupper
Re: Best practices to share catalog data?
on May 25, 2011 at 7:04:58 pm

Found it thanks Rolf.



Return to posts index


Matthew Stamos
Re: Best practices to share catalog data?
on May 25, 2011 at 7:27:29 pm

Just something to keep in mind with the Enterprise Server the Preferences are stored on the on the server per each group. You can load the prefs from any group you are a member of... you may also save one locally so you can work offline with a particular preference set.


Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2017 CreativeCOW.net All Rights Reserved
[TOP]