Ideas para resolver el problema de guardar 1er y 2º apellido por separado

[capo]

Imagino que a quienes hayáis trabajado con CiviCRM en América Latina o España, se os habrá dado alguna vez el problema de tener que guardar por separado el 1er y 2º apellido. Soy neófito en el uso de CiviCRM así que busco, sobre todo, ideas de cómo enfrentar este problema.

Si no he entendido mal, la solución "standard" de CiviCRM es utilizar el campo inglés Surname para guardar ambos apellidos. De hecho, la traducción es "Apellidos". La pregunta es, ¿cómo habéis resuelto (o cómo resolveríais) este problema manteniendo ambos por separado? Se aceptan ideas.

Algunas ideas, para ir abriendo boca:

• Utilizar el campo 2º nombre para el 1er apellido y el campo apellido para el 2º apellido (cambiando las traducciones para que las etiquetas pongan 1er y 2º apellido, respectivamente).
• Utilizar el campo 2º nombre para el 2º apellido y el campo apellido para el 1er apellido (solución parecida a la anterior).
• Crear un campo personalizado para el 2º apellido y tratar de modificar la plantilla de contactos para que se pueda manipular este dato desde la cabecera, junto al 1er apellido (no me gusta mucho la opción de tener que desarrollar para algo tan simple).

[Upperholme]

Hola

No hablo espanol (still learning).

Why do you need to keep first and second last names separate?

[capo]

Why do you need to keep first and second last names separate?

To separate 1st and 2nd last names is a standard and normalised way to save the data. The information has more quality keeping them separated. Even in our Spanish ID's both last names are separated.

The most important reason is that if you've them separated, you can join them whenever you want. Nevertheless, if you join them, you can't allways separate them. For example, if someone has a complex last name (as is my case), you won't know how to separate it.

Example:

• Name: Carlos
• 1st Last Name: Capote
• 2nd Last Name: Pérez Andreu

If we save last names in one single field, we'd have: "Last name = Capote Pérez Andreu", so we wouldn't know where to split it.

A second reason is that, in mailings, we use to call people by their name and first last name (in my case: Carlos Capote).

A third reason, is that we're migrating from a system where we've both fields and we don't want to lost quality information during the migration.

Thanks for participating

[Upperholme]

Thanks for the additional information. If this is an issue that affects Spanish users, and therefore perhaps many Latin American users as well as European Spanish, the potential size of the affected user group is substantial. Plus of course this may well be something that affects other nations also.

I would therefore suggest that it is an issue that needs to be raised in the Internationalization and Localisation forum (http://forum.civicrm.org/index.php/board,10.0.html), where it might attract a better informed response.

[capo]

I would therefore suggest that it is an issue that needs to be raised in the Internationalization and Localisation forum (http://forum.civicrm.org/index.php/board,10.0.html), where it might attract a better informed response.

Should I post it also there? Or should I ask a moderator to move it? (Sorry for the question, I'm new here).

[Upperholme]

Maybe a moderator will spot this thread and move it. but in the meantime I would post a topic in the Localization forum referencing this thread.

[capo]

I've done it. Now it's here: http://forum.civicrm.org/index.php/topic,25482.0.html.

Thanks for your advices!

[apater]

¿Alguien ha desarrollado una solución para esto? ¿Ha añadido un campo para el segundo apellido?

El sector sin fines de lucro en América Latina (incluyendo el sur de los EE.UU.) es enorme. Creo que esto es muy, muy importante para la gente de esta zona.

[apater]

Está funcionando aquí y he creado una "Pull Request"

https://github.com/civicrm/civicrm-core/pull/1364

Sólo tener en cuenta que no soy un programador, por lo que es probable que hay un montón de errores.