And in death, her name was incorrectly formatted as \u201cBasalduaruiz,\u201d leading a number of news organizations to replicate the error. The mistake combined her father\u2019s family name with that of her mother.<\/p>\n\n\n\n
But in the Army\u2019s eyes, that was her name; a spokesperson for the 1st Cavalry Division confirmed the name came directly from her official personnel file.<\/p>\n\n\n\n
From punch cards to press releases, the Army\u2019s personnel systems have struggled to render special characters \u2014 like the space in Basaldua Ruiz\u2019s name \u2014 for decades, mangling memories, identities and heritage in the process.<\/p>\n\n\n\n
While the Army said a recent human resources system upgrade will fix the issue moving forward, the service\u2019s record-keeping policies and database technological constraints stripped such characters and \u201cclosed up\u201d compound names. Other names were cut off. The problem disproportionately impacts Latino and Native American soldiers, whose compound surnames often include spaces.<\/p>\n\n\n\n
The repercussions aren\u2019t merely a matter of identity or honor, either. Lawmakers and the Defense Department are working through who will fix misspelled names on the Korean War Veterans Memorial\u2019s new Wall of Remembrance<\/a>, which advocates say could be more than 1,000 names. It\u2019s still not clear who will foot the bill for the errors in the $22 million wall<\/a>.<\/p>\n\n\n\n The mistakes, which echo the Army\u2019s past struggles to accurately record such names in its personnel systems, further outraged lawmakers who reviewed Military Times\u2019 findings. They emphasized the importance of getting names right and committed to solving the errors.<\/p>\n\n\n\n The surname errors for soldiers listed on the Wall of Remembrance likely emerged from policy decisions shaped by technological constraints and a high volume of deaths, according to archival documents reviewed by Military Times. Digital archivist Jefferson Bailey first posted the documents online<\/a> in a 2014 academic paper.<\/p>\n\n\n\n When World War II began, the Army manually tracked unit rosters and casualties through legions of typists, according to a November 1945<\/a> research study by the service\u2019s European theater headquarters. But as the death toll mounted, the service adopted machine-readable punch cards as a way to efficiently track each fallen soldier and notify their families.<\/p>\n\n\n\n By the time war broke out in Korea in 1950, Army casualty punch cards were down to a faulty science, including a list of guidelines<\/a> on how to input names.<\/p>\n\n\n\n The card\u2019s 18-character name field had little room to spare, so operators had strict marching orders:<\/p>\n\n\n\n By the war\u2019s end, nearly 110,000 punch cards sat in filing cabinets in the Adjutant General\u2019s Office.<\/p>\n\n\n\n Even when databases are upgraded \u2014 such as when the Army\u2019s so-called TAGOKOR casualty file was digitized in the 1960s and then reformatted by the National Archives multiple times since \u2014 the information inside them retains the constraints of its original format.<\/p>\n\n\n\n In other words, moving truncated names into a new system doesn\u2019t restore their original form.<\/p>\n\n\n\n In fact, data entry policies from the TAGOKOR records mirror the errors found in today\u2019s Korean War casualty lists, though Military Times could not independently trace the sources of the wall\u2019s list further back than the 1980s. The modern-day Defense Casualty Analysis System\u2019s historical conflict listings came from the Washington Headquarters Service\u2019s Worldwide Casualty System, but it\u2019s not clear what specific systems fed data into the Worldwide Casualty System when it emerged 40 years ago.<\/p>\n\n\n\n In 2021, Military Times was the first to report<\/a> that the Korean War Wall of Remembrance could have thousands of errors due to lingering misspelling and formatting problems. But both the Defense Department and the foundation overseeing the Wall\u2019s construction argued the law authorizing the memorial left them powerless to change the spelling of the names.<\/p>\n\n\n\n The Vietnam Veterans Memorial wall solved the name issue through sheer willpower; in his memoir, Jan Scruggs, an Army veteran who was instrumental in the Vietnam wall\u2019s creation, recounted the \u201cmajor challenge\u201d<\/a> of reformatting the names of the dead from the original list that the Pentagon provided.<\/p>\n\n\n\n Yet the long-running debate over the names on the Vietnam wall \u2014 and the process of adding new names to it since it was originally carved \u2014 led to the odd arrangement for the Korea wall\u2019s names, according to the New York Times<\/a>. The Defense Department set eligibility criteria and sent names to the Korean War Veterans Memorial Foundation, and the foundation was legally obligated to submit any requested changes to the Pentagon for approval.<\/p>\n\n\n\n Both parties deflected blame for potential name problems as the monument took form following a major donation from the South Korean government. The foundation said they had to follow the law, and DoD officials said changes to the name database needed to follow \u201cestablished\u201d bureaucratic procedures.<\/p>\n\n\n\n Navy Cmdr. Nicole Schwegman, a Pentagon spokesperson, told Military Times that the Defense Manpower Data Center list provided to the foundation was originally based on information from each of the branches.<\/p>\n\n\n\n \u201cIf the data received from the Services is missing a space, hyphen or dash in the name, we can only provide or present the data we\u2019re provided,\u201d she explained.<\/p>\n\n\n\n The foundation knew some of the names may have had errors \u2014 it submitted a list of potentially incorrect names to DoD, its director James Fisher told Texas Monthly magazine<\/a> in 2021. But because the Pentagon was the final arbiter of the list, officials there had to substantiate and approve any changes before green-lighting the final roster of the fallen.<\/p>\n\n\n\n The end result? \u201cAbout 1,000\u2033 misspelled or misformatted names were cut into stone, historian Hal Barker, who along with his brother Ted has run the Korean War Project<\/a>\u2019s online database and archive for decades, claimed in an email to Military Times. Hal cautioned that determining an exact number would require careful comparison between the final engraving list, the project\u2019s database and historical records.<\/p>\n\n\n\n For years, the Barker brothers, the foundation and the DoD have oscillated between clashing and cooperating on the subject. But the relationship permanently soured after the foundation and the Barkers couldn\u2019t reach an agreement over sharing the project\u2019s name data.<\/p>\n\n\n\n Meanwhile, members of Congress are furious about the Wall of Remembrance\u2019s errors.<\/p>\n\n\n\n In one case first detailed by the New York Times, a Native American Army corporal named Frederick Bald Eagle Bear was recorded on the Wall as \u201cEAGLE B F BALD.\u201d<\/p>\n\n\n\n In a joint letter<\/a> to Defense Secretary Lloyd Austin on March 2, four House and Senate committees covering military affairs and natural resources requested documents on the process the Pentagon used to provide names to the Department of the Interior and Korean War Veterans Memorial Foundation. The letter also demanded a list of incorrect names and the department\u2019s plan to correct the errors.<\/p>\n\n\n\n \u201cErrors of this magnitude should not have made it past the initial blueprints, much less carved into stone, and certainly not erected and unveiled to the public,\u201d the letter read. \u201cWe find these errors deeply concerning and write to seek accountability on how the Remembrance Wall\u2019s glaring flaws went unnoticed until post-construction.\u201d<\/p>\n\n\n\n The foundation did not respond to questions from Military Times before this story\u2019s publication deadline, and the DoD\u2019s comments did not address the number of incorrect names on the wall.<\/p>\n\n\n\n Yet similar errors still exist in the Army\u2019s personnel databases thanks to their programming heritage, according to Karl Anderson, the interim deputy director of enterprise modernization at Army Human Resources Command.<\/p>\n\n\n\n When the Army upgraded to electronic records in the 1960s, the systems were programmed to function much like punch cards, with many of the same restrictions. Subsequent efforts didn\u2019t break free of that format as programming languages evolved based on the punch card concept.<\/p>\n\n\n\n The Total Army Personnel-Database, which served as the Army\u2019s master personnel database from the 1980s until 2022, was written in COBOL, the world\u2019s first-ever high-level programming language that the military developed in concert with private industry beginning in 1959. COBOL also mimicked punch cards and could not handle special characters in the name field, Anderson explained.<\/p>\n\n\n\n Most often, this resulted in dual surnames being smashed together, Anderson said. That\u2019s what happened with Basaldua Ruiz.<\/p>\n\n\n\n Even though a new program capable of handling special characters and spaces \u2014 the new Integrated Pay and Personnel System-Army \u2014 recently subsumed the old database, it imported data from the existing data source. That means the name errors from the old system remain.<\/p>\n\n\n\n Anderson said the service needs soldiers\u2019 help to fix the name errors that were transferred from the old system.<\/p>\n\n\n\n \u201cI would [tell impacted soldiers] to stop and see their friendly neighborhood S1,\u201d Anderson said, referring to personnel offices by their staff abbreviation. \u201cThey can either make that edit directly, or they can submit [a] customer relations management ticket to make that happen.\u201d<\/p>\n\n\n\n The good news, Anderson said, is that \u201cthose fixes should become increasingly less necessary.\u201d New soldiers\u2019 data will be correct from day one, because the new system can accurately reflect names. Once current troops with impacted names either correct them or leave the service, the problem of misspelled and misformatted names will be permanently solved.<\/p>\n\n\n\n Anderson, also a retired National Guard lieutenant colonel, celebrated the upgrade to \u201ca more robust system that is able to capture the diversity and the heritage of our workforce and give the soldiers the kind of respect that they deserve.\u201d<\/p>\n\n\n\n \u201cBeing able to accurately reflect your name, that\u2019s kind of important,\u201d Anderson said. \u201cIt\u2019s foundational to soldiers\u2019 identity.\u201d<\/p>\n\n\n\n Echoing Anderson\u2019s reasoning, lawmakers and experts who spoke with Military Times said they were shocked and frustrated to learn that the name formatting problems persisted for so long due to legacy database restrictions.<\/p>\n\n\n\n Manuel P\u00e9rez Qui\u00f1ones, a professor of information systems at University of North Carolina at Charlotte, has written on the disconnect between dual Latino surnames and databases.<\/p>\n\n\n\n Over the years, P\u00e9rez Qui\u00f1ones has run into database troubles in civilian life when his dual surname was entered into human resources systems. He explained that most databases have data validation features, or \u201cerror checks.\u201d This is where programmers, among whom heritages with dual surnames aren\u2019t the norm, can tell the system to reject certain kinds of characters.<\/p>\n\n\n\n The solution is simple, P\u00e9rez Qui\u00f1ones argued. A space between two names should not be flagged as an error, he said.<\/p>\n\n\n\n The Air Force mandated such a change in 2021 after a Puerto Rican airman wrote a letter to senior officials<\/a> about the importance of the spaces in his last name.<\/p>\n\n\n\n For communities whose heritage includes such surnames, the stakes are higher than just a data formatting error, the professor added.<\/p>\n\n\n\n \u201cIt is part of our culture, just that simple,\u201d P\u00e9rez Qui\u00f1ones told Military Times. \u201cForcing me to change my name is a form of forced assimilation that is really not needed. But more importantly, it reflects a focus on family.\u201d<\/p>\n\n\n\n A last name \u2014 or \u201capellido\u201d \u2014 carries great importance in Latino communities, according to a McGill International Review report<\/a> by Maria Yacolca Magui\u00f1a. The author writes that \u201cfamily name\u201d is a better translation for apellido in order to better understand this common occurrence in Latino communities.<\/p>\n\n\n\n After all, Yacolca Magui\u00f1a writes, the existence of two \u201capellidos\u201d denotes the importance of both family names. Such a practice symbolizes the union between two bloodlines.<\/p>\n\n\n\n P\u00e9rez Qui\u00f1ones agreed.<\/p>\n\n\n\n \u201c[The plural apellido] reinforces that the family is a union of two individuals and puts the focus on the kids, not the parents,\u201d he said, describing the practice as \u201cvery common.\u201d<\/p>\n\n\n\n Yacolca Magui\u00f1a offered an example.<\/p>\n\n\n\n If Mar\u00eda Garc\u00eda Morales and Miguel Gonz\u00e1les Hern\u00e1ndez have a child named Valeria, the child\u2019s birth certificate would read Valeria Gonz\u00e1les Garc\u00eda. The first surname is the father\u2019s family name, and the second is that of the mother.<\/p>\n\n\n\n For Rep. Gabe Vasquez, D-N.M., there is importance and meaning in a last name. He echoed P\u00e9rez Qui\u00f1ones\u2019 sentiments in an email to Military Times, saying dual surnames in Latino communities honor the lineage of both parents.<\/p>\n\n\n\n \u201cWhen your heritage, culture and language are not the norm, these mistakes will continue to happen because those with authority lack the context and awareness to look for errors when reviewing official documents,\u201d Vasquez said. \u201cAs one of the few Latinos on the committee, this weighs heavy on me for our servicemembers and veterans.\u201d<\/p>\n\n\n\n Vasquez, who is one of five Latinos on the House Armed Services Committee, said he has faced trouble with his own name being misspelled \u2014 or mistaken for another name altogether.<\/p>\n\n\n\n At a time when military services face a recruiting crisis, Vasquez noted, the services should promote \u201cattention to identity\u201d to make service members from a variety of backgrounds feel welcomed in the armed forces.<\/p>\n\n\n\n All services \u2014 with the exception of the Space Force and Marine Corps \u2014 missed their recruiting marks for fiscal year 2022. The Army in particular missed its recruiting goal by 15,000 soldiers<\/a> last year \u2014 and anticipates it will fall short of its 2023 goal<\/a> by 10,000 soldiers<\/p>\n\n\n\n Rep. Tony Gonzales, R-Texas, a retired master chief petty officer in the Navy, told Military Times in a statement that troops deserve to have their service properly memorialized.<\/p>\n\n\n\n \u201cI completely support the bipartisan, bicameral effort to investigate why thousands of soldiers have had their sense of identity and heritage misconstrued,\u201d Gonzales said, noting that the errors disproportionately impact \u201cminority veterans.\u201d<\/p>\n\n\n\n \u201cI hope that the investigation gets to the root of how and why these inexcusable errors occurred and that the names of each soldier affected are corrected,\u201d he added.<\/p>\n\n\n\n Rep. Ruben Gallego, D-Ariz., struck a similar note as Gonzales, his sea service colleague, in a statement to Military Times. The Marine Corps veteran was blunt.<\/p>\n\n\n\n \u201cDoD needs to own its mistake and correct the issue with its databases,\u201d Gallego said.<\/p>\n\n\n\n Yet the department took three months to respond to lawmakers\u2019 concerns about the problems with the Korean War wall, amid pressure from policymakers, advocates and allies alike. That included South Korea\u2019s veterans ministry, which vowed in January to fix misspelled and missing names on the new wall.<\/p>\n\n\n\n The Pentagon\u2019s response came via a June 2 briefing to committee staff members, according to a defense official and House Natural Resources Committee Communications Director Rebekah Hoshiko.<\/p>\n\n\n\n It\u2019s not clear what Pentagon officials told staffers in that meeting, but Hoshiko previously told Military Times that if the military shook off oversight from Congress, a \u201clegislative solution\u201d could be on the table.<\/p>\n\n\n\n In the briefing\u2019s wake, Hoshiko added that the memorial\u2019s name problem \u201ccontinues to be a concern for the committee and we will remain engaged until all issues with the wall are fixed.\u201d<\/p>\n\n\n\n And members are signaling their willingness to pursue such a solution, if necessary.<\/p>\n\n\n\n Vasquez, the New Mexico lawmaker, committed to \u201cworking to correct the historical databases.\u201d<\/p>\n\n\n\n At least one member of the upper chamber is ready to take action as well. Sen. Tammy Duckworth, D-Ill., told Military Times that she\u2019ll throw her weight behind \u201cthe best and fastest way\u201d to correct the errors.<\/p>\n\n\n\n Some advocates \u2014 such as Noem\u00ed Figueroa Soulet, who wrote and directed a 2007 documentary on Puerto Rico\u2019s 65th Infantry Regiment during the Korean War \u2014 remain frustrated that it\u2019s come to this, though.<\/p>\n\n\n\n When Figueroa Soulet learned of the formatting problems that would disproportionately impact Puerto Rican dead, she contacted the Korean War Veterans Memorial Foundation and the Defense Department in an effort to fix the names.<\/p>\n\n\n\n \u201cThey were given an opportunity to get it right from the beginning,\u201d she said in a phone interview with Military Times. \u201cSo it\u2019s really shameful that they now have to spend money to fix what they were told they should fix from the beginning. It\u2019s ridiculous.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":" The Army’s new personnel system can correctly render Latino names, but that won’t undo decades of damage.<\/p>\n","protected":false},"author":7,"featured_media":87521,"comment_status":"open","ping_status":"open","sticky":false,"template":"single-post-featured-layout","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","_yoast_wpseo_canonical":"","_acf":"","_yoast_wpseo_primary_category":88,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","_smg_distribution_targets":[]},"categories":[29,15,88],"tags":[],"coauthors":[3456,3484],"class_list":["post-80796","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-home","category-news","category-your-military"],"acf":{"subheadline":"","legacy_arc_id":"KEMBZQGTBVB4VGBPVEK6CDJCNI","arc_canonical_url":"\/news\/your-army\/2023\/06\/22\/how-old-army-admin-systems-mangled-the-names-of-fallen-latino-soldiers\/","remove_feature_photo":false,"is_sponsored":false,"subtype":"featured-layout","redirect_url":"","disable_inline_ads":false,"native_logo_pretext":"Presented By:"},"yoast_head":"\n\u2018Close up\u2019 hyphenated names<\/h2>\n\n\n\n
![\"\"](\"\/wp-content\/uploads\/2026\/08\/52908032865_76034a3eda_o.jpg.jpg\")
![\"\"](\"\/wp-content\/uploads\/2026\/08\/Screen-Shot-2023-06-22-at-11.24.49-AM.png.png\")
![\""Eagle"](\"\/wp-content\/uploads\/2026\/08\/Eagle-Solo-Nameplate.jpg.jpg\")
New system, old data<\/h2>\n\n\n\n
![\"\"](\"\/wp-content\/uploads\/2026\/08\/IPPS-A.jpg.jpg\")
\u2018Forced assimilation\u2019<\/h2>\n\n\n\n
![\"\"](\"\/wp-content\/uploads\/2026\/08\/6659971.jpg.jpg\")
![\"\"](\"\/wp-content\/uploads\/2026\/08\/GettyImages-1442615273.jpg.jpg\")
An error-riddled remembrance \u2014 still<\/h2>\n\n\n\n
![\"One](\"\/wp-content\/uploads\/2026\/08\/Soldier-WashMon-XLow.jpg.jpg\")