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

Qnotero Integration? #2

Open
adam3smith opened this issue Jan 16, 2015 · 2 comments
Open

Qnotero Integration? #2

adam3smith opened this issue Jan 16, 2015 · 2 comments

Comments

@adam3smith
Copy link

This maybe wishful thinking, but since you wrote both:
I've long thought that using Qnotero as a substitute for word processor add-on would be really neat:
i.e. instead of copying a citation's citekey from Zotero (I realize that's not possible for academicmarkdown yet, but it'd be trivially easy to write a Zotero translator that does that--if you're interested I can do that for you), you'd just select the item in Qnotero, and create the citekey.
Is that realistic at all?

edit: ideally, the format of the citekey would be customizable. I'd really like this to also work for our google doc/Scrivener oriented ODF-scan format

@smathot
Copy link
Owner

smathot commented Jan 19, 2015

Something like that would be very convenient, but I'm not sure how to implement this best. Right now, academicmarkdown doesn't really use unique citekeys. It's more of a search query, which should match exactly one reference. So say that @Doe2014 is a unique reference in one database, it may not be in another database with two 2014 papers by Doe, in which case you'd have to write e.g. Doe2014Journalname.

So how would that logic fit into the idea of citekeys? And do Zotero references really have unique citekeys?

@adam3smith
Copy link
Author

Hopefully Zotero will eventually get (human-usable) stable citekeys, but that's a different topic.
My approach would be to pick something relatively safe to be unique- i.e. including the (short?) title - here. Might still be preferable to many people (especially the less-techy crowd that markup may be able to attract over LaTeX). Allowing basic customization via prefs wouldn't be hard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants