Can you describe what the issue is you’re experiencing? My bulk import has been stuck in the “animal detection” stage for 3 days. I’m not sure if there’s something I’m forgetting to do.
If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
Zebra Codex should be opening up today, but it hasn’t been officially opened up yet. We have been fixing bugs and updating the servers regularly, so I am not surprised this has happened. Please delete your bulk import, and I will respond here when we are ready to open up this first Codex.
I was wondering if Zebra Codex is working now? I got an email saying it was but I just wanted to confirm since I retried the bulk import and am still having some issues.
It is ready for your use, but we have not yet shot the orientation video (likely today). Feel free to share the details of your bulk import challenges. Please share screenshots to help orient us. Please send the related spreadsheet to services@wildme.org.
My bulk import has finished detection and identification this time, however it will not allow me to confirm or manually assign most matches.
This is what happens when I try to assign annotations during the match confirmation process:
I have created a Collaboration with user “Public” for you, which represents publicly submitted data. Please try again and let me know if you hit the same error. We likely need to create more collaborations for you to access the full Princeton catalog as well.
If you hit the same error again, can you please send the link to the page you see these messages on?
Can you also please send me the link to the matching screen that led to the link above? It looks like this screen isn’t getting the data it needs. I looked through some of your most recent bulk imports, and I could not reproduce this.
Thank you! We found two bugs (DEX-1280;DEX-1281) that we are working quickly to fix. These are largely due to the fact that the legacy data from the Princeton lab is assigned to a user “Public”, which isn’t a real user and therefore cannot approve collaboration requests. So we need to account for that and let you add data to individuals from that dataset.
Hi, @ahsi !
DEX-1280 and DEX-1281 fixes have been deployed, so this shouldn’t be an issue going forward. For your current issue, the annotation has been assigned.
Do you have an edit-level collaboration with her? Check your landing page (Collaborations table) and bump up the collaboration to edit (if it isn’t already) and then please try again. Rosemary will need to confirm on her side too before you try again.
Thanks! I have requested edit access and will let you know if it works. I was wondering if I will need to request edit access with every owner of every zebra I try to match mine to?
Yes, silo security is there to respect project and collaborators’ rights to data. Edit access is needed if you have never added an Encounter to an individual before. If you have some contribution to that individual, the addition should be automatically approved.
