Skip to main content
SimilarExport ZIP
100%

Zotero converter for Wikidata Quick Statements

✓ Published0🌍 Public
CCliffordAnderson
Last edited Aug 17, 2020
Created on Aug 14, 2020

This example presents a Zotero translator that converts bibliographic records into QuickStatements commands for Wikidata, enabling direct import of academic citations. The code maps Zotero item types to Wikidata entity IDs (e.g., `Q571` for book) and assigns properties via rapid-fire tab-separated statements like `P356` for DOI. It uses a JavaScript object-based mapping for languages and identifiers, and constructs commands using string concatenation within a custom `addStatement` function. No external visualization libraries appear; the output is a text file of structured statements for the Wikidata batch editing tool.

AI-generated description

Similar vizzes

Loading thumbnail…

Get Zotero JSON from API

This example demonstrates how to retrieve and parse Zotero library items as structured XML from the Zotero API. It uses the XQuery `fetch:text` function to download JSON data from the API endpoint, then parses that JSON with `json:parse`. The code extracts all `note` elements from the parsed data and converts each into an XML fragment using `fn:parse-xml-fragment`. This approach shows a direct pipeline from API response to manipulable XML nodes, useful for further processing or transformation in an XQuery environment.

CCliffordAnderson
52% match
Loading thumbnail…

Wikidata for Theological Librarians

This example demonstrates how theological librarians can use Wikidata to explore and visualize interconnected scholarly data. It shows a SPARQL query interface that retrieves information about theologians, their works, and associated religious concepts, rendered as an interactive network graph. The visualization uses D3.js’s force-directed layout to position nodes and links, with hover tooltips revealing entity details. Data is sourced live from Wikidata’s public endpoint, while the code employs the `d3.forceSimulation` API for physics-based layout and custom SVG rendering for clarity.

CCliffordAnderson
52% match
Loading thumbnail…

Wikidata RPC for NetsBlox

This visualization demonstrates how Wikidata can be accessed as a Remote Procedure Call (RPC) service within NetsBlox, a visual programming environment. Built with Vue and rendered on HTML5 Canvas, the project pairs an XML room definition with a markdown guide that explains Wikidata's code-block integration. The example uses WebGL for rendering and focuses on Berlin-related Wikidata queries, showing real-time data retrieval from the live knowledge base directly within NetsBlox's block-based interface. The visualization is accompanied by an animated GIF illustrating the code blocks in action, making it a practical reference for developers working with semantic data in educational or prototyping contexts.

CCliffordAnderson
49% match
Loading thumbnail…

{$doc/RecordTitle/text()}

This example extracts bibliographic records from a collection of quarterly publications and serializes them into CSV format. It queries a local XML document store containing full-text articles, capturing fields such as title, publication, volume, issue, date, pagination, and a document link. The XQuery 3.1 script uses the `csv:serialize` function to convert the generated `element csv` tree into a delimited text file, demonstrating a straightforward data-wrangling pipeline for export and downstream analysis.

CCliffordAnderson
48% match
Loading thumbnail…

Prompt for marking up TEI P5

This example demonstrates a prompt-driven workflow for converting raw historical text into TEI P5 XML with named entity markup. It shows how the system identifies personal names, queries Wikidata for matching entities, and assigns attributes like @ref, @full, and @cert for disambiguated references. The process relies on the Wikidata API for entity resolution and uses TEI's controlled vocabulary for confidence levels. The output is a self-contained XML fragment, with unidentifiable names marked as unknown. This approach highlights the integration of external linked-data sources into scholarly text encoding, emphasizing automated authority control and metadata enrichment.

CCliffordAnderson
48% match
Loading thumbnail…

SPARQL queries for the Semantic Web Working Group

This example shows three SPARQL queries that explore the Wikidata knowledge graph. One query counts paintings containing cats versus dogs to test a hypothesis about which animal appears more frequently. Another generates an ImageGrid view of Rembrandt’s artworks using the defaultView directive, while a third lists Spanish painters and sample images of their work. The queries use standard SPARQL syntax with property paths (wdt:P135/wdt:P279?), label service calls, and BIND for computed values. Results render directly in Wikidata’s query service interface.

CCliffordAnderson
48% match
Loading thumbnail…

For Zach Johnson

This example transforms a raw XML extract of the Jesse Wills finding aid into structured archival units using XQuery 3.1. The code loads a source document from a GitHub gist, then uses a tumbling window to pair adjacent XML elements into `c02` records. It tokensizes `unittitle` text by semicolons and periods, classifies segments as folder containers or dates, and constructs `did` elements with normalized `unitdate` and `unittitle` values. The result is a cleaned, hierarchical data structure suitable for downstream visualization, though no rendering library is invoked here.

CCliffordAnderson
47% match
Loading thumbnail…

Pandoc bash conversion

This visualization demonstrates a user’s workflow of converting and renaming files across directories using shell commands. It shows three distinct bash operations: deleting HTML files in a specific folder, converting sociology files to DOCX via Pandoc, and renaming XML files to HTML using the `rename` utility. The code relies on standard shell scripting constructs and the Pandoc command-line tool, with no graphical or interactive rendering libraries like D3 or Three.js. The data source is the local file system paths referenced in each command, and the rendering approach is purely textual—showing the raw bash scripts rather than any visual output.

CCliffordAnderson
45% match