Upgrade StorageWould love to be able to export citation type "website" to COinS
The dev:exposing_metadata page [ https://www.zotero.org/support/dev/exposing_metadata ] suggests that one way to make a web page's metadata accessible to Zotero is to use Zotero itself to create a COinS object (or objects) which is embedded into the web page. Since I'm working on my own personal web page right now and looking for ways to expose the individual web pages as bibliographic objects -- in part to Zotero itself -- I think it would be great if I could use Zotero to create the required Z3988 class objects.
Ideally, my workflow would look something like this.
1. Create a web page for my site.
2. Import it into Zotero, perhaps by using the "New Item from Current Page" button.
3. Correct any inaccuracies and flesh out incomplete information by using Zotero's interface.
4. Use Zotero's export function to create a COinS object, and then embed that into the web page itself.
Since I'm already using some microformats on my web pages, some information gets captured already, but it needs to be cleaned up. (Incidentally, I *really* appreciate the "embedded metadata translator.)
However, COinS objects that are exported from "web page" items are blank. (I'm using Zotero 4.0.12 with Bodhi Linux and the MATE desktop environment; I've just verified that my site translators are up to date.)
This thread [ https://forums.zotero.org/discussion/31226/some-item-type-wont-export-as-coins/ ] seems to suggest that the problem is that not all Zotero item types can be exported as COinS, and that "web page," specifically, is one of the ones that doesn't work.
What I'd like to suggest is that I personally would rather have the item exportable as COinS in suboptimal situations (e.g., listed as generic "document") than not at all. (=
Ideally, my workflow would look something like this.
1. Create a web page for my site.
2. Import it into Zotero, perhaps by using the "New Item from Current Page" button.
3. Correct any inaccuracies and flesh out incomplete information by using Zotero's interface.
4. Use Zotero's export function to create a COinS object, and then embed that into the web page itself.
Since I'm already using some microformats on my web pages, some information gets captured already, but it needs to be cleaned up. (Incidentally, I *really* appreciate the "embedded metadata translator.)
However, COinS objects that are exported from "web page" items are blank. (I'm using Zotero 4.0.12 with Bodhi Linux and the MATE desktop environment; I've just verified that my site translators are up to date.)
This thread [ https://forums.zotero.org/discussion/31226/some-item-type-wont-export-as-coins/ ] seems to suggest that the problem is that not all Zotero item types can be exported as COinS, and that "web page," specifically, is one of the ones that doesn't work.
What I'd like to suggest is that I personally would rather have the item exportable as COinS in suboptimal situations (e.g., listed as generic "document") than not at all. (=
Dan, Simon, Aurimas - do you have any thoughts on this? COinS specs
http://alcme.oclc.org/openurl/servlet/OAIHandler/extension?verb=GetMetadata&metadataPrefix=mtx&identifier=info:ofi/fmt:kev:mtx:book
allow for "document" and "unknown" in genre. I think just falling back to that rather than exporting empty COinS makes a lot of sense - or is there a good reason _not_ to (maybe connected to the whole OpenURL origin of COinS).
https://github.com/zotero/zotero/pull/472