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

Rename fields in Strapi data (RPB-160) #81

Merged
merged 39 commits into from
Jun 12, 2024
Merged

Rename fields in Strapi data (RPB-160) #81

merged 39 commits into from
Jun 12, 2024

Conversation

fsteeg
Copy link
Member

@fsteeg fsteeg commented Apr 29, 2024

fsteeg added 30 commits April 29, 2024 14:26
No change in lobid output data expected after running:

`sbt "runMain rpb.ETL conf/rpb-test-titel-to-strapi.flux"`
`sbt "runMain rpb.ETL conf/rpb-test-titel-to-lobid.flux"`

Or, as a shortcut to run both:

`sbt "test-only tests.EtlTest"`
And add filter to exclude in lobid transformation if `true`

See `transformAndImportTest.sh` for testing Strapi import
Noticed while testing import for RPB-160
To `volume`, `issue`, `year`, `pages`, `alternativeNumbering`

Grouped as `bibliographicCitation` in lobid data
(Noticed while working on RPB-160)
(Is transformed to flat `note` array for lobid)
In Strapi title data; -> `subject.componentList` in lobid (RPB-160)
f01.f01_ -> volumeIn.numbering  # Zählung (Vorlage)
f01.f01s -> volumeIn.sortBy     # Zählung (Sortierform)
f01.f01u -> volumeIn.value      # Verknüpfung zur MtM (ÜO)
In Strapi independent-work data (RPB-160)
@fsteeg fsteeg changed the title WIP: Rename fields in Strapi title data (RPB-160) Rename fields in Strapi title data (RPB-160) May 15, 2024
@fsteeg fsteeg changed the title Rename fields in Strapi title data (RPB-160) Rename fields in Strapi data (RPB-160) May 15, 2024
@fsteeg fsteeg marked this pull request as ready for review May 15, 2024 16:35
@fsteeg fsteeg requested a review from acka47 May 15, 2024 16:35
Copy link
Contributor

@acka47 acka47 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my comment. But I am not actually sure whether adjustments are needed and might have misinterpreted something.

@@ -65,7 +65,7 @@
"type" : [ "Contribution" ]
}, {
"agent" : {
"id" : "https://d-nb.info/gnd/VCN 77",
"id" : "VCN 77",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the output for elasticsearch, right? It does not look correct that the id field is filled with a non-URI string. There is the same problem in conf/output/test-output-65.json.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's actually kind of a fix: if the value in the source field is not actually an ID (but a label), we no longer prepend the base URI. For consistency (to always have id and label), the label is used for the ID field. This might not be the final solution, but I think we can look into this when we tweak the web UI.

@acka47 acka47 assigned fsteeg and unassigned acka47 May 16, 2024
@fsteeg fsteeg assigned acka47 and unassigned fsteeg May 17, 2024
@acka47 acka47 self-requested a review May 21, 2024 07:19
Copy link
Contributor

@acka47 acka47 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@fsteeg fsteeg merged commit 3c342c2 into main Jun 12, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants