MLZ standalone
Hi,
I really want to begin working with MLZ, as I need to use the style required by the book with the blue cover. However, I don't like FF and really do like Chrome. Any plans on having an MLZ standalone soon?
Also, another questions if I may. Since I've been using Zotero standalone for quite some time, and I have tons of items there, also synced to the server with attachments, how will the migration work? Will these things appear in MLZ too? Do I need to actively move them there somehow?
Thanks,
Roy
I really want to begin working with MLZ, as I need to use the style required by the book with the blue cover. However, I don't like FF and really do like Chrome. Any plans on having an MLZ standalone soon?
Also, another questions if I may. Since I've been using Zotero standalone for quite some time, and I have tons of items there, also synced to the server with attachments, how will the migration work? Will these things appear in MLZ too? Do I need to actively move them there somehow?
Thanks,
Roy
Thanks again,
Roy
MLZ can be built as a Standalone client; it's just a matter of finding people to do the builds, since my time is limited and I don't have access to all of the relevant platforms (Mac, Windows). If anyone wants to help with this, it would be great.
??
Roy
(The particular case that worried me was where there are two records: one with "Smith" as the author name and (say) "Sumisu" as a multilingual alternative; and another record with "SmithX" as the author name. If the first record author is changed to "SmithX", I was concerned that the pointer to the "Sumisu" alternative would be lost. Testing this use case, I find that the "Sumisu" alternative persists on the first record, which is what should happen.)
We want to step carefully, but it appears that using official Zotero Standalone on an MLZ database is safe. Note, though, that multilingual fields will be invisible in official Standalone, and that any copy operation (such as "Duplicate this item") in official Standalone will omit multilingual fields.
There are also some small differences in the CSL field mappings for legal item types between the two tools (MLZ and official Standalone), so best practice will be to use an MLZ style from http://citationstylist.org with MLZ itself when generating citations.
I assume we should just go feature by feature and arrive at an implementation consensus and get this over with. Are there certain features of MLZ that Dan or Simon would be opposed to?
Before we get carried away though, I think this discussion should probably continue on zotero-dev google group.