TobiasNx

Nope, picaxml encoder is still a valid feature. Just the usecase is not urgent anymore.

Task: map incoming data to header order, add new row in header, if element does not exist.

It seems that this also works in the flux: https://github.com/TobiasNx/metafacture_runner_examples/blob/b94d361280f7eec816acc5e4abae8da67b7e7ae4/examples/marc21-to-edm/MARC21-EDM.flux#L18

you are right, adding the namespace within the flux could be more convenient

> It's `handle-marcxml`, not `decode-marcxml`, right ? If you want the documentation appear into the flux-commands you have to also follow https://github.com/metafacture/metafacture-core/wiki/Flux-user-guide#adding-new-commands. Your right. But I will wait until the...

@dr0i could we merge this?

With the new changes to core, we could add new releases to FLUX and FIX and also update the documentation.

Hi, when updating our annotations on our website here (http://lobid.org/resources/api), we encountered the same problem. In our case the annotations are not viewed with the extension but embedded in the...

I found this again. We cannot just transform marc21 -> marcxml or the other way around marcxml -> marc21 due to the inconsistent leader handling. We additionally need to transform...

Also docu states wrongly: https://github.com/metafacture/metafacture-core/blob/2cec78959d2c84ba6e408402680413098d9010eb/metafacture-biblio/src/main/java/org/metafacture/biblio/marc21/Marc21Encoder.java#L56-L57