Upgrade StorageZotero COinS Export
Zotero COinS Export
Thank you very much for supporting COinS. We use them extensively.
Previously, we used the COinS generator, http://generator.ocoins.info/, but since OCLC apparently decommissioned the COinS generator, we have begun using Zotero to create COinS for some of the many publications we host.
I noticed that the Zotero COinS generator begins the ContextObject with "url_ver=Z39.88-2004&" The COinS generator began the ContextObject with "ctx_ver=Z39.88-2004" and omitted the url_ver field. I believe the url_ver field should be omitted from the COinS. This is based on the following sources:
The COinS description, http://ocoins.info/, "Specification : OpenURL ContextObject in SPAN (COinS)- Embedding Citation Metadata in HTML,"
"To add a COinS to an HTML document, put a NISO 1.0 "ContextObject" into the "title" attribute of an HTML span element with class attribute set to "Z3988". A brief guide to the OpenURL 1.0 ContextObject, http://ocoins.info/cobg.html, is available.
Example
OpenURL COinS:
<span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.issn=1045-4438"></span>"
The "Brief guide to Implementing OpenURL 1.0 Context Object for Journal Articles," http://ocoins.info/cobg.html, states,
"Here's the smallest amount of information that you need to know to make correct, minimized, NISO OpenURL 1.0 ContextObject for journals and journal articles:
a 1.0 OpenURL ContextObject using the "journal" metadata format can be made as follows
ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&<key1>=<value1>&<key2>=<value2>&...&<key2>=<value2>
If you append a ContextObject to the end of <baseurl>?url_ver=Z39.88-2004&, you get a valid 1.0 OpenURL link.<baseurl> is the address of an OpenURL link service.
ctx_ver=Z39.88-2004 says "this is a version 1.0 OpenURL ContextObject"..."
More formally, the NISO 1.0 KEV ContextObject Format in is defined in "The OpenURL Framework for Context-Sensitive Services," http://www.niso.org/apps/group_public/download.php/6640/The OpenURL Framework for Context-Sensitive Services.pdf, p. 36-37. The allowed fields in the ContextObject Format do not include the url_ver field.
"The OpenURL Framework for Context-Sensitive Services," http://www.niso.org/apps/group_public/download.php/6640/The OpenURL Framework for Context-Sensitive Services.pdf, p. 75 defines the url_ver field as a field of the OpenURL Transports model.
If you agree that the url_ver field does not belong in the COinS, I request that you remove it from the COinS generating function. Our institution creates thousands of COinS and this correction would make our work easier.
Thank you for your consideration of this request.
ref. http://www.zotero.org/support/dev/exposing_metadata/coins
Thank you very much for supporting COinS. We use them extensively.
Previously, we used the COinS generator, http://generator.ocoins.info/, but since OCLC apparently decommissioned the COinS generator, we have begun using Zotero to create COinS for some of the many publications we host.
I noticed that the Zotero COinS generator begins the ContextObject with "url_ver=Z39.88-2004&" The COinS generator began the ContextObject with "ctx_ver=Z39.88-2004" and omitted the url_ver field. I believe the url_ver field should be omitted from the COinS. This is based on the following sources:
The COinS description, http://ocoins.info/, "Specification : OpenURL ContextObject in SPAN (COinS)- Embedding Citation Metadata in HTML,"
"To add a COinS to an HTML document, put a NISO 1.0 "ContextObject" into the "title" attribute of an HTML span element with class attribute set to "Z3988". A brief guide to the OpenURL 1.0 ContextObject, http://ocoins.info/cobg.html, is available.
Example
OpenURL COinS:
<span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.issn=1045-4438"></span>"
The "Brief guide to Implementing OpenURL 1.0 Context Object for Journal Articles," http://ocoins.info/cobg.html, states,
"Here's the smallest amount of information that you need to know to make correct, minimized, NISO OpenURL 1.0 ContextObject for journals and journal articles:
a 1.0 OpenURL ContextObject using the "journal" metadata format can be made as follows
ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&<key1>=<value1>&<key2>=<value2>&...&<key2>=<value2>
If you append a ContextObject to the end of <baseurl>?url_ver=Z39.88-2004&, you get a valid 1.0 OpenURL link.<baseurl> is the address of an OpenURL link service.
ctx_ver=Z39.88-2004 says "this is a version 1.0 OpenURL ContextObject"..."
More formally, the NISO 1.0 KEV ContextObject Format in is defined in "The OpenURL Framework for Context-Sensitive Services," http://www.niso.org/apps/group_public/download.php/6640/The OpenURL Framework for Context-Sensitive Services.pdf, p. 36-37. The allowed fields in the ContextObject Format do not include the url_ver field.
"The OpenURL Framework for Context-Sensitive Services," http://www.niso.org/apps/group_public/download.php/6640/The OpenURL Framework for Context-Sensitive Services.pdf, p. 75 defines the url_ver field as a field of the OpenURL Transports model.
If you agree that the url_ver field does not belong in the COinS, I request that you remove it from the COinS generating function. Our institution creates thousands of COinS and this correction would make our work easier.
Thank you for your consideration of this request.
ref. http://www.zotero.org/support/dev/exposing_metadata/coins
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
Open Worldcat uses url_ver in their COinS, Harvard's Hollis uses ctx_ver
That does make me wonder how much and where that ever matters?
Thanks,
Alice
https://github.com/zotero/zotero/blob/3.0/chrome/content/zotero/xpcom/openurl.js#L92
Zotero uses the same code to encode openURL requests, so it doesn't look like one could just take the url_ver out there.
Considering that this is done in some very common implementation of COinS like Worldcat, I'm going to leave this alone unless there is any indication that this will ever break anything. My guess would be that using url_ver and ctx_ver makes this more universally recognized.