Provide additional information for a citation, e.g. chapter/pages about duecredit HOT 5 OPEN

I think it should be a comment or keyword we add to the entry, not to the
citation. With respect to this, I was thinking we should reconsider the
idea of entries and citations, and implement them as in latex. What we call
entries are References (that appear in the bibliography), and have all the
information, and they are fixed. Citations can be in multiple functions,
and should work like the \cite command in latex. On the same line, I was
refactoring the .count moving it to entries and not to citations.

On Fri, Jul 31, 2015 at 10:53 AM, Yaroslav Halchenko <
[email protected]> wrote:

not sure yet either it should become part of the reference entry (e.g. we
could easily add a chapter or pages to generated bib if doi/bibtex), or
more of a comment (might be more flexible) added to the citation (e.g. arg
"comment" or more explicit "location" argument for Citation/dcite/cite?).
Example could be when referencing 'edu' materials from a text book and
wanting to point to a specific location within that reference. If original
reference is a Url, it might be a "#id" to be added to the url (too
specific for Url though but smth to keep in mind)

—
Reply to this email directly or view it on GitHub
#33.

from duecredit.

hold on -- but it is already pretty much like that! ;) you can cite/dcite by a key, instead of providing a full entry. But that is often is inconvenient, thus it is allowed to give a full entry at the point of citation. But inside, it is like in Latex, and that is why we allow to preload entire .bib with entries -- references go by the key really. BTW -- I kept populating PyMVPA little by little: https://github.com/PyMVPA/PyMVPA/pull/330/files so have a look

And then again, it is echoing latex/bibtex where you have a bib entry, and then reference a specific location within it, e.g. 6\% of Debian~\citep[p.51, Table 4; p.50, Figure 28]{ghosh2006}. that is why I thought it would be better to keep it within citation, not entry, which can be reused for various spots

from duecredit.

gotcha, and forgot about \citep :p so I think that it's better if we keep the entries fixed, and the page/table/figure is added to the specific citation of the entry in the specific path.

from duecredit.

how will we call it/them? in latex it is like "before", "after" ;) so "add_before", "add_after" or you have ideas for something more descriptive?

from duecredit.

but before and after what? do you envision sth like this for the output summary?

also I think that the url id should go to the reference, not to the citation because otherwise it's confusing (would you plug the id next to the citation number, e.g., [3, #thisistheid]?

DueCredit Report:
- mymodule (v 0.0.16) [1]
  - mymodule:myfunction (solution to life) [2, p. 140]
  - mymodule:uberfunction (uber function) [3]
1 modules cited
2 functions cited

References
----------

[1] Halchenko, Y.O. & Hanke, M., 2012. Open is not enough. Let's take the next step: An integrated, community-driven
    computing platform for neuroscience. Frontiers in Neuroinformatics, 6(22).
[2] Atkins, J.H. & Gershell, L.J., 2002. title. My Fancy. Journ., 666(3009).
[3] http://www.pymvpa.org (Accessed 2015-07-31)

from duecredit.