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

Message-queue-mapper: automatically parse YARRRML #8

Open
SvenLieber opened this issue Jul 23, 2021 · 0 comments
Open

Message-queue-mapper: automatically parse YARRRML #8

SvenLieber opened this issue Jul 23, 2021 · 0 comments

Comments

@SvenLieber
Copy link
Contributor

Currently the mapping relies on RML files, however, in this repo we provide RML files in the human-friendly YARRRML syntax. This means that right now whenever a mapping changes there is a manual step of creating RML from YARRRML and updating the RML file used by the message-queue-mapper.

This manual step could be avoided if the transformation from YARRRML to RML happens automatically.

On the receiving end,

  • lib/generators/warc-generator.js needs to be extended with an if( msg['type']=== 'yarrrml_mapping')
  • the connected lib/targets/rmlmapper.js needs to be extended with an if( msg['type] ...) to check for both yarrrml and rml
  • the connected lib/targets/rmlmapper.js should use the yarrrml-parser on the input YARRRML file to create a RML file usable by the RMLMapper if the type is yarrrml_mapping.

On the sending end

  • lib/targets/rabbitmq.js should emit yarrrml_mapping as type
  • the key mappingFileLookup of the config config-rabbitmq.json from lib/targets/rabbitmq.js should use yarrrml_files
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

No branches or pull requests

1 participant