Differences

This shows you the differences between two versions of the page.

--- dev:exposing_metadata [2022/03/19 00:32] – [Using an Open Standard for Exposing Metadata] abejellinek
+++ dev:exposing_metadata [2024/02/24 01:59] (current) – [Exposing Your Metadata] dstillman
@@ Line 1: / Line 1: @@
 ====== Exposing Your Metadata ======
-Whether you are a publisher of a scientific journal, operate a news site, or are a blogger, Zotero users will be eternally grateful if you expose bibliographic metadata on your website.
+Do you operate a website containing resources people might want to save to their Zotero libraries?
-In your decision to expose metadata, it is important to identify the object of interest: this can be the webpage itself (e.g. a page on a newspaper's website showing a article), or the resources described on the webpage (e.g. a page of a library catalog showing bibliographic records).
+Zotero has over 700 [[:translators|translators]] that allow it to save high-quality bibliographic metadata from across the web, but the best translator is no translator at all: by exposing metadata on your site in a format that Zotero already understands, you can ensure that Zotero users can always save accurate bibliographic information and correctly cite the materials on your site.
+When exposing metadata, it's important to identify the object of interest: this can be the webpage itself (e.g., a page on a newspaper's website showing a article) or the resources described on the webpage (e.g., a page of a library catalog showing bibliographic records).
 ===== Zotero-Ready Web Applications =====
@@ Line 28: / Line 30: @@
 Alternatively you can directly edit your HTML code of your webpage, using one of the following open standards, to expose your metadata:
-    * **Embedded Metadata** The <meta> tags in the header of many webpages will be parsed and used by Zotero. This fairly standard embedding of RDF metadata can use any RDF vocabularies; Zotero supports most major RDF vocabularies used for bibliographic metadata. For details on this approach, see the [[http://dublincore.org/documents/2008/08/04/dc-html/|Dublin Core description]]. The translator will also interpret metadata expressed in the [[http://scholar.google.com/intl/en/scholar/inclusion.html|Google/Highwire key-value system]]. Zotero supports the following values for the <meta> ''name'' attribute from the Highwire vocabulary:
+    * **Embedded Metadata** The <meta> tags in the header of many webpages will be parsed and used by Zotero. This fairly standard embedding of RDF metadata can use any RDF vocabularies; Zotero supports most major RDF vocabularies used for bibliographic metadata. For details on this approach, see the [[https://www.dublincore.org/specifications/dublin-core/dc-html/2008-08-04/|Dublin Core description]]. The translator will also interpret metadata expressed in the [[http://scholar.google.com/intl/en/scholar/inclusion.html|Google/Highwire key-value system]]. Zotero supports the following values for the <meta> ''name'' attribute from the Highwire vocabulary:
         * Title: ''citation_title''
         * Date: ''citation_date'' (preferred), ''citation_publication_date'', ''citation_cover_date'', ''citation_online_date'', ''citation_year''
@@ Line 77: / Line 79: @@
 ===== Force Zotero to refresh metadata =====
-Websites for which metadata changes without a page reload should fire a ZoteroItemUpdated event to tell Zotero to re-detect metadata on the page. This is supported in Zotero 3.0 and later.
+Websites for which metadata changes without a page reload should fire a ZoteroItemUpdated event to tell Zotero to re-detect metadata on the page.
 <code javascript>