Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dónde poner los campos que faltan para el módulo de formación #175

Closed
yajo opened this issue May 22, 2015 · 8 comments
Closed

Dónde poner los campos que faltan para el módulo de formación #175

yajo opened this issue May 22, 2015 · 8 comments

Comments

@yajo
Copy link
Member

yajo commented May 22, 2015

Siguiendo con #174, necesito añadir estos campos a res.partner:

  • % discapacidad
  • ¿Afectado por terrorismo?
  • ¿Afectado por violencia de género?
  • Categoría profesional.
  • Grupo de cotización.
  • Nivel de estudios.

¿Sabéis si se encuentra alguno de ellos en algún módulo de OCA que ya exista?

Si no, tendré que hacerlos... ¿a qué repositorios debería enviar cada uno?

@yajo yajo mentioned this issue May 22, 2015
@dreispt
Copy link
Member

dreispt commented May 26, 2015

(Sorry, it's easier for me to write in english)
We can separate what is "Personal data", going on res.partner, and "Employee data", on hr.employee. In my opinion:

Personal data:

  • % discapacidad
  • ¿Afectado por terrorismo?
  • ¿Afectado por violencia de género?
  • Nivel de estudios.

Employee data:

  • Categoría profesional.
  • Grupo de cotización.

@yajo
Copy link
Member Author

yajo commented May 26, 2015

Do you know if there is any module that links a hr.employee with a res.partner always?

@yajo
Copy link
Member Author

yajo commented May 26, 2015

Today I worked on this and realized that fields professional and contribution group are so intrinsically linked to Spanish' TGSS normative that would fit better in this repository. I still have to see about study level.

@alejandrosantana
Copy link

@dreispt I think @yajo 's case is beyond hr.employee, as he needs to use those "employee data" for partners, who are professional trainees to attend professional courses, thus he needs that info in res.partner.

Besides, hr. employee should also have those two fields and, if employee corresponds to a res.partner, info should be the same.
That is how I see it. Hope I explained well the case.

@yajo
Copy link
Member Author

yajo commented May 26, 2015

@alejandrosantana That's exactly the case. Having those fields in hr.employee could be useful for other use cases, but those fall out of the scope of #174.

@yajo
Copy link
Member Author

yajo commented May 27, 2015

I have created already all those modules, but I need OCA/partner-contact#120 merged before I can start sending PR.

@rafaelbn
Copy link
Member

rafaelbn commented Aug 3, 2015

@yajo there are more modules in this project l10n-spain which implement several new fields for a specific functionality.

In my opinion

@yajo
Copy link
Member Author

yajo commented Aug 4, 2015

For what I understand, many people need some of these fields in hr.employee, and nobody in res.partner except us, so it means all of them are specific. I'll put them all in one module, thanks everyone.

@yajo yajo closed this as completed Aug 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants