Collect things that are still different between Catmandu and Fix/Metafacture

[TobiasNx]

We should collect things that are different between fix and catmandu and decide if we want to keep it like that or open tickets:

• Indexing of array/repeatable fields: Catmandu starts with 0, Fix starts with 1 due to JsonDecoder.
• embedded fix in catmandu commands can be separated by ;

[TobiasNx]

• when transforming to yaml from marc catmandu shows the hidden _id by default too, metafacture does not

[TobiasNx]

• YAML encoding in Catmandu ends record with ..., metafacture does not

[TobiasNx]

• Marc handling in MF and Catmandu are completly different. MF: Leader-Element, XXX+Indicies = Toplevel elements, Subfilds=> Subfields, difficulties are created by repeated subfields, Catmandu: _id, array-in-array, unclear structure) (MF has an big advantage here. MF: uses generic fix, Catmandu: uses its special Marc-Fix

[blackwinter]

when transforming to yaml from marc catmandu shows the hidden _id too, metafacture does not

It does if you tell it to: copy_field("_id", "_id") (see #84).

[TobiasNx]

when transforming to yaml from marc catmandu shows the hidden _id too, metafacture does not

It does if you tell it to: copy_field("_id", "_id") (see #84).

but not by default (should have been more specific). Catmandu see here: https://librecatproject.wordpress.com/2014/12/11/day-9-processing-marc-with-catmandu/

[TobiasNx]

do list(path:"...", "var":"...) in MF Fix the var needs to be in " in catmandu not

[TobiasNx]

substring-function does not define start and end index but start and number of signs.

[TobiasNx]

the match conditional does not work as the regexp-filter in morph. The string needs to be matching the whole pattern. The regexp-filter also matches with parts of the string.

[TobiasNx]

Fix has no morph-like filter functions that only keep values that match the condition. You need a conditional as workaround.