-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Align item types and field mappings #61
Comments
For Zotero, there is already an effort to redesign the data model of item types, fields, and field availability: https://github.com/ajlyon/zotero-bits/wiki/Zotero-types-whiteboard If CSL is to succeed as a standard, I think we should take a more leading role in defining which item types should have which fields. |
The question is, how? Maybe we need a table (say on this project wiki?) with columns for csl, zotero, mendeley, etc. types and variables? |
Alright, a place-holder. People from Zotero, Mendeley, etc. should fill this out if they like. https://github.com/citation-style-language/schema/wiki/Data-Model-and-Mappings |
Note that the Zotero mappings are already here: http://gsl-nagoya-u.net/http/pub/csl-fields/index.html And that the Zotero type review is mainly in the issue tracker: https://github.com/ajlyon/zotero-bits/issues |
I think an important first step would be Mendeley and Papers publicizing their item type/field mappings, in a way similar to http://gsl-nagoya-u.net/http/pub/csl-fields/index.html. |
On Thu, Jul 28, 2011 at 9:05 AM, rmzelle
That's why I put up the table. Anyone can add to it, and it's better Bruce |
Maybe a (Google docs) spreadsheet would work better for this? |
On Thu, Jul 28, 2011 at 9:31 AM, rmzelle
Either way. |
I tinkered a little with Zoho Creator, an online database app. I'm not too familiar with database software, but using a database might make it easier to maintain the overview of item types and field mappings, while making them easier to parse. See an early effort: https://creator.zoho.com/rmzelle/csl-item-type-field-mapping/#View:Item_Type_View |
I have been working with mapping Mendeley attribute names to CSL attribute names for use with citeproc-js. I'm not sure that citeproc-js is fully CSL conformant, but I think it is. I have updated the page added by bdarcus by adding a table named "tentative entries". https://github.com/citation-style-language/schema/wiki/Data-Model-and-Mappings The first part of that table contains my best guesses at mappings of CSL attribute names to Mendeley names. The second part contains Mendeley attributes for which I do not see any corresponding CSL attributes. I will try to add a list of CSL attributes that don't seem to map to CSL attributes. It would be great to complete the "verified" table at the top of the page, if anyone has time and knowledge. |
Thanks, @rmzelle. Very helpful. |
Based on information from the Mendeley website, I updated the table added by @bdarcus. I also updated the lower table ("tentative entries") to include CSL attribute names for which the Mendeley site does not define mappings. Some of these (e.g. id, type, author, editor) are pretty clear. Those could be moved to the top table. Others are less clear. It might be helpful if someone could add entries for Mendeley attributes that do not map to CSL. I can't provide that at the moment. |
Thanks much for doing this! On Fri, Oct 26, 2012 at 11:55 AM, jimeng notifications@github.com wrote:
|
@denismaier This should be formalized. cf. https://discourse.citationstyles.org/t/do-we-need-style-coding-guidelines/1627/8 |
Zotero and Mendeley don't share the same item types, field availability, and field mappings (this affects other CSL-supporting applications as well). This limits interoperability of CSL styles between these applications (especially those styles that rely on field content instead of item-type conditionals), and an effort to align things would dramatically improve style output reproducibility.
The text was updated successfully, but these errors were encountered: