Wikidata:Primary sources tool/ही

प्राथमिक स्रोत उपकरण डेटा दान के लिए विकेटा के लिए एक क्रियान्वयन कार्यप्रवाह के लिए अनुमति देता है, जहां विकिडा संपादक समुदाय को दी गई आंकड़ों की समीक्षा, संपादित करने या अस्वीकार कर सकते हैं। वर्कफ़्लो विकिडाटा में एकीकृत है।

एक कोशिश करें

1. go to your Gadgets;
2. tick the Primary Sources item (Wikidata-centric section) and press the Save button at the bottom of the page;
3. on the left sidebar, click on the gear icon, next to the Random Primary Sources item link;
4. select a dataset, such as strephit-confident, soweego, or freebase;
5. you can test the tool in 3 ways:
   1. the Primary Sources list sidebar link (Tools section)
      • click on the Load button for a quick grasp of the dataset content;
      • optionally insert a property id to filter statements;
   2. the Random page sidebar link shows an Item to be curated;
   3. an Item of your choice.

N.B.: Wikidata gadgets are written in JavaScript, so make sure you have allowed its execution in your browser.

प्राथमिक स्रोत उपकरण उतार-चढ़ाव का प्रस्ताव

प्राथमिक स्रोत उपकरण (पीएसटी) का पहला और वर्तमान संस्करण Google द्वारा फ्रीबेस के दान से उपजी है। Based on community feedback collected since its deployment as a Wikidata gadget, the StrepHit team submits here a radical uplift proposal, which will lead to the next version of the tool.

प्राथमिक स्रोतों टूल का बीटा संस्करण

Please note that all the mock-ups referenced in this document are accessible at phab:M218.

वर्तमान कोड आधार

• Back end: written in C++, with SQL storage, deployed as a Web service via REST APIs;
• front end: written in JavaScript, deployed as a Wikidata gadget.

लक्ष्य

The general goal is to make the tool self-sustainable. To achieve this, the highest priority is given to:

• Web standards;
• stability, i.e., choices driven by the Wikidata stable interface policy;
• programming languages adoption by the Wikimedia community.

In addition, the tool should also become the preferred choice for data releases from third-party providers. This makes even more important the need for a standard release procedure.

उपयोगकर्ता वर्कफ़्लो

उपयोगकर्ता टूल द्वारा सुझाए गए एक नए कथन को अनुमोदित या अस्वीकार कर सकता है: # एक आइटम पृष्ठ दिया गया है, सुझाए गए कथन को नीले रंग की पृष्ठभूमि के साथ हाइलाइट किया गया है;

1. उपयोगकर्ता "" दावे का अनुमोदन करें "" या क्रमशः "" दावे को अस्वीकार करें "" लिंक पर क्लिक करके इसे स्वीकार या अस्वीकार कर सकता है;
2. इसके बाद, पेज पहले मामले में नए बयान के साथ या दूसरे में इसके बिना अपडेट होगा।

Identically, the tool can suggest new references for an existing statement:

1. the new reference is highlighted with a blue background;
2. the user can approve or reject it by clicking either on the approve reference or on the reject reference links respectively;
3. the user can also see a preview tooltip that shows where the source came from by clicking on preview reference;
4. if the dataset contains fine-grained provenance information, e.g., the text snippet where the suggested statement was extracted, the preview tooltip will highlight that exact piece of information;
5. in case the interaction between the front end and the back end is not smooth, a tooltip will show up with an alert message.

प्राथमिक स्रोत विन्यास

1. When the user clicks on the gear icon next to the Random Primary Sources item link (cf. the section below) in the main menu on the left sidebar, a modal window will open;
2. the user can search and select which dataset to use;
3. essential information is shown, namely Dataset description, Missing statements and Total statements;
4. the user can either Save or Cancel the new settings.

यादृच्छिक प्राथमिक स्रोत आइटम

1. The user can jump to a random Item containing suggested statements by clicking on the Random Primary Sources item link located in the main menu on the left sidebar;
2. the item will be randomly picked from the datasets selected in the Primary Sources configuration.

प्राथमिक स्रोतों को ब्राउज़ करें

1. The user can browse through the suggested statements grouped by property by clicking on the appropriate property link below the Browse Primary Sources menu on the left sidebar;
2. the user can move back to the top of the page by clicking on the back to top link right below the Browse Primary Sources menu on the left sidebar.

फ़िल्टर-आधारित उपकरण

A similar workflow applies to a filter-based tool, located in the Tools menu of the left sidebar.

1. When the user clicks on the Primary Sources filter link (currently Primary Sources list), a modal window will open;
2. the user can view a table of suggested statements with eventual references by building filters in several ways:
   • Domain of interest: the user starts typing a domain he or she is interested in and gets autocompletion based on simple constraints, typically the instance of (P31) property. For example, list all the Items that are a chemical compound (Q11173);
   • Property: the user starts typing a property he or she is interested in and gets autocompletion based on property labels. This filter then only shows suggested statements with the given property. For instance, list all the date of birth (P569);
   • SPARQL Query: this filter is intended for power users and accepts arbitrary SPARQL queries;
   • Source language: shows only statements in the selected language;
   • Dataset: lets the user pick one or more specific dataset to use, similarly to Primary Sources configuration.

After building the filters, the tool shows a table of statements, where the user can either approve or reject suggestions, after a preview of the reference source, as per the "User workflow" section. The approval or reject actions can be blocked if the source preview is not opened.

वास्तुकला

StrepHit के आधार पर विकीडाटा प्राथमिक स्रोतों के टूल संस्करण 2 के लिए सामान्य वास्तुकला प्रस्ताव।

बैक-एंड कार्यान्वयन

डेटा प्रारूप

The tool currently accepts datasets serialized in QuickStatements (Q20084080). While it is indeed a very compact format, useful to upload large datasets, it is totally non-standard: the only available documentation is contained in the QuickStatements service page itself. Hence, we foresee the support of stable formats for both the self-sustainability of the project and a standardized data donation workflow. Still, we will keep the QuickStatements support.

Datasets from third-party providers should be serialized in RDF and follow the Wikidata RDF data model. We believe this is the most standard way for 2 reasons:

1. RDF is a mature Web standard, being a W3C recommendation since 1999;
2. The Wikidata RDF export format is claimed to be stable.

मुख्य घटक

Given these premises, a Wikidata Query Service instance is a good fit for the back end, since it:

• uses a RDF triple store, i.e., Blazegraph as the storage engine;
• is claimed to be a stable Wikidata public API;
• is written in Java, probably a more adopted programming language compared to the current implementation in C++;
• has facilities to upload datasets in Wikidata RDF dump format;
• exposes APIs to access data via SPARQL, specifically useful for both the domain filter and the query text box features.

The main tool will support full statements, while the filter-based tool should be fed with truthy statements.

अंतर्ग्रहण एपीआई

अंतर्ग्रहण एपीआई तीसरे पक्ष के डेटा प्रदाताओं के साथ बातचीत के लिए जिम्मेदार है। इनकमिंग डेटासेट पहले विकीडाटा आरडीएफ डेटा मॉडल के खिलाफ मान्य हैं। यह तब डेटासेट के लिए निम्नलिखित सुविधाएं प्रदान करेगा:

• अपलोड;
• अद्यतन करें;
• गिरना।

क्यूरेशन एपीआई

अवधि एपीआई विकीडाटा उपयोगकर्ताओं के साथ 2 मुख्य सेवाओं के साथ बातचीत के लिए जिम्मेदार है। यह बैक-एंड स्टोरेज में अस्वीकार किए गए सुझावों को जोड़ने और फ़्लैग करने के लिए दावे सुझाएगा।

फ्रंट-एंड कार्यान्वयन

The main self-sustainability goal is to avoid breaking the front end whenever a change is made in the Wikidata user interface. To achieve this, the current gadget will become a MediaWiki extension for Wikibase (Q16354758). A major refactoring of the code base is essential and will:

• include unit tests. Failures are expected in case of changes in the Wikidata user interface, and will break the Wikidata build instead of breaking the tool;
• make a clear distinction between the interaction with the back end and the users;
• port the HTML templates.

The code will be split into the 2 typical components of a MediaWiki extension, written in PHP and JavaScript respectively.

PHP घटक

PHP घटक केवल विस्तार विन्यास के लिए जिम्मेदार होगा। शेष सभी को जावास्क्रिप्ट घटक द्वारा नियंत्रित किया जाएगा।

जावास्क्रिप्ट घटक

जावास्क्रिप्ट घटक होगा:

• अंतिम टेम्पलेट रेंडरिंग बनाएँ। अधिक विशेष रूप से, यह आवश्यक होने पर मौजूदा आइटम स्टेटमेंट के लिए टेम्पलेट को जोड़ देगा;

• उपयोगकर्ता के साथ बातचीत संभाल। अधिक विशेष रूप से, यह होगा:
  • किसी अनुमोदित दावे या संदर्भ के अनुमोदन या अस्वीकृति पर टूल बैक एंड को सूचित करें;
  • मीडियाविकि एपीआई के माध्यम से विकीडाटा के लिए अनुमोदित दावा या संदर्भ जोड़ें;
• implement the features described in "User workflow" section.