Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • I Import API
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

We are happy to announce the rollout of GitLab 15.0 in July! 🥳 Please check the information on breaking changes and feature removals to determine if your workflows are impacted.

  • memoriav
  • Memobase 2020
  • services
  • Import Process
  • Import API
  • Issues
  • #1

Closed
Open
Created Jul 14, 2020 by Sebastian Schüpbach@sschuepbachOwner

Enriching multiple instantiations of one record in import workflow simultaneously

Until now I haven't been aware that the different instantiations of a record (digitalObject, physicalObject, proper record metadata) are serialized in a message each. However this is a problem for the media-metadata-extractor, which must enrich the record entity as well as its digital object. The information required for the enrichment, the link to the media resource, is only available in the digitalObject. Right now I see two strategies to solve this problem, and I'd like to discuss them with you, @jonas.waeber and @lionel.walter:

  • Keeping all information regarding one record in one message and probably splitting them after the enriching step in media-metadata-extractor
  • Aggregating the needed information in media-metadata-extractor and enriching only after each required part of the record has arrived in the service

What do you think?

Assignee
Assign to
Time tracking