Skip to content

SORSE/sorse-data-filter

Repository files navigation

sorse-data-filter

This project manages the visibility of data and automatises several workflows centred around the abstract submission process of SORSE – A Series of Online Research Softare Events. It is our aim to ensure that no connection between personal data and diversity information can be derived from data exported from the Indico event management platform.

Input of the tool is the exported data from the Indico system. Via a command line interface a user can pick one of the available workflows. For each workflow, allowed fields from the import data is specified along with the output format that is required.

The tool currently supports the following automatised workflows:

  • website: export of Markdown-formatted data after acceptance to the website
  • scheduling: export of data to a google drive to support the scheduling process

Further workflows are planned including:

  • rejected: export of information on rejected abstracts
  • mentoring: export of data to a google drive to support the mentoring process
  • statistics: export of statistical data to a google drive

Configuring workflows

The export of data is centred around the concepts of allowing specific data fields and providing formatting with the help of the templating engine Jinja2.

Configuring allowed fields

Allowed fields within a workflow are specified in the workflows.yaml file. For each workflow an entry is created that holds a section for allow_lists. The entries in this field follow the model specified in models and include the contribution itself, persons and questionnaires holding specific information for each contribution type as well as diversity information.

Configuring templates

Templates that can be used are contained in the templates folder. For example the template for the website workflow is templates/website.md. Available templating constructs can be found in the documentation of Jinja2. In principle, all different file formats can be configured with this templating engine.

The name of a template for a given workflow is given via the field output_template in the configuration file.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •  

Languages