Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
dev:make_your_site_zotero_ready [2011/04/14 23:21] – rmzelle | dev:make_your_site_zotero_ready [2011/04/15 11:36] – rmzelle | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Exposing Your Metadata ====== | + | See [[/ |
- | + | ||
- | 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. | + | |
- | + | ||
- | 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' | + | |
- | + | ||
- | ===== Zotero-Ready Web Applications ===== | + | |
- | + | ||
- | The easiest way to expose bibliographic metadata is to use a web application that comes with this feature, or offers it through a plugin or minimal configuration. Examples are the content management systems | + | |
- | + | ||
- | Zotero-compatible OPAC (Online Public Access Catalog) software packages for libraries, archives, and museums include: | + | |
- | + | ||
- | * Aleph | + | |
- | * DRA | + | |
- | * Dynix | + | |
- | * [[http:// | + | |
- | * GEAC | + | |
- | * InnoPAC | + | |
- | * [[http:// | + | |
- | * SIRSI | + | |
- | * TLC/ | + | |
- | * Voyager (WebVoyage) | + | |
- | * VTLS | + | |
- | + | ||
- | ===== Using an Open Standard for Exposing Metadata ===== | + | |
- | + | ||
- | Alternatively, | + | |
- | * **Embedded RDF** | + | |
- | * **COinS** The [[http:// | + | |
- | * **unAPI**. As described on the [[http:// | + | |
- | * **MODS XML**. Developed by the Library of Congress, [[http:// | + | |
- | * **MARC**. An older, flat format, MARC is only recommended if your application can already generate it. | + | |
- | * **Zotero/ | + | |
- | * **[[http:// | + | |
- | + | ||
- | ===== Zotero Web Translators ===== | + | |
- | + | ||
- | Exposing bibliographic metadata through an open standard is very powerful (and also benefits non-Zotero users!). However, if you have little control over the way your website is build, you may have to [[dev/translators|create a Zotero web translator]] for Zotero-compatibility. Translators have some downsides: apart from the fact that they are a Zotero-specific solution, translators can break easily if the structure of the targeted website changes. An advantage is that translators can easily attach related content when saving metadata (e.g. a translator can save the full-text PDF along the bibliographic metadata of a scientific paper). | + |