Release v0.6.0

[pkiraly]

The main focus of the current release is to support the basic analyses of PICA records, i.e.

• validation
• completeness
• indexing
• subject indexing
• authority names
• cataloguing history

PICA field definitions are not hardcoded as in case of MARC, but comes from external Avram schema, so the customization to a library's need is flexible. If no other schema is provided, QA catalogue uses the metadata schema of North German union catalogue, K10plus which can be downloaded from https://format.k10plus.de/avram.pl?profile=k10plus-title. The work on PICA is sponsored by Verbundzentrale (VZG) des Gemeinsamen Bibliotheksverbundes (GBV).

The release also contains other bug fixes and improvements.

The artefacts of the release are available in Maven Central as well: https://central.sonatype.dev/artifact/de.gwdg.metadataqa/metadata-qa-marc/0.6.0.

PICA related changes:

• PICA: filter out records #137 filter out records
• PICA: parsing PICA plain file #138 parsing PICA Plain file
• PICA: parsing PICA record #140 parsing PICA records
• PICA: completeness #142 completeness of PICA records
• PICA: Filter out internal fields #144 filter out internal fields
• PICA: Implement PICA Path #145 Implement PICA Path
• PICA: validate #151 validate PICA records
• PICA: ignorableFields parameter should support masking #152 ignorableFields parameter should support masking
• PICA: index with Solr #153 indexing PICA records
• PICA: subject indexing analysis #154 subject indexing analysis for PICA
• PICA: name authority analysis #155 name authority analysis
• PICA: cataloging history #161 cataloguing history
• PICA: Parsing PICA Plain with $ in field values #164 Parsing PICA Plain with $ in field values
• PICA: FRBR functions #174 FRBR functions
• PICA: add parameter to exclude issue types #187 add parameter to exclude issue types

Other changes:

• Move validators to distinct classes #188 Move validators to distinct classes
• Implement incremental timeline #128 Implement incremental timeline
• Include version specific subfields to the JSON schema representation and completeness #127 Include version specific subfields to the JSON schema representation and completeness

Many thanks for @nichtich for being an excellent committer and product owner of this release!

---

This discussion was created from the release Release v0.6.0.