Leslie Jo Martin
My feedback
99 results found
-
122 votes
An error occurred while saving the comment Leslie Jo Martin
supported this idea
·
-
96 votesLeslie Jo Martin
supported this idea
·
-
90 votesLeslie Jo Martin
supported this idea
·
-
162 votesLeslie Jo Martin
supported this idea
·
An error occurred while saving the comment Leslie Jo Martin
commented
Thank your Aeries Support.
-
137 votes
-
28 votesLeslie Jo Martin
supported this idea
·
-
32 votesLeslie Jo Martin
supported this idea
·
-
72 votesLeslie Jo Martin
supported this idea
·
-
74 votesLeslie Jo Martin
supported this idea
·
-
74 votesLeslie Jo Martin
supported this idea
·
-
42 votesLeslie Jo Martin
supported this idea
·
-
31 votesLeslie Jo Martin
supported this idea
·
-
132 votesLeslie Jo Martin
supported this idea
·
-
79 votesConsidered for feature modernization ·
AdminTamika Sloan
(Senior Business Analyst, Aeries Software)
responded
This idea is being planned for the Next Generation of Aeries.
Leslie Jo Martin
supported this idea
·
-
24 votesLeslie Jo Martin
supported this idea
·
-
10 votes
-
6 votes
-
78 votes
We are currently researching this topic and would like to get additional feedback on Student Alias names to help make the best development decision. If you haven’t already done so, please complete this brief survey to share your feedback:
An error occurred while saving the comment Leslie Jo Martin
commented
I am submitting an Aeries Ticket and a programming idea request. There is a conflict with Aeries and CALPADS regarding the proper usage of the alias name fields. I am hoping for the programmers at Aeries acknowledge this conflict and update the title of their alias fields to state “Legal Alias First Name,” “Legal Alias Last Name” and “Legal Alias Middle Name.”
This alias name data does get extracted into the SINF and uploaded to CALPADS. Therefore, only LEGAL previous names should be in these fields. PLUS, for privacy reasons and to adhere to recent law, we need to ensure that teachers and other staff within LEA’s do NOT see the previous legal name information, especially in the case when a name change is due to a gender change. Those student’s now have the right, by law, to insure only “need to know” staff at LEA’s can view their previous legal name information. Currently, due to the Aeries/CALADS conflict on the purpose of the use of the alias fields, LEA’s have incorrectly been putting nick names (not legal) in these alias fields and that data is seen by teachers and in some attendance and other reports in Aeries when it should not be.
-
2 votes
An error occurred while saving the comment Leslie Jo Martin
commented
I am submitting an Aeries Ticket and a programming idea request. There is a conflict with Aeries and CALPADS regarding the proper usage of the alias name fields. I am hoping for the programmers at Aeries acknowledge this conflict and update the title of their alias fields to state “Legal Alias First Name,” “Legal Alias Last Name” and “Legal Alias Middle Name.”
See attached screen shots.
This alias name data does get extracted into the SINF and uploaded to CALPADS. Therefore, only LEGAL previous names should be in these fields. PLUS, for privacy reasons and to adhere to recent law, we need to ensure that teachers and other staff within LEA’s do NOT see the previous legal name information, especially in the case when a name change is due to a gender change. Those student’s now have the right, by law, to insure only “need to know” staff at LEA’s can view their previous legal name information. Currently, due to the Aeries/CALADS conflict on the purpose of the use of the alias fields, LEA’s have incorrectly been putting nick names (not legal) in these alias fields and that data is seen by teachers and in some attendance and other reports in Aeries when it should not be.
-
12 votes
This would be a very awesome upgrade.