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

Central referencable literature database #3306

Open
akorgor opened this issue Sep 6, 2024 · 1 comment
Open

Central referencable literature database #3306

akorgor opened this issue Sep 6, 2024 · 1 comment
Assignees
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority stale Automatic marker for inactivity, please have another look here T: Enhancement New functionality, model or documentation

Comments

@akorgor
Copy link
Contributor

akorgor commented Sep 6, 2024

It can be challenging to maintain consistency when referencing literature across multiple sections of the NEST documentation. For example, in an ongoing project, we frequently reference two specific papers across different sections. One of these papers is still a work in progress, with its title and author order changing. Managing these references manually increases the likelihood of formatting errors and inconsistencies.

I propose adding a central bibliography file to the NEST documentation. This file would contain all relevant literature, and references to these works could be made across the documentation by linking to this file. The formatted references would be rendered in the respective location, ensuring that the documentation from the user's perspective remains the same, with a short literature list in each relevant section (see for example Sphinx documentation on bibliography. This approach would:

  • Ensure consistent formatting of references throughout the documentation
  • Minimize the chances of errors
  • Simplify the process of maintaining and updating references
  • Eliminate the need for manual copying of reference data in multiple places

An alternative would be to continue manually copying and pasting references into each section of the documentation. However, this approach is more error-prone and time-consuming, especially when frequently updating or referencing papers with changing information.

@jessica-mitchell jessica-mitchell added T: Enhancement New functionality, model or documentation S: Normal Handle this with default priority I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) labels Sep 6, 2024
Copy link

Issue automatically marked stale!

@github-actions github-actions bot added the stale Automatic marker for inactivity, please have another look here label Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority stale Automatic marker for inactivity, please have another look here T: Enhancement New functionality, model or documentation
Projects
Status: To do
Development

No branches or pull requests

2 participants