Split up transformation to strapi and lobid data #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Ok for now but we will have to align it with the data the Strapi API will serve in the end. (to do: create content types, add example titles, check JSON as serveed by Strapi). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For RPB-1, see instructions for running at https://github.com/hbz/rpb/blob/8f2a318/README.md#run-transformation-to-strapi-data.
With this, we could look into importing the output of the first workflow into strapi (test data: conf/output/test-output-strapi.json, create full data in single file with
sbt "runMain rpb.ETL conf/rpb-titel-to-strapi.flux").