-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Validation of CSL with custom variable #7294
Comments
I would strongly recommend using standard CSL variables. We cannot accept styles that do not validate into the repository, and I would strongly advise against adopting a data model for your organization that renders your data incompatible with other CSL styles (which don't use your custom variable). Could you describe your confusion about original-publisher? What's your intended use for "second-distributor"? |
Thank you; this is exactly the type of feedback I was hoping for. I really appreciate your prompt and helpful response! Our confusion around 'original-publisher' stems from legacy practices around collaborative distribution of physical data collections (that have been since digitized). In those cases, the data collections were jointly published, not necessarily 'republished' as the definition for the variable states. This is probably a good time for us to revisit those MOUs and their applicability with digital collections where the DOI only resolves to our data repository. Thanks again! |
For joint publishers, the current CSL approach is to enter both into the same |
Thank you for taking the time to make this suggestion; we really appreciate it! |
Greetings; my organization is working to submit a CSL style. Our data repository includes instances where two institutions may collaborate on the publication of data and our local citation style reflects this by presenting both institutions as 'publishers.'
To avoid confusion around the standard variable 'original-publisher', we thought that we would use a custom variable ('second-distributor') to designate this second data publisher/distributor.
In our local texts, this approach works when using the 'cheater syntax' with citeproc-js (as noted in this forum post).
The drawback is that--unsurprisingly--our CSL file fails validation at https://validator.citationstyles.org/. Given that the CSL submission guidelines state that we should "correct any validation errors" prior to submission, would you have any guidance on whether we should (a) adapt standard variables to our local needs or (b) submit and explain the use of our custom variable via a 'documentation' link or (c) just keep our CSL style local?
Thanks in advance for your help/expertise and apologies if any of the above is unclear!
The text was updated successfully, but these errors were encountered: