Shared Keyword Libraries - Backup Tip
You'll know that a catalog/session will have a keyword library associated with. These libraries are kept within the catalog /session database, thus backed up whenever the catalog/session is.
Not so with shared keyword libraries. They do not belong to a catalog/session, but lives indepently in a database file called <name>.cokeywords.db, living in (Windows) the AppData folder <user>\AppData\Local\CaptureOne\KeywordLibraries.
The backup functions in COP does not comprise this database file. Therefore, for a complete COP backup:
1. Use the backup functions inside COP to backup the catalog/session
2. Then manually backup the <name>.cokeywords.db shared keyword libraries, or setup any general backup software to do so automatically.
MLI
Not so with shared keyword libraries. They do not belong to a catalog/session, but lives indepently in a database file called <name>.cokeywords.db, living in (Windows) the AppData folder <user>\AppData\Local\CaptureOne\KeywordLibraries.
The backup functions in COP does not comprise this database file. Therefore, for a complete COP backup:
1. Use the backup functions inside COP to backup the catalog/session
2. Then manually backup the <name>.cokeywords.db shared keyword libraries, or setup any general backup software to do so automatically.
MLI
0
-
Good tip. A general backup routine is what you always should have, but it is nevertheless good to make users aware of the fact that a shared keyword library is not part of the catalog backup.
By the way, there is no session backup from within Capture One Pro.0 -
Paul_Steunebrink wrote:
By the way, there is no session backup from within Capture One Pro.
Thanks, Paul. I just took it for granted, wrongly.
MLI0 -
mli20 wrote:
Paul_Steunebrink wrote:
By the way, there is no session backup from within Capture One Pro.
Thanks, Paul. I just took it for granted, wrongly.
MLI
Well, it actually makes sense to take such feature for granted, MLI. It should have been there too. ☹️0
Post is closed for comments.
Comments
3 comments