{"action":"created","issue":{"url":"https://api.github.com/repos/semprag/biblatex-sp-unified/issues/8","labels_url":"https://api.github.com/repos/semprag/biblatex-sp-unified/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/semprag/biblatex-sp-unified/issues/8/comments","events_url":"https://api.github.com/repos/semprag/biblatex-sp-unified/issues/8/events","html_url":"https://github.com/semprag/biblatex-sp-unified/issues/8","id":105668246,"number":8,"title":"What to do when issuetitle and editor are present in an @article entry?","user":{"login":"adamliter","id":4974404,"avatar_url":"https://avatars.githubusercontent.com/u/4974404?v=3","gravatar_id":"","url":"https://api.github.com/users/adamliter","html_url":"https://github.com/adamliter","followers_url":"https://api.github.com/users/adamliter/followers","following_url":"https://api.github.com/users/adamliter/following{/other_user}","gists_url":"https://api.github.com/users/adamliter/gists{/gist_id}","starred_url":"https://api.github.com/users/adamliter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adamliter/subscriptions","organizations_url":"https://api.github.com/users/adamliter/orgs","repos_url":"https://api.github.com/users/adamliter/repos","events_url":"https://api.github.com/users/adamliter/events{/privacy}","received_events_url":"https://api.github.com/users/adamliter/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-09-09T19:29:00Z","updated_at":"2015-09-10T20:50:36Z","closed_at":"2015-09-10T20:49:38Z","body":"With the current implementation of `biblatex-sp-unified` (77705180f97bcc4489e62a23b5a8eba6719a21f3), the MWE given below will lead to this output in the References section:\r\n\r\n> Chomsky, Noam. 2013. Problems of projection. *Lingua* 130(1): *Syntax and cognition: Core ideas and results in syntax*. Luigi Rizzi (ed.). 33–49. `http://dx.doi.org/10.1016/j.lingua.2012.12.003`.\r\n\r\nI have a few questions about this, and at the risk of being perhaps a bit chatty and a bit off-topic for a GitHub Issue, I feel like I should also be transparent about why I'm asking. :smile: \r\n\r\nA friend and I are working on a project that we're calling [Lingbib](https://github.com/lingbib/lingbib). It's not ready to see the light of day yet, but the idea is to develop a GitHub repo where people can collectively contribute to a single `.bib` file for all of linguistics. We think it's a waste of time for people to do this individually, and we also think this will ensure greater accuracy of the information in the `.bib` file, since multiple sets of eyes will be looking at it.\r\n\r\nWe want the `.bib` file to ultimately be as portable as possible. This is why I proposed the changes for the `@inproceedings` driver that I did. If the entry really is an `@inproceedings` entry, then the `.bib` file will be portable and usable with other styles if it is entered into the database as an `@inproceedings` entry (not an `@article` entry).\r\n\r\nRelated to portability of the `.bib` file is the issue of ensuring that all available bibliographic information that is available is included in the entry in the `.bib` file. Some styles might call for more information than others, and so we want that information to be available in the `.bib` file should someone want to use the `.bib` file with a style that calls for more information.\r\n\r\nSo that's the background of why I'm asking this question. :smile: \r\n\r\nThe Chomsky (2013) reference was part of a *Lingua* special issue, so there is an `Issuetitle` (and `Issuesubtitle`) as well as an `Editor` for this `@article` entry.\r\n\r\nGiven that you've largely adopted the drivers from `standard.bbx`, there is more information printed than the Unified Style Sheet strictly calls for. So here are the questions that I have:\r\n\r\n1. Strictly speaking, the Unified Style Sheet doesn't say anything about this extra information, so I'm not sure what the best thing to do would be. Since it doesn't explicitly call for it, I'm assuming that it should just be omitted. Do you have any insight into what might be best to do in order to conform to the Unified Style Sheet guidelines?\r\n2. If the information should not be omitted, how should it be formatted? I'm guessing that it would probably be different than above. (Of course, the antecedent of this conditional could very well be false.)\r\n3. I was also wondering if you'd be open to me opening more issues like this. Part of the reason that Lingbib isn't ready to see the light of day yet is because we want to be able to distribute it with a Biblatex style that conforms to the Unified Style Sheet so that people can actually use the `.bib` file out of the box. If you'd rather not have me opening issues because of this, I'm happy to develop an implementation on my own, probably using yours as the basis. However, if you're open to me opening issues because of our Lingbib project, then you'll probably be seeing more of me. :smile: I don't want to bombard and overwhelm you, though, so I figured I should probably ask.\r\n\r\nAt any rate, depending on what you think about questions (1) and (2), I've developed an `issueandeditor` option that defaults to `false` in 2bd733dad649692edb6a31e81461620d56743782. If it is `false`, the information is not printed. If it is `true`, the information is printed and shows up exactly as described above (given the reliance on the `@article` driver of `standard.bbx`).\r\n\r\nBut there might be a better way of handling this case, depending on your answers to (1) and (2). Or if you'd prefer to not handle this case at all and you'd rather just have people not enter this information into the `.bib` file, that's fine, too. Then you can just close this issue, and I'll probably start working on a different implementation to be distributed with Lingbib.\r\n\r\nSorry for being a bit chatty and perhaps off-topic. :smile: \r\n\r\n## MWE\r\n```tex\r\n% !TEX encoding = UTF-8 Unicode\r\n% !TEX TS-program = arara\r\n% arara: pdflatex\r\n% arara: biber\r\n% arara: pdflatex\r\n\r\n\\begin{filecontents*}{\\jobname.bib}\r\n@article{chomsky2013:projection,\r\n\tAbstract = {With the crystallization of the ``generative enterprise'' half a century ago, two concepts became salient: the initial state and final states of the language faculty, respectively, UG (the genetic component) and I-languages. Since then inquiry has gained far greater scope and depth. It has also led to sharpening of fundamental principles of language. At first, descriptive adequacy appeared to require rich and complex assumptions about UG. A primary goal has always been to overcome this deficiency. Core properties of concern have included compositionality, order, projection (labeling), and displacement. Early work assigned the first three to phrase structure rules and the last to the transformational component. Simplification of computational procedures suggests that compositionality and displacement (along with the ``copy theory'') fall together while order may be a reflex of sensorimotor externalization, conclusions that have far-reaching consequences. As for labeling, minimal computation restricts options to the few that have considerable empirical support.},\r\n    Author = {Chomsky, Noam},\r\n    Doi = {10.1016/j.lingua.2012.12.003},\r\n    Journaltitle = {Lingua},\r\n    Issn = {0024-3841},\r\n    Issuetitle = {Syntax and cognition},\r\n    Issuesubtitle = {Core ideas and results in syntax},\r\n    Editor = {Rizzi, Luigi},\r\n    Langid = {english},\r\n    Langidopts = {variant=american},\r\n    Pages = {33--49},\r\n    Title = {Problems of projection},\r\n    Volume = {130},\r\n    Number = {1},\r\n    Date = {2013-06}}\r\n\\end{filecontents*}\r\n\r\n\\documentclass{article}\r\n\r\n\\usepackage[\r\n\tbackend=biber,\r\n\tbibstyle=biblatex-sp-unified,\r\n\tcitestyle=sp-authoryear-comp,\r\n\tmaxcitenames=3,\r\n\tmaxbibnames=99%,\r\n\t%issueandeditor=true\r\n]{biblatex}\r\n\\addbibresource{\\jobname.bib}\r\n\r\n\\begin{document}\r\n\\textcite{chomsky2013:projection}\r\n\\printbibliography\r\n\\end{document}\r\n```"},"comment":{"url":"https://api.github.com/repos/semprag/biblatex-sp-unified/issues/comments/139375141","html_url":"https://github.com/semprag/biblatex-sp-unified/issues/8#issuecomment-139375141","issue_url":"https://api.github.com/repos/semprag/biblatex-sp-unified/issues/8","id":139375141,"user":{"login":"adamliter","id":4974404,"avatar_url":"https://avatars.githubusercontent.com/u/4974404?v=3","gravatar_id":"","url":"https://api.github.com/users/adamliter","html_url":"https://github.com/adamliter","followers_url":"https://api.github.com/users/adamliter/followers","following_url":"https://api.github.com/users/adamliter/following{/other_user}","gists_url":"https://api.github.com/users/adamliter/gists{/gist_id}","starred_url":"https://api.github.com/users/adamliter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adamliter/subscriptions","organizations_url":"https://api.github.com/users/adamliter/orgs","repos_url":"https://api.github.com/users/adamliter/repos","events_url":"https://api.github.com/users/adamliter/events{/privacy}","received_events_url":"https://api.github.com/users/adamliter/received_events","type":"User","site_admin":false},"created_at":"2015-09-10T20:50:36Z","updated_at":"2015-09-10T20:50:36Z","body":"> I've merged your PR. Closing this issue, but we will follow up on collaboration on the broader issues raised.\r\n\r\n:+1: Thanks!"}}