> - Ability to store references in Word documents.
Can you clarify more?
DOC?
DOCX?
ODF (w/OpenOffice)?
Bruce
Chris,
I'm keen to do some testing of 3.0b1. Though I'd like to know how this
will effect my current database & installations.
I currently run the Firefox version 2.1.8r10027 across two machines
(Linux Mint and Linux Mint Debian) and was already contemplating
moving towards the standalone installation.
Would I be fine to uninstall the Firefox & LibreOffice plugins,
install the stand alone and point it at my library? And, would I have
to do this to both installations? ie. Does 3.0 update my database?
Thanks
Tim Hamilton
--
Vote NO in referenda.
We're using the CSL citation schema from https://github.com/citation-style-language/schema/blob/master/csl-citation.json to encode the metadata, so it's a tweak to the field code that will work everywhere. It should be cross-compatible with Mendeley, although I'm not sure if they're equipped to recognize our field codes on non-Windows platforms.
I'm keen to do some testing of 3.0b1. Though I'd like to know how thiswill effect my current database & installations.
I currently run the Firefox version 2.1.8r10027 across two machines
(Linux Mint and Linux Mint Debian) and was already contemplating
moving towards the standalone installation.Would I be fine to uninstall the Firefox & LibreOffice plugins,
install the stand alone and point it at my library? And, would I have
to do this to both installations? ie. Does 3.0 update my database?
Hello Simon,
I've had a test of this latest on a MacBook Lion and one thing I noticed is that the standalone installed fine but there is a problem with Safari connection.
However when installing for Firefox 5 on Lion it works just fine but the problem is there is no PythonEx version for Zotero 3.01b. I tried installed the older version of PythonEx and it seems to installed just fine but when click on inserting citation in MacWord 2011 and there is no APA referencing style list.
Chrome isn't working on OSX Lion so therefore I cannot test this out.
--
You received this message because you are subscribed to the Google Groups "zotero-dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/zotero-dev/-/b_UqrlrorcAJ.
To post to this group, send email to zoter...@googlegroups.com.
To unsubscribe from this group, send email to zotero-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/zotero-dev?hl=en.
Translators should all work fine. Among the changes for translator
authors, however, is that the translators are served directly from
GitHub (https://github.com/zotero/translators), which means both that
they should be able to reach users faster and that the preferred
submission method for translators is now to fork the main repository
and issue a pull request; see https://github.com/zotero/translators
for instructions on doing so using GitHub. This workflow is exactly
what we recommend for style submission (in fact, I stole the
documentation from that page), so it should be familiar to many.
The other major change is that Zotero 3.0 (and Zotero 2.1.9, which
should be imminent) support automated translator testing, as discussed
on this list several months ago. I've written up a basic overview of
that system (http://www.zotero.org/support/dev/translators/testing),
but the documentation still needs some work, including screenshots.
To work best with the translator testing system, you should also
install the Scaffold 3.0 preview
(http://www.zotero.org/support/dev/translators/scaffold), which makes
it easy to create and run translator tests in Zotero 2.1.9+ and Zotero
3.0, in addition to other cool features, like the ability to use an
external text editor, ACE integration, error highlighting, and
improved translator selection in the load translator window.
Avram
One final note: we're now encouraging the inclusion of a licensing block in each translator to make licensing terms explicit.
Sean
> --
> You received this message because you are subscribed to the Google Groups "zotero-dev" group.
The guidelines for connector compatibility, and other such changes are
outlined in the developer changelog
(http://www.zotero.org/support/dev/client_coding/changes_in_zotero_2.1_and_zotero_standalone).
More detailed information on connectors will eventually make its way
to a separate page
(http://www.zotero.org/support/dev/translators/connectors).
Note that translators that use Erik's translator framework are
automatically connector-compatible.
> One final note: we're now encouraging the inclusion of a licensing block in each translator to make licensing terms explicit.
Licensing is noted here: http://www.zotero.org/support/dev/translators#licensing
It would be helpful if people who have submitted unlicensed code in
the past would post license declarations for their contributions (even
contributions made years ago), so that we can get explicit licenses on
the translators. Affero GPL, the main license of the project, is
recommended. It is the opinion of Erik and me that framework-derived
translators are automatically subject to the Affero GPL, as they are
derived from AGPL code. Still, explicit declarations would be nice for
them as well.
Maybe I can add license insertion as a Scaffold feature.
Avram
Not for the first beta, but we'll see what we can do for later betas.
Mappings are easy, but changed fields could require a lot of work if we
don't want to do a sync cut-off (and 3.0 doesn't yet require a DB
upgrade either), so those may get pushed back to the next major release.
> Also, anyway we can address the issue of the styles shipped with the
> clients - as I have pointed out many times, the list of styles shipped
> currently with Zotero makes very little sense - e.g. it includes two
> styles that are essentially redundant (MHRA and Vancouver/NLM) and
> other styles that are of poor quality (ASA, Harvard 1).
>
We've already updated the build script to pull styles from GitHub, so at
least it's now including up-to-date ones. Feel free to take the lead on
hashing out a final list. Once we have that, we can adjust what gets
bundled.
The problem is it won't detect the cites on the website with Safari OSX10.7.
But it is installed just fine on OSX 10.6. So I guess you may need to revise on the OSX Lion as well.
I've been testing Zotero Standalone on Linux Mint 11 (essentially
Ubuntu 11.04) and have a few comments and observations.
The connector with Firefox does not appear to be working as I do not
get an icon in order to import citations.
LibreOffice integration seems to work well except for a two niggles
with the Quick Format Citation dialog. Although it works correctly in
the majority of times it is called about 30-40% of the time it will
either not be in focus or, more often, will pop up behind the active
window. Also on the odd occasion esc key does not cause it to exit.
I'll also give the Chrome/Chromium connector a run however the link in
to the file is currently showing a site update message.
Cheers
Tim
HI Simon,I've been testing Zotero Standalone on Linux Mint 11 (essentially
Ubuntu 11.04) and have a few comments and observations.The connector with Firefox does not appear to be working as I do not
get an icon in order to import citations.
LibreOffice integration seems to work well except for a two niggles
with the Quick Format Citation dialog. Although it works correctly in
the majority of times it is called about 30-40% of the time it will
either not be in focus or, more often, will pop up behind the active
window. Also on the odd occasion esc key does not cause it to exit.
I'll also give the Chrome/Chromium connector a run however the link in
to the file is currently showing a site update message.
For clarity, this is a 32bit system using Zotero_linux-i686.
>> The connector with Firefox does not appear to be working as I do not
>> get an icon in order to import citations.
>
> At what site(s)? Can you generate a report ID and a debug ID?
This problem occurs on all sites, none display a Zotero save icon in
the Firefox address bar. A selection would be:
Library of Congress (http://catalog.loc.gov)
Google books (http://books.google.com.au/)
Melbourne University Library (http://cat.lib.unimelb.edu.au/)
LaTrobe University Library (http://www.lib.latrobe.edu.au/)
Report ID: 1215028378
Debug ID: As Zotero is not invoked by Firefox there is no debug output
to report.
Running Zotero from the command line after enabling debug logging
produces the following output.
http://pastebin.com/91QdpQUn
Is it possible that a previous installation of the Zotero Firefox
plugin is causing a conflict even though it has been removed?
Is it worth testing with an alternate Firefox profile?
> I'm not sure why escape wouldn't exit, but the reason it's not in focus is
> that your window manager has focus stealing prevention enabled. We'll have a
> solution for this eventually.
Great, will this also solve the issue that when using the Classic View
citation dialog that the Zotero window is brought to the foreground
while citation details entered and not backgrounded again once
complete?
>> I'll also give the Chrome/Chromium connector a run however the link in
>> to the file is currently showing a site update message.
The Chromium extension seems to work fine though I did have an issue
saving items from the Library of Congress. I would assume this is a
translator issue though it did seem to save correctly.
Debug ID: D664061157
Cheers
Tim
For Zotero-in-Firefox to talk to Zotero Standalone and send it
citations, you need to install the Zotero 3.0 XPI -- Zotero 2.1 can't
do it, and Firefox can't talk to Standalone without Zotero installed.
> The Chromium extension seems to work fine though I did have an issue
> saving items from the Library of Congress. I would assume this is a
> translator issue though it did seem to save correctly.
>
> Debug ID: D664061157
This seems to confirm that the problem is just that you don't have a
connector installed for Firefox-- the standard Zotero XPI can switch
modes between full-fledged Zotero and connector. The latter is
relatively untested, but it looks like you just don't have it set up
at all.
Avram
> This seems to confirm that the problem is just that you don't have a
> connector installed for Firefox-- the standard Zotero XPI can switch
> modes between full-fledged Zotero and connector. The latter is
> relatively untested, but it looks like you just don't have it set up
> at all.
>
> Avram
>
That would be the issue, I must have misinterpreted Simon's original
post & was wondering why Firefox didn't require a connector.
After installing the Zotero 3.0 XPI adding bibliographic records to
fully-fledged Zotero in Firefox works correctly. And, with the Zotero
LibreOffice Integration for Firefox plugin adding citations to a
LibreOffice document works.
As a connector to Standalone, however, it seems a little buggy. Adding
a bibliographic records seems a little hit and miss. Major websites
seemed to work well though less well known sites did not work at all.
Some Tests & Results
Saving a record when 'My Library' selected in Zotero Standalone worked
with no errors.
Saving the same record when a sub-collection selected in Zotero
Standalone threw a 'Could Not Save' Item error & did not save the
record to the selected sub-collection. The record was still added
correctly to 'My Library'.
Google Books DebugID: D163554390.
Library of Congress DebugID: D1945613949.
Saving a record from either University of Melbourne or LaTrobe
University library catalogues resulted in a 'Could Not Save Error'
University of Melbourne DebugID: D1293906016
LaTrobe University DebugID: D1275161596
Hope some of this is useful.
Tim
Nope. Just not finished. They'll be returning in a later beta.
When I try "Save Zotero Snapshot from Current Page" from Chrome, I get
nothing. No debug output in the connector, no error messages in the
console, nothing.
Saving using the address bar icons works fine (and feels like magic!).
Avram
On 8/11/11 1:13 PM, adamsmith wrote:
> I know you're mainly interested in testing, but I'd be curious about
> the status of the csl/zotero schema/item update that Avram, Rintze et
> al have been putting a lot of work into (i.e. can we at least get the
> mapping changes/fixes/additions?).Not for the first beta, but we'll see what we can do for later betas.
Mappings are easy, but changed fields could require a lot of work if we
don't want to do a sync cut-off (and 3.0 doesn't yet require a DB
upgrade either), so those may get pushed back to the next major release.
On Thu, Aug 18, 2011 at 9:53 AM, Simon <si...@simonster.com> wrote:
> Forgot the connectors:
>
> Zotero Connector for Chrome:
> http://download.zotero.org/Zotero_Connector_2.999.1pre.r10195.crxWhen I try "Save Zotero Snapshot from Current Page" from Chrome, I get
nothing. No debug output in the connector, no error messages in the
console, nothing.
I've posted new pre-beta versions of Zotero 3.0b1 at the following locations:
Zotero for Firefox: http://www.zotero.org/download/dev/zotero-trunk.xpi
That explains it. The smooth restartless installation of the Chrome
extension made it easy to forget that I hadn't even reloaded the
pages. Works now; thanks!
Avram
Zotero 3.0 is a huge release, for which a database upgrade and sync
cut-off are not unreasonable. These changes have been under
consideration for the better part of a year, and they are now a fairly
stable lot. Making these carefully considered changes is a big part of
demonstrating once again that Zotero is seriously dedicated to the
basic research needs of its users, even as it pursues great new
features like the web interface and standalone. The solid scholarly
underpinnings of Zotero distinguish it from the competition, and
refinement on that front is at least as important as the grant-funded
innovation that Zotero 3.0 also brings.
The biggest shortcoming of Mendeley, as was poignantly pointed out by
a would-be switcher on Twitter, is that they're not focused on the
essential minutiae of scholarship:
http://twitter.com/#!/jonnycollege/status/104395453650567169 and
http://twitter.com/#!/jonnycollege/status/104396470534422529
I know it's a huge decision to cut off syncing, and every database
upgrade is a little scary (I know I always have this little fear that
somehow the whole thing will be corrupted), but these changes matter a
whole lot to a lot of people.
Avram
Entirely fair, but "the next major release" doesn't have to mean a year
from now, and I don't think there's any reason to greatly delay getting
the current 3.0 code, which is relatively stable, into users' hands
going into the school year. And I think we're well beyond the point
where a complete sync cut-off is even an option (and it would be
completely untenable paired with a beta period of any length).
What I think we should do is branch 3.0 soon, get a final out as soon as
possible, and then implement per-library syncing on the trunk, which
I've wanted to do for a while anyway. Among other benefits, that could
let us make schema changes and allow users to essentially upgrade server
libraries independently, with a prompt before syncing each one the first
time with the new version. Dealing with group libraries would still be
tricky�who gets to decide when a group gets updated?�but even if any
member who made changes to a group could update it, the worst that would
happen is that users who didn't upgrade wouldn't be able to sync that
library. Any libraries that hadn't been used with the new version,
including personal libraries, would continue to sync with older versions.
This sounds good, especially since per-library syncing could be rolled
out as 3.1 without necessarily waiting for a large number of
additional features. That would also open the way for the eventual
merger of the multilingual branch with its associated significant
schema revisions.
Mainly, though, we need to make sure that these changes are on the
short-to-medium-term roadmap. Because they matter a lot.
Avram
Sorry, just full-text content�I forgot we added tags and note content to
"All Fields" when we changed that to the default.
The relevant ticket is here: https://www.zotero.org/trac/ticket/1563
I'm also hoping to hear some more reasoning as to why the feature
should be limited to HTTP and HTTPS, or to the other protocols being
added.
Avram
Blacklisting a few schemes (data:, javascript:) might be fine. The main
consideration is that these could be synced, so we don't want to allow
anything that could be used as an attack vector.
I'm also a bit worried about this in terms of increased attack service
too, so I think I'm leaning towards white-listing, or a hard-coded
blacklist in combination with a whitelist in a hidden preference. No
known feature would currently cause Zotero to request any of these
URIs without user action, but a double-click on an item in a group (or
personal, of course) library shouldn't run the risk of launching
unexpected local applications, which may have unexpected security
holes of their own.
Avram
Yeah, I agree. Blacklist + a user-configurable whitelist�empty by
default, I think�seems like a good idea.
So what happens when a user has a link attachment that uses a scheme
not in the local Zotero client's whitelist? Do we suppress the
attachment? Prevent the link from being opened? If we're aiming to be
careful here, I suppose we could prevent it from being opened and
display a message that directs the user to a support page with
information on URI schemes, how to specify the whitelist, and the
security implications.
This will need to be considered for the server-side write API when the
time comes as well.
Avram
Actually, we can probably let Firefox handle this. Opening a new
protocol via loadURI() as we already do should display a security
warning to the user�"An external application must be launched to handle
[scheme] links."�with an option to whitelist the scheme permanently.
It's possible, however, that we should be calling
externalProtocolHandlerExists() before attempting loadURI(). Not sure
would happen right now if an unsupported scheme was passed.
Looks like we're already preventing these from being called in
ZoteroPane.loadURI(). Might as well prevent them from being added
through the client, though.
Also, there's a regexp for Standalone in ZoteroPane.loadURI() that might
need to be tweaked for this.