Upgrade Storagebdarcus
About
- Username
- bdarcus
- Joined
- Roles
- Member
Comments
-
If you're arguing we can make this "simple" initially (to get it working), then fine. But am I correct that you'd have no objection to eventually go to a more complex system like Dan describes? Basically, yes. If we need to go there, so be it. But …
-
So you're saying that you wouldn't allow multiple representations for a given person in the database? At least as a first step, yes. Or only at the citation level, instead using whichever name was marked as canonical in the database? Not following y…
-
This might not be quite as straightforward in Zotero, since some people may want/need to cite the author as listed in the particular work. I think before we'd move forward on any particular solution to this very real problem, we'd want to interrogat…
-
Well, the bigger solution is the same as in a decent contact application: to treat agents (authors, publishers, etc.) as full objects, rather than dumb text strings. But that itself doesn't solve all problems; there'd still be details to work out.
-
@trench: What kind of resources are you needing? Street-corner resources? Black-market resources? Dilithium resources? Please. Ultimately, it's a matter of time. Zotero development has primarily happened through paid labor (with some exceptions; for…
-
Ditto adamsmith. I would love to see a Chrome extension. I'd also love to see a native Android client application that can interact with Zotero servers. But that's not the same thing as me coming here and demanding the Zotero developers create the…
-
FWIW, I'm very much in favor of adding additional fields to a wider range of types. Have complained about this issue a number of times.
-
This is related to previous discussions (you can search for) on journal abbreviations. It's not supported, in part because it's a tricky issue.
-
It's not clear to me why you need this. If it's a common case, then I'm guessing what Gracile is writing (I don't do french) is probably along the right track (changing the style to have ibid handling).
-
@blazek: thanks for the explanation, but that's not what I asked. I was trying to figure out what case examples it would catch. My assumption is that if the answer to my second question is no, then it can only work for acronyms.
-
This allows detection of the words that are non-standard, so the management of exceptions can quickly focus on the problematic details. What sort of cases do you see this algorithm catching? And does it only work if the raw data is entered British s…
-
Don't know if this makes any sense to you but I would find it most welcome and usefull, and it wouldn't compromise the db sharing, as far as I can see. Maybe I'm just misunderstanding you, but it seems to me it would absolutely "compromise ... db sh…
-
This points out a flaw in notes as currently implemented. Right now, there is no way to see who has authored a note in the Zotero UI. This is a major PITA if you're collaborating. So first things first is that the UI needs to indicate who edits or o…
-
On preserving case, I think some of it could be automatically handled, and the rest can be done with a simple HTML micro-language behind the scenes, which in the Zotero UI would be invoked with some simple mechanism (like highlight --> contextual…
-
Actually, I was thinking the easiest way to do a CV is to just do it in Word, but copy-and-paste the formatted bibliography entries in? Is there any reason that's not sufficient?
-
Maybe worth adding a "last updated" field to certain types which requires a full date? Worth further discussion in any case ...
-
One advantage of doing this is it would be a backdoor way to get support for mobile platforms like the iPhone and Android. I'd suggest adding this and include the ability to limit import by tag.
-
Plus it seems space delimited attribute values can't be easily changed with XSLT. Some hint at using regexp ( http://www.biglist.com/lists/lists.mulberrytech.com/xsl-list/archives/200907/msg00043.html ), but I haven't been able to get that working y…
-
I assume your concept of "class" describes what Zotero implements as the fallback type (monograph=book, part in a monographs=chapter, part in serials=article). Exactly! If structural characteristics are clearly defined for these classes/fallbacks in…
-
Another thought - Why don't we replace all CSL types with just the three fallback types and have some schema extension mechanism to support all native types? Picking this up from previous reply, what exactly do you mean by the extension mechanism? A…
-
There are people who overuse types and put them everywhere even if they could do without them as your example shows. That is not a problem of fallbacks, however. That is a problem of all types in general. Fallbacks (although you may have introduced …
-
@rintze: what is the current selection of CSL item types based on? The Bibliographic Ontology? (http://bibliontology.com/) Let's say they were developed in parallel. But they have somewhat different purposes, so there's some divergence.
-
this is just not true, given the demands of styles like Chicago and Bluebook. Your example above would not work for manuscripts, for one. @erazlogo: are you saying it's not possible to tweak the example macro I provided (which was just for illustrat…
-
The fallback feature simplifies the citation style files and makes them easier to develop. Does it really? Consider macros like this (not verified, so there may be a minor error of syntax): Peopl…
-
I would wish to think it will not be a practical problem, however, why risk it now that Zotero community has managed to establish such a great number of citation styles that it can be be reckoned with in this regard in comparisons to other leading r…
-
If you remove the fallbacks, what do you plan to do about the existing styles that will thus get broken? My guess is it won't be much of a practical problem. Where it is, those styles will have to be updated (manually, I'd imagine).
-
No. I developed the fallback system in the original version, before we had the cs:choose structure. This makes it redundant, and so adds unnecessary complexity for implementers. We have thus removed that (BTW, undocumented) processing behavior.
-
Publishers can have multiple locations, and items can (though rarely) have multiple publishers. So the solution isn't that straightforward.
-
I would "enter 'Princeton & Oxford' as a single string."
-
I really wish this sort of thing wouldn't get added when we have no clear idea (at least I don't) what the plan is for the evolution of Zotero's data model and UI.