Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nomad-FAIR nomad-FAIR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 218
    • Issues 218
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nomad-labnomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #663
Closed
Open
Issue created Nov 22, 2021 by Lauri Himanen@himanel1Maintainer5 of 5 checklist items completed5/5 checklist items

MaterialsProject parser + metadata improvements

We now have a parser for Materials Project workflow data, and there is also a lot of data that could be uploaded to the beta deployment. Before this, we should do a few improvements in order to make this data more findable and also cross-linked back to Material Project.

  • The parser should add some basic methodology information. This could be as simple as adding a results.method.method_name = "DFT", but it would be even better if we can also add a more detailed DFT methodology. Maybe all MP workflow uses the same XC functional etc. and we can have it hardcoded? Or then we retrieve the methodology from some external source (another NOMAD archive, MP API call, etc.)
  • The entries should be tagged with external_database = Materials Project. I think currently this is done by adding a configuration document (nomad.json?) in the upload folders which determines the origin.
  • In the entry overview page we need to add a link back to the Material Project website. For now, we simply reference the corresponding Materials Project material page which contains all the same data.
  • We should prepare a CLI function for creating and updating the materials project workflow data by using their API.
  • We should prepare a single upload containing a subset of the workflow data. Once we have improved the parsing of the data we could eventually even include the whole dataset.
Edited Feb 03, 2022 by Lauri Himanen
Assignee
Assign to
Time tracking