Build cv_entry template for an individual data package

[saraedum]

Tasks:

• Create the heading Pt(111) from metadata. (see CV template: added entries from the metadata file. #37)
• Create the small heading subtitle from metadata.
  • see below electrolyte (see Context-dependent Descriptors + Electrolyte Rendering #81)
• Create introductory text from metadata.
  • Create entries that can be extracted directly from metadata file (see CV template: added entries from the metadata file. #37)
  • Create electrolyte text
    • Loop over components and print component name + concentration_unit (see Context-dependent Descriptors + Electrolyte Rendering #81)
  • Create entry for scan rate (see Context-dependent Descriptors + Electrolyte Rendering #81)
  • Create literature link (see Include the bibliography files (bibtex) in the Database #69 and see Add citation as entry.citation and implemented citation in cv_entry.md #77)
  • include the Figure identifier in the description (raised in wang_1996_ordered_6672 #52) (implemented in Refactoring unit implementation for use in dataframes and plots #88 as label of the curve n the plot)
• Create literature reference from .bib files. (see Include the bibliography files (bibtex) in the Database #69 and see Add citation as entry.citation and implemented citation in cv_entry.md #77)
• Properly format plots.
  • render plots with original figure units (see Refactoring unit implementation for use in dataframes and plots #88)
  • Add Reference scale on x-Axis (see Refactoring unit implementation for use in dataframes and plots #88)
• Add the comment from metadata below the plot
  • once Fixes #85 and added comment property svgdigitizer#93 is done
  • Also indicate if the data is digitized or if it is raw data (see CV template: added entries from the metadata file. #37)
• Add collapsible bibliography in bibtex style. (see Add collapsible bibliography to cv_entry.md #94)
• Create collapsible figure description section inlcuding a short text for the meaning of this data (see Add collapsible figure description to cv_entry.md #89)
• Style "Further Information" section. Styling cv_entry.md to make it look more pleasing. #113
• Make metadata from .yaml file available, e.g., by showing the metadata formatted as YAML with syntax highlighting. (see CV Template: Implement collapsible metadata #40)
• Remove duplicate sections about electrolyte, reference electrode and scan rate. (see CV template: added entries from the metadata file. #37)

[DunklesArchipel]

Would it be helpful to have a button, where reades could submit raw data for the digitized data. Lets say an author finds his/her dataset in the DB an thinks it would be nice to actually show the real data.

[saraedum]

What should that button do exactly? That might be a lot of work to implement actually. But maybe just a link that points to instructions how to improve the data if you are the author...would be good?

[DunklesArchipel]

It could either simply be a link to an e-mail or to a submission form, where the author can provide some details, which will be sent by e-mail. Google forms?

[linuxrider]

It would be great but most probably out of scope/not feasible if the said button would trigger an "anonymous" (submitter without github account) commit to a new branch and a merge request on the website repo which then can be reviewed by someone of the (core) team. With this we would directly have the benefits of all tests with minimal effort by us.

[DunklesArchipel]

Would it be useful to have a report button, if there are mistakes for example in the metadata file? I don't think that everyone knows how to create an issue or a pull request.

[DunklesArchipel]

Note: Package to transform strings to markdown:

https://pypi.org/project/markdown-strings/