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

Add "short" versions of "title", "container-title" fields #57

Open
rmzelle opened this issue May 25, 2013 · 9 comments
Open

Add "short" versions of "title", "container-title" fields #57

rmzelle opened this issue May 25, 2013 · 9 comments

Comments

@rmzelle
Copy link
Collaborator

rmzelle commented May 25, 2013

Some items don't have a Zotero field for the "short" form of a regular CSL variable. An example is the "Book Section" item type, which doesn't have a short field for the "container-title" variable. See citation-style-language/styles#560 (comment) for the specific request. This presumably extends to other items types as well.

@bwiernik
Copy link
Collaborator

bwiernik commented Feb 4, 2019

With Juris-M/citeproc-js@4f7dabd, citeproc-js recogizes -short forms of any variable.

@rmzelle rmzelle changed the title Add "short" versions of "title", "containter-title" fields Add "short" versions of "title", "container-title" fields Feb 6, 2019
@denismaier
Copy link

Should this be in CSL 1.1?

@denismaier denismaier added this to Proposed in Proposal Review Apr 20, 2020
@adam3smith
Copy link
Collaborator

title-short and container-title-short are already in CSL (this was/is for Zotero).
Btw, I now recall that the issues already had labels in the past (e.g. this one would have said zotero-fields), but they get lost when moving repositories, so are now missing.

Question is if, as per bwiernik's last comment and citeproc-js's current behavior, the -short suffix should be recognized on any variable. That seems a bit tricky to me -- it certainly would seem like a larger change in processor behavior that I wouldn't put in 1.1 and that I think warrants some discussion.

@denismaier
Copy link

So can this be closed if it's already there?

Concerning bwiernik's last comment: I guess this is more or less the same as this, right? If yes, discussion should perhaps take place there.

@adam3smith
Copy link
Collaborator

adam3smith commented Apr 20, 2020 via email

@denismaier denismaier removed this from Proposed in Proposal Review May 27, 2020
@dstillman
Copy link
Member

Does this need to be added to every type with a container-title field? If so, how do we want to label this? publicationTitle is "Publication" in some types and various other things in others (e.g., "Proceedings Title", "Encyclopedia Title"). We have "Short Title" for title already. Do we just prepend "Short" and abbreviate? "Short Pub.", "Short Proc. Title", "Short Enc. Title" and put it immediately after in the list?

@adam3smith
Copy link
Collaborator

Does this need to be added to every type with a container-title field?

That depends on how restrictive you want to be with this. For the ones you list definitely, also for the legal item types, but publication/container-title is also e.g. the blog title and the forum title and that seems unnecessary (but also doesn't do any harm).

Do we just prepend "Short" and abbreviate? "Short Pub.", "Short Proc. Title", "Short Enc. Title" and put it immediately after in the list?

I think that's good, yes.

@denismaier
Copy link

Do we just prepend "Short" and abbreviate? "Short Pub.", "Short Proc. Title", "Short Enc. Title" and put it immediately after in the list?

Another option would be to add "(short)", i.e. "short" in parentheses, after "Publication" etc.
=> "Publication (short)", "Proceedings Title (short)", "Encyclopedia Title (short)".

@bwiernik
Copy link
Collaborator

bwiernik commented Aug 23, 2021

I think prepending "short" makes the most sense.

I can also imagine a UI setup where "Short" could be nested underneath a title field, alongside potential future things like translated or alternative forms of the title variable.

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

No branches or pull requests

5 participants