nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Duplicate Lookup IDs for Cuseum Digital Cards

Kaitlin LeRoy

We have been using Cuseum's digital card program for about a year now and have been very happy with it. Currently, I pull the membership data from a query and manually upload it to Cuseum. We did this because we were experiencing lots a duplicates and errors in the query (due to some bad data). We've cleaned this up for the most part, and I am beginning to look to fully integrating with Cuseum to make the upload process automatic.

So, my question is:

We offer some folks who specifically request it at certain levels a “Guest of" card. Example in the photo below, Gwynne McDevitt is on one card and the second card says “Guest of Gwynne McDevitt”. We do not create an additional record for the Guest of card. We simply edit the name on the card in the “Member Cards” section.

This is creating an issue for Cuseum's integration because their system will read these two records as duplicates (because they are both Gwynne McDevitt with the same Lookup ID). Other than creating a new record for the Guest (which isn't ideal), are there any other options that would solve the Lookup ID issue? Or do I need to find a way to exclude these members from my query?

cd17d478fa63d2d9c6afdd766b377f67-huge-im

Any thoughts are appreciated!

Find more posts tagged with

Comments

Emily Ferguson

Hi Kaitlin, I'd recommend changing the name format of Gwynne's card to “Gwynne McDevitt and Guest” and only issue one card. Gwynne could then use the “Share Pass” feature to email a copy of the card to their guest if needed.

Kelley Donselar

Hi Kaitlin! I agree with Emily, that using the “share pass” feature may be best. We have memberships with extra guests and since they're not named and not in Altru we explain how the “share pass” function works to members instead.

But if you're looking to generate separate “guest of” cards, here are my thoughts. Is the query you're using pulling the member name or the member card name? If you use the name(s) on the card, it might differentiate the record enough between the member and “guest of."

672a2f017a375fd7ad35f59811b52595-origina

Of course you'll want to make sure your other member records pull correctly if you change the query in this way. If you're not doing a large number of “guest of” cards, maybe it would be best to do manual uploads of just those records while using the automatic upload for your general membership base.

You may be able to work with Cuseum to use a different account “anchor” in their system. This is the information used to check records already in Cuseum to determine if a record should be updated or a new account created. If it's hitting on the lookup ID, see if it could be the card name instead. (I had to do this to resolve duplicate issues before!)

Kaitlin LeRoy

Thank you both SO much. These are great solutions and I'm running them both by my team. I think we can definitely make this work and appreciate your responses!