-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add workflow basis to fetch HEBIS Data RPB-225 #105
Conversation
I reuse the hole transfomration, sofar no adjustments were done for specifc hebis data source. e.g. almaMmsId should be renamed hebisId
This needs to be adjusted with regard to the strapi indexing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@acka47 have a look at the files named conf/output/test-hebis-to-lobid-output-n.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@acka47 files named conf/hebisMarc2lobid-transformation/comparisonRpbRecords/rpb-hebis-records-n.json
are for only for comparison they are records from the productive rpb.
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:
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 |
"label" : "Systematik der DNB (bis 2003)", | ||
"id" : "https://bartoc.org/en/node/18497" | ||
} | ||
}, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This subject
entry is to spars wrt the lobid-resources JSON schema, see #105 (comment)
"label" : "Systematik der DNB (bis 2003)", | ||
"id" : "https://bartoc.org/en/node/18497" | ||
} | ||
}, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This subject
entry also is to sparse wrt the lobid-resources JSON schema, see #105 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same situation as above.
702074f
to
f73b85b
Compare
| batch-reset(batchsize="1") | ||
| encode-json(prettyPrinting="true") | ||
| write(FLUX_DIR + "output/test-hebis-to-lobid-output-${i}.json") | ||
; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the productive workflow @fsteeg you would need to adjust the process here.
"type" : [ "Item", "PhysicalObject" ], | ||
"callNumber" : "Mog m 7188" | ||
}, { | ||
"heldBy" : { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The structure here seems to be wrong: heldBy
is in a separate object, but should be in the object above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed this.
To merge external hebis data with strapi record for indexing
Great, this works in principle, see comment in Jira. Assigning:
|
I added a comment in 4a8c98f , but cannot see it ... has GitHUb changed its behaviour, can you see my comment? |
I don't see it. Maybe you added it to a review, but didn't submit the review? |
Found the comment and replied here: |
Now under functional review by LBZ in https://jira.hbz-nrw.de/browse/RPB-225. |
Re-requested review from @acka47 to make sure requested changes are addressed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
Reuse lobid transformation for Hebis Mapping
TODO: