Hello!
I’m trying to import some user data (full data import), and Gibbon keeps skipping a third of my row, saying that they are duplicates. I’m pretty sure my data does not contain any duplicate entries. Also, there are not other entries yet in the user table with the exception of the administrator.
What criteria is Gibbon using to determine if an imported row is a duplicate?
Kindly,
Lorenz
Hi @Lori welcome to the Gibbon community.
With the full user import, it looks like the unique values expected are username and email address. Are you able to check your data in a spreadsheet program that can highlight duplicates, to ensure that you don’t have any clashes? Otherwise, feel free to share a screenshot of the error, it may indicate the row and field number that it is finding duplicates on, and this can point to the cause of the issue. Hope this helps!
@Sandra Thanks! That did the trick.
But now I have the problem that my import does not show up under People → Students. I classified them all as Student (primary role and all roles) and put the Clas of field to the current school year.
Am I missing something?
Kindly,
Lorenz
Great to hear it worked! 
Yes, there is one more step. Your students exist as users, but without an enrollment in the current school year, the system won’t see them as current students. They will still show up in places with an “All Users” option, which is useful for finding past or upcoming students. For them to show up, be sure to go to Admissions > Student Enrolment. These can also be imported. Hope this helps!
Hello @Sandra
Thanks, found it - and it works fine when entering enrolment manually. However when I try to import I keep getting there error: Each Student value should match an existing username|email in gibbonPerson.
I made a column in my csv file with the format username|email but with no effect.
What am I missing now?
Kindly,
Lorenz
Hi @Lori, sorry the details aren’t clear, the | is an “or” symbol, so it can take a column with email or username (but not both together). Hope this helps!
Hello @Sandra
Thanks, that worked out fine!
May I suggest that you update this import instructions? In Gibbon as well as in the documentation. I would assume that most schools who decide to adopt Gibbon have a pre-existing dataset that they want to be able to import. If the import process is not clear in every detail, they might gibe up and switch to another solution.
I’m happy to help with this, let me know what’s the best way !
Kindly,
Lorenz
Thanks Lorenz for your feedback. As a small team on an open source project, sometimes documentation can be our weakest area, as our capacity is quite limited and focused on maintaining the codebase. I have recently refreshed our documentation site, so if you were keen to contribute any instructions to them I’d be most appreciative. Otherwise, I’ll be sure to see about adding some more clarifications to these, as I can certainly appreciate that the import process is among the first areas that a school will need to learn when using Gibbon. Thanks!
Hi @sandra
I know about the challenges 
that’s why I offered to help. I couldn’t see if your documentation page are a wiki or not (or if so whether they allow plulc entries) but I can write down my learning in a how to form and sent them to you?
Hi Lorenz, thank you for your kind offer, yes I’d be happy to accept contributions in any form. There is an Edit button on each page of the docs, which enables using GitHub to suggest changes, however you’d also be welcome to email any documents to support@gibbonedu.org
Much appreciated! 