-
Notifications
You must be signed in to change notification settings - Fork 0
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
getting a publication list #11
Comments
I started a bibtex file in simpeg/simpeg.github.io#15. Is anyone aware of simple ways to build a page from a bibtex file? |
Rather than maintain a bibtex, it might be nice to have abstracts + images to show things off a bit. What do folks think of something like this? A curvenote project that has an article per publication (paper / conference abstract / poster / etc) https://curvenote.com/@simpeg/publications/cockett-et-al-2015-simpeg |
I think I like the pyGIMLi approach more, simply because it is on the website, and not somewhere else (for both maintenance sake but also to not loose/confuse the user). Another approach would be a gallery-style thing, like I tried in empymod: https://empymod.emsig.xyz/en/stable/gallery/published/index.html (however, that approach certainly needs improving...) |
On the SimPEG website, it would be valuable to have a page that includes a list of references of publications that use SimPEG. PyGimli is a nice example: https://www.pygimli.org/publist.html
They use a bibtex file and build the page from there. I suggest we follow a similar pattern and also collect publications via a bibtex file (makes it easy for contributors), encourage folks to include both doi and arxiv link (or other open access version -- e.g. from research group or otherwise). It can live at
simpeg.xyz/publications.html
and link in the docs (as suggested in simpeg/simpeg#500).Additionally, I think we should have a presentations (new page?
simpeg.xyz/presentations
) that can embed talks given at scipy or otherwise that use SimPEG. This could also be built from a bibtex (a bit clunky, but might be nice for consistency).Please feel free to add your thoughts!
The text was updated successfully, but these errors were encountered: