Hi, I create users via an external application connected to the gibbonPerson database table, it happens that when I go to register the users to the specific application I get “STAFF” instead of “Student”, as in the attached photo. How can I edit and get the right text out? In another test installation I get “Parent” instead. I need the student to come out in order to register them.
Thank you.
Please, has anyone ever encountered this problem?
Hi @infotecnica Welcome to the community and thank you for your post, my apologies for the delay in a response, as your post came in during our summer break in HK.
The admissions system is designed for the creation of students and families. It looks like you may be using the option to manually create an application form attached to an existing user, which assumes the user submitting the application is an adult (either a parent or staff member with a child). If you’re looking to create a new student not attached to an existing account in the system, I recommend using the Blank Application option.
However, it may be important to note that the application form process will create the gibbonPerson entry for the student, parents, and any other database records required for the student. So, if you are using an external process to manually add students to the gibbonPerson table, this looks like it may circumvent the application form and result in duplicate students.
Perhaps your intended use case is different than the default admissions process in Gibbon, in which case, any information you share about it may help us offer advice. Thanks!
Hello and thanks for the reply.
Basically I’m trying to match an attendance registration application via card reader. I have two possibilities to hook up to the gibbonPerson table, populating it directly from the application or reading and associating it with an existing student. I think I’ll use the second method.
Hi @infotecnica Yes, it sounds like the second approach may be better, as the application system is generally only meant to be used when first creating and accepting a student into the school.
For hooking up a card reader system to attendance, rather than writing to the gibbonPerson table, it sounds like writing to the gibbonAttendanceLog table may be helpful in this case, if your aim is to track student attendance this way. One way to do this could be to look at the current entries in that table, and then look to insert one that matches the same field set (likely using the Person context). Good luck!