Add workflow basis to fetch HEBIS Data RPB-225

[TobiasNx]

Reuse lobid transformation for Hebis Mapping

• reused almost all of the lobid transformation. Not used stuff is overhead but it makes it more easy to adjust.
• I put all maps static and test in the maps folder.

TODO:

• adjust to HEBIS and rpb specific stuff
• simple holdings are provided in 924, they are now included.
• Check: Do they provide rpb specific infos via sru? It seems not
• Introduce bash script that creates the sru query and reuses them in the flux
• This PR is depending on Update to Java 11 #129

[TobiasNx]

@fsteeg and @acka47 have a look at my transformed data from hebis including holdings from 924. This could be your basis for the strapi import.

[TobiasNx]

@acka47 have a look at the files named conf/output/test-hebis-to-lobid-output-n.json

[TobiasNx]

@acka47 files named conf/hebisMarc2lobid-transformation/comparisonRpbRecords/rpb-hebis-records-n.json are for only for comparison they are records from the productive rpb.

[acka47]

I tested the files against the JSON schema from https://github.com/hbz/lobid-resources/blob/master/src/test/resources/schemas/resource.json Overall, this looks good but there are apparently two subjects in the test files that do not get sufficient information in the resulting JSON. (I will add additional comments as pointers.) Here is the validation output:

$ sh validateJsonTestFiles.sh 
Testing version: draft
alma-fix/test-hebis-to-lobid-output-0.json passed test
alma-fix/test-hebis-to-lobid-output-1.json passed test
alma-fix/test-hebis-to-lobid-output-10.json failed test
[
  {
    instancePath: '/subject/2',
    schemaPath: 'complexSubject.json/required',
    keyword: 'required',
    params: { missingProperty: 'label' },
    message: "must have required property 'label'"
  },
  {
    instancePath: '/subject/2',
    schemaPath: 'complexSubject.json/required',
    keyword: 'required',
    params: { missingProperty: 'componentList' },
    message: "must have required property 'componentList'"
  },
  {
    instancePath: '/subject/2/type/0',
    schemaPath: 'complexSubject.json/properties/type/items/const',
    keyword: 'const',
    params: { allowedValue: 'ComplexSubject' },
    message: 'must be equal to constant'
  },
  {
    instancePath: '/subject/2',
    schemaPath: 'skosConcept.json/required',
    keyword: 'required',
    params: { missingProperty: 'source' },
    message: "must have required property 'source'"
  },
  {
    instancePath: '/subject/2',
    schemaPath: '#/properties/subject/items/anyOf',
    keyword: 'anyOf',
    params: {},
    message: 'must match a schema in anyOf'
  }
]
alma-fix/test-hebis-to-lobid-output-11.json failed test
[
  {
    instancePath: '/subject/2',
    schemaPath: 'complexSubject.json/required',
    keyword: 'required',
    params: { missingProperty: 'label' },
    message: "must have required property 'label'"
  },
  {
    instancePath: '/subject/2',
    schemaPath: 'complexSubject.json/required',
    keyword: 'required',
    params: { missingProperty: 'componentList' },
    message: "must have required property 'componentList'"
  },
  {
    instancePath: '/subject/2/type/0',
    schemaPath: 'complexSubject.json/properties/type/items/const',
    keyword: 'const',
    params: { allowedValue: 'ComplexSubject' },
    message: 'must be equal to constant'
  },
  {
    instancePath: '/subject/2',
    schemaPath: 'skosConcept.json/required',
    keyword: 'required',
    params: { missingProperty: 'source' },
    message: "must have required property 'source'"
  },
  {
    instancePath: '/subject/2',
    schemaPath: '#/properties/subject/items/anyOf',
    keyword: 'anyOf',
    params: {},
    message: 'must match a schema in anyOf'
  }
]
alma-fix/test-hebis-to-lobid-output-12.json passed test
alma-fix/test-hebis-to-lobid-output-13.json passed test
error:  /home/acka47/git/lobid-resources/src/test/resources/alma-fix/test-hebis-to-lobid-output-14.json: Unexpected end of JSON input
-e Test FAILED

We might have to add a mapping there or to ignore these subjects.

However, it would probably make sense to set up an automatic test that fetches the schema from the lobid-resources repo an validates the files against it, wouldn' it?

[acka47]

This subject entry is to spars wrt the lobid-resources JSON schema, see #105 (comment)

[acka47]

This subject entry also is to sparse wrt the lobid-resources JSON schema, see #105 (comment)

[TobiasNx]

Same situation as above.

[TobiasNx]

This looks something like a incorrect given notation a gnd subject classification: https://d-nb.info/standards/vocab/gnd/gnd-sc#19.1dp (label is: Persons associated with geography, with local and regional geography)

Interestingly there is a map for rppd in this repo:

rpb/conf/RPB-Export_HBZ_SWN.tsv

Line 37 in 7dcaf83

19.1dp Geographie, Heimat- und Länderkunde

Were the wrong label is give. Not sure why.