input: uris, mendeley properties
See original GitHub issueTwo quick questions below.
As I was digging around for an answer of how to annotate the csl-citation.json uris
property, I came across this, from Mendeley.
So the description for uris
should simply be:
"description": "Any number of URIs that identify the bibliographic item."
Question 1 no reason to change this right; simply add the annotation? Or is there any reason to deprecate?
The other issue is the other properties they have; example:
"mendeley":
{
"previouslyFormattedCitation" : "(2007)",
"manualFormatting" : "2007b"
}
These are defined as follows:
- a “previouslyFormattedCitation” element of type “string”, set to the rendered output of the cite of the previous rendering round (this can be used to determine if the user manually altered the output)
- a “manualFormatting” element of type “string”, set to the user-customized output of the cite (this output will be used in favor of the generated output)
Question 2 should we add either or both of these to the schema? Do they provide value to citeproc-js
or citeproc-rs
in the context of Zotero?
To me, the first one seems more obvious than the second.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Mendeley - LibGuides @ URI at University of Rhode Island
Introduction. Mendeley is a free* reference manager. It works on PCs and Macs, and can sync your data with Mendeley's servers and other...
Read more >Untitled
Specify the URI to establish the identity of the style. The URI should be stable, unique and dereferenceable URI. Specify the journal's ISSN(s)...
Read more >csl-citation.txt
The CSL citation data object consists of: * a required "schema" element of type "string", set to the URI of the schema *...
Read more >Mendeley API Reference
Core catalog document attributes. The following attributes are returned by default. Attribute, Type, Description. id, string, Identifier (UUID) ...
Read more >03. Editing a reference in a citation - Mendeley Cite
Within the attributes panel you will see various options for editing the reference. You can add values to specific reference attributes (such as...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t have a strong preference on trying to get GUI apps to all use the same structure–this is something that those applications interact with, not the processors. For example, for Zotero, if
dontUpdate
is true, then it just ignores the processor generated output and leaves the text along. If Mendeley sets up a different workflow, I don’t think that’s necessarily a problem, especially not enough of one to try to get applications to make changes.Perhaps we should just allow custom properties (additionalProperties) on the citation JSON schema? Thinks like uris, dontUpdate, etc. can be added by the application as needed, but aren’t of concern to CSL?
Yes, understand. Just wanted to be clear that this is really up to them, doesn’t involve other moving parts at all.