-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Hi,
It would be nice if you could provide a bibtex file next to your source code.
E.g. if you try to import bibtex from google scholar, then google parsed
the proceedings horribly. (Check it in Google Scholar.)
However, it is not clear e.g. who is the publisher, is it a proceedings or a special issue,
if there is any page number, etc.
The best practice would be:
- provide a bibtex file in the github repository
- give a DOI and/or link the original article, etc.
(if the article is open access and copyable,
it might be a good idea to directly publish a pdf in the github repository.
But this depends on the publisher, check it first if it is allowed.) - add duecredit support to your code
https://github.com/duecredit/duecredit
+1: I assume that scikit-image would be interested in a pull request.
It might be some work to actually merge it into the code base,
but it would make it much more known, and probably would generate
more citations/collaborations/etc. (or into OpenCV, etc. But skimage
is the most similar, in my opinion, to your code in style, language, etc.)
Metadata
Metadata
Assignees
Labels
No labels