Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Deleting auto metadata suggestion errors

Kommentare

8 Kommentare

  • Eric Valk
    Go to the ~/Library folder and with Capture One NOT running rename the Capture One Preferences File to something like com.phaseone.captureone11_old.plist1. The intent of the change is that you can find it, and CaptureOne cannot recognise it.

    For detailed instructions see post #5 of

    That will remove the autofill data, but it may also remove other preferences you don't want removed. Depends on your workflow. If too many other preferences are removed for your liking, delete the new preferences file, and rename the old file back to com.phaseone.captureone11.plist
    0
  • George Weeks
    Eric, it appears that the plist is re-built from information held in the database and/or in the program code itself since it is re-constructed if it's missing. Instead of removing the plist file would it be reasonable to edit the metadata in the appropriate section of the plist file. For example:

    <key>contact_city_METADATA_COMPLETIONS</key>
    <array>
    <string>St. Andre</string>
    <string>St Andre</string>
    </array>


    becomes

    <key>contact_city_METADATA_COMPLETIONS</key>
    <array>
    <string>St Andre</string>
    </array>

    I tried this using a test catalog and it seems to work as I would expect although the change did not take effect until the second time C1 was started.

    Clive, if you try this on an important catalog I suggest making a back-up of your catalog and plist files in case there are unexpected effects.
    0
  • George Weeks
    Clive,
    Following on my previous reply...

    The "Reset Metadata Completions" item in the "Metadata ..." menu will remove all text completion entries from the plist file. So that would work if you don't mind re-typeing every metadata entry the first time as you need them. Might be a bit drastic if there are only a few that you want to get rid of, and could result in introducing new errors.

    Regarding keywords:
    If you right click on a keyword in the keyword list in the metadata tab you will get a context menu containing Rename Keyword and Delete Keyword.
    0
  • Permanently deleted user
    Thank you for the prompt replies, much appreciated. A simple fix and one I should have tried prior to posting. I shut down Capture One, renamed my Preference file, opened up Capture One and no more auto fill. I am travelling and using a temporary catalog anyway so even if there are (none I can see yet) other unwelcome consequences from creating a new preference file it will be easy to fix.

    Thank you once again.
    0
  • OddS.
    [quote="GeorgeWeeks" wrote:
    ...it appears that the plist is re-built from information held in the database


    Just out of curiosity -- I wonder if keywords in image files and/or sidecar files may be additional source(s) of keywords to be re-built if preference "Auto Sync sidecar XMP" is set to Load or Full Sync, or if the user manually performs a Reload Metadata.
    0
  • George Weeks
    OddS,
    If by "keywords to be re-built" you are referring to the Metadata Text Completions that appear when typing metadata entries I think the answer is no. Loading metadata using auto-load, auto-sync, or manual reload does not create new text completion entries. The text completion entries are created only if they are typed into to metadata fields (based on my testing).
    0
  • OddS.
    [quote="GeorgeWeeks" wrote:
    OddS,
    If by "keywords to be re-built" you are referring to the Metadata Text Completions...


    Sorry for creating confusion here. To me, keywords as such are not text completions, keywords live in image or sidecar files or in a database with a strong binding to a specific image. It may not be the case for C1, but keywords harvested from said files may well end up in a text completion arrangement.
    0
  • George Weeks
    Clive: Regarding the keywords

    There are two locations that I know of for keywords. One is the keyword library file and the other is a table in the catalog file. The keyword library file can be reconstructed by exporting it as a text file, modifying the exported text file, deleting the list of library keywords from it's toolbar ... menu, then importing the text file from the "Keyword Library" toolbar.

    If the unwanted keywords appear in multiple sessions or catalogs, or in a new catalog then they might be present in your Keyword Library database file. That file is separate from the "Catalog Keywords" table that gets created inside the main catalog database when keywords are added to an image.

    The Keyword Library list will appear below the "Catalog Keywords" list in the Metadata tool tab.

    If the Keyword Library file is the problem you might be able to clean it up as follows:

    1. Export the Keyword Library as a text file (click on the ... on the Keyword Library toolbar)
    2. Use a text editor to search for the unwanted keywords in the text file and delete them if found.
    3. Save the modified text file.
    4. Delete the Keyword Library file using the ... menu on the toolbar adjacent to the Library name. The Library list and the Library toolbar will disappear.
    5. Now, carefully select the ... menu on the "Keyword Library" toolbar near the top of the tool tab. Be sure not to select the "Catalog Keywords" toolbar.
    6. From the context menu select "Create Keyword Library" then "From Keyword Text File".
    7. Select the modified text file and it will be loaded as a Keyword Library. This will re-create the keyword library database with the changes you made in the text file.
    8. Check to see if the unwanted keywords are gone.

    If you want to try this I would suggest creating a new empty catalog. That will avoid any error that might be made in selecting from the ... menus. Since the Keyword Library is common to all catalogs and sessions the result will be the same as using a production catalog or session. Import one or two image files to allow testing the keyword auto-completion feature.

    If the unwanted keywords were in the keyword library database they should now be gone. If they are still present in your production catalog or sessions then there might be a problem in the keyword table in the catalog or session database and resolving that will probably require technical support from Phase One.
    0

Post ist für Kommentare geschlossen.