Skip navigation
This discussion is archived

Can't delete an added lookup

3235 Views 7 Replies Latest reply: Mar 5, 2010 6:45 AM by John F. Whitehead RSS
jheywood Level 1 Level 1 (0 points)
Currently Being Moderated
Mar 1, 2010 3:48 PM
A lookup was added to the "rights holder" field in the "rights" metadata group. This lookup contained all of our known rights holders. The problem is there is no longer a user editable field for that "rights holder" so we can't add new names.

I'm trying to go back to the user editable field of "rights holder" and get rid of the lookup, but i'm having no luck.

I've gone in to the "rights" metadata group, selected "Rights holder" in the "Fields - selected" window and it shows the field lookup as none and editable.

I've gone into the metadata field window in the admin panel, found rights holder and set "lookup values" to none. I save, then if I immediately reopen the admin panel for editing the metadata field, the "lookup values" read "copyright holder lookup" instead of "none". It's not saving my change.

Any idea how I can get the rights holder field back to a simple user editable field with no lookup? As it is we can't add any rights holders unless we go into admin and add them to the lookup table..

What am I missing here? We're running 1.5 having just upgraded.

I can remove the field entirely, but that doesn't really help.
  • John F. Whitehead Level 2 Level 2 (380 points)
    Currently Being Moderated
    Mar 1, 2010 6:09 PM (in response to jheywood)
    jheywood wrote:
    I've gone in to the "rights" metadata group, selected "Rights holder" in the "Fields - selected" window and it shows the field lookup as none and editable.


    This is the correct procedure. Something else must be going on.

    1. Are you sure when you go into the Rights metadata group, you are looking at PAGRP_CUST_ASSETRIGHTS and not the production equivalent?

    2. Consider upgrading to 1.5.1. I don't know if this specific issue was something that was addressed, but at the very least you'll have other bug fixes in place. You'll have to upgrade the server to 10.5.8 or 10.6.2 first.

    You could also try shutting the server down and restarting it (in the system prefs), but that shouldn't really be necessary.
    MacBook Pro, Mac OS X (10.6.2)
  • wilsonbyu Level 1 Level 1 (100 points)
    Currently Being Moderated
    Mar 4, 2010 9:38 AM (in response to jheywood)
    I have experienced some weird behavior when dealing with lookups and fields. I would suggest you delete the lookup in the administrator panel altogether. If that doesn't work (it doesn't let you). Then I would first, delete the metadata field. Then, quit FCS. Open it again, and re-add the field. That should clear any connection it had with the lookup.

    Anytime you are adding/removing/changing fields, it is best to quit the instance you are working in to see if the changes you made took correctly.
    MacBook Pro 2.33 GHz, Mac OS X (10.6.2), and Windows 7
  • wilsonbyu Level 1 Level 1 (100 points)
    Currently Being Moderated
    Mar 4, 2010 12:08 PM (in response to jheywood)
    Eh, that is tough - I didn't know you had text in that field that you needed to keep. If you delete the field, you will loose the data for sure. Short of complex watchers and/or scripting, I am not sure how you could get that data out and mapped to another field, because that is the only way you're going to be able to get rid of that lookup field.

    FCS can't delete the lookup if there is a metadata field that points to it. In the database, there is a pointer from the field to the lookup that tells the field what the data is, so in essence, if you delete the lookup field you will delete the data you currently have in that field. Thus, the only way to get away from the lookup is the method that I mentioned above. It is not without an investment of a lot of time.

    Your current solution may be the best work around.
    MacBook Pro 2.33 GHz, Mac OS X (10.6.2), and Windows 7
  • John F. Whitehead Level 2 Level 2 (380 points)
    Currently Being Moderated
    Mar 5, 2010 6:45 AM (in response to jheywood)
    It's not so strange that you can still search and that the metadata still exists - when you add a lookup it doesn't change existing metadata; it only filters what is in that field. Your field is still a Unicode String. If your string doesn't match what's in the lookup, it won't be displayed, but it won't be deleted until you choose something new from the lookup.

    I'm still confused why your Rights mdgroup is not PAGRP_CUST_ASSETRIGHTS and wondering if all your attempts at changing things are not linking to what you think they are. (I'm also still presuming you're on 1.5.1.)

    Things are definitely out of whack, but it may not be possible to troubleshoot through the admin interface. What you could do - well, maybe not recommended, but what I would do - is examine the db via the CLI, and figure out what it truly pointing to what.
    MacBook Pro, Mac OS X (10.6.2)

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.