We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For landing EnoV3, it's easier to simplify the pogues2lunatic transformation. Instead of pogues2ddi (done by EnoV2) then ddi2lunatic (done by EnoV3).
The transformation becomes pogues2lunatic directly (transformation supported by EnoV3 without passing through the ddi).
The text was updated successfully, but these errors were encountered:
I think we need a PoguesMapper to do this -> https://github.com/InseeFr/Eno/tree/v3-main/eno-core/src/main/java/fr/insee/eno/core/mappers
Sorry, something went wrong.
@laurentC35 yes Pogues as input is the next planned in Eno java. Once done, we could do Pogues -> Lunatic directly.
For now this is paused, since we're thinking about doing a refresh of Pogues, which might change the model a lot.
However, to prepare for this, I'd like to introduce a "Pogues to Lunatic" endpoint in Eno web-service, which could be useful here in Pogues backend.
Merge branch 'main' into feat/#182
c0b1bb0
laurentC35
nsenave
Successfully merging a pull request may close this issue.
For landing EnoV3, it's easier to simplify the pogues2lunatic transformation.
Instead of pogues2ddi (done by EnoV2) then ddi2lunatic (done by EnoV3).
The transformation becomes pogues2lunatic directly (transformation supported by EnoV3 without passing through the ddi).
The text was updated successfully, but these errors were encountered: