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

Failed to read PICA Plain format with PICA_PLAIN #481

Open
nichtich opened this issue May 29, 2024 · 1 comment
Open

Failed to read PICA Plain format with PICA_PLAIN #481

nichtich opened this issue May 29, 2024 · 1 comment
Assignees
Labels
bug partner:vzg Feature request from VZG
Milestone

Comments

@nichtich
Copy link
Collaborator

nichtich commented May 29, 2024

Setting --marcFormat PICA_PLAIN seems to be useful to validate human-readable samples of PICA+ records, but apparently the PICA serialization is not the one described at https://format.gbv.de/pica/plain.

It looks like parsing pica plain is supported but only after additional configuration with "PICA related parameters" -2 <path> and -u <char>. The default should be to parse PICA Plain as defined at https://format.gbv.de/pica/plain

@nichtich nichtich added the partner:vzg Feature request from VZG label May 29, 2024
@pkiraly pkiraly self-assigned this May 30, 2024
@pkiraly pkiraly added the bug label May 30, 2024
@pkiraly
Copy link
Owner

pkiraly commented Jun 14, 2024

I think it is not a real issue. The error described in #482 is due to a different issue. Both -2 (--picaIdField) and -u (--picaSubfieldSeparator) has default values: 003@$0 and $. You can check it with

./qa-catalogue --schema PICA --params "--marcFormat PICA_PLAIN" --input src/test/resources/pica \
  --input-dir "." --mask pica-plain.pp --output ~/temp/test-06-14 completeness

@nichtich If you still can reproduce the error, please provide some details.

@pkiraly pkiraly added this to the PICA: 1.3 milestone Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug partner:vzg Feature request from VZG
Projects
Status: 👀 In review
Development

No branches or pull requests

2 participants