Difference between revisions of "FactGrid:Troubleshooting"

From FactGrid
Jump to: navigation, search
(Requests for search scripts)
(pdf and other uploads)
Line 66: Line 66:
=== pdf and other uploads ===
=== pdf and other uploads ===
that should be a switch in the LocalSettings but might also be a database issue.
that should be a switch in the LocalSettings but might also be a database issue.
Uploads fail with this note >Could not open lock file for "mwstore://local-backend/local-public/6/65/test.jpg".<
=== Wikidata context help when creating an entry not available on FactGrid ===
=== Wikidata context help when creating an entry not available on FactGrid ===

Revision as of 13:55, 14 March 2019


Advice: best practice data structures

Repeated information - avoid it or go for it?

We have some 7000 documents in the database. Each document has an author, most documents have recipients and most documents mention other persons.

Organising Bode's data set Johann Joachim Christoph Bode (Q133): should we list all these documents in three sections? It might be interesting to do this because this is the point at which we show that we have far more information on the man than any other database.

I am otherwise not to eager to begin this because this was the reason why we left the Wiki and went for the database: The ideal situation is that we have every fact only once in the database. A data sheet on Bode should fill the "Bode as Author" section with a look into the database. Once we start creating lists we have to make sure that they are all constantly up to date and well organised - and a Bode data sheet with a list of 1123 documents he received will no longer be funny.

The ideal situation is a split of functions: A Bode page is created in data base retrievals. You geht the list as soon as you click at "more" freshly made from the data base. (There is a tendency to use Wikibase much like a Wikipedia page: have everything on Bode on "his page" and understand that the dataset Johann Joachim Christoph Bode (Q133) is all we know about Bode...)

Membership information: have the information on person? on the organisation or on an intermediate membership item?

We have about 1350 Illuminati search. Is being a member a personal thing, to be stated in the person's data set? Is it a thing on the account of the Order to be stated here Order of the Illuminati (Q10677) - or shall we create items for each membership and refer to these items on both sides, person and organisation?

A particular problem is that mere membership information will not be the end of the story. Members progress in the order, they get degrees and reach positions. We will not be able to list these details as qualifiers of the respective membership (member of the Illuminati, begin date, place, proposed by, advanced to position x, date... [Wikibase will list all dates together])

Membership items could be complex but would they be operable? Would users know what to look for? --Olaf Simons (talk) 10:45, 20 November 2018 (CET)

Changing entities and cuts through time

See Münchner Buchhandel 1500–1850 at Wikipedia for the problem.

The Publishing House of Moritz Georg Weidmann becomes eventually the Olms Verlag - if we treat this as one company - how do we create different references for different times? Books have different imprints decade after decade - especially with the early modern practice to use the publishers' personal names in the imprints. Our system must be able to make sense of practically any imprint we find - and it should at the same moment understand how the changing imprint information is actually connected to existing companies. Munich does not have 57 companies from 1500 to 1850 but six under changing names.

  • How do we give the proper picture in queries with time frames (tell me how many bookshops Munich had in 1700)?
  • How do we best organise data on an item that goes from 1500 to the present?
  • Should we create different item under each name and state how these items are related?
  • Should we create one idem and state the changing names with begin/end information (sound better because a lot of information like the location might be stable)?

The same problem occurs with addresses. A city quarter can be torn down, the new quarter gets old street names - but are these still the same addresses? (They might have new geographic coordinates).

What should we do with our 1500 transcripts of documents?

We are in need of a good place to offer transcripts (and eventually: scans).

Would Q22976 be a good place for the transcript of Contract between Christian Weidmann and August Bohse for 'Die unglücklich verliebte Europäerin Constantine', Jena, 1693-08-10 (Q22976)?

Would it be better to have a direct input field for the transcript of full pages?

Could the reasonator as a standard unser interface grab transpripts from such wiki pages?

Could we use the Wikisource extension to offer scans side by side?


Daniel Mietchen hinted at Scholia https://tools.wmflabs.org/scholia/ and how that could change many of our problems. We could here use a software solution that embeds SPARQL queries. It could also embed the transcripts of texts which we have to present. We would basically decide how many sorts of database objects we have and compose templates of the searches they are supposed to embed. Question remains: who would compose this for us. (On the design front: it is not as cohesive as Magnus Manske's Reasonator.) --Olaf Simons (talk) 16:34, 27 November 2018 (CET)

Specific problems of our Wikibase Installation

GND Identifiers do not link

See Johann Joachim Christoph Bode (Q133). Why does the GND number not linkt to the GND as in Wikidata?

Wikidata has a function that allows quoting items via {{}} template, can we do that as well?

Does not seem to work... Side aspect: Wikidata states Q-Numbers like Q123, we state "Item:Q123" (and I have begun to link transcripts to the Q-Pages) --Olaf Simons (talk) 12:20, 23 November 2018 (CET)

Description 250 character limit

We have extended descriptions wherever we have foreign data inputs. Daniel Mietchen said we can modify the character limits on our own Wikibase instance - would be good to allow perhaps 1500 characters. --Olaf Simons (talk) 12:26, 23 November 2018 (CET)

Time: Hours and Minutes cannot be stated

We were trying to state events on single days, and did not manage to state hours or minutes, though the Sofware seems to offer the option. --Olaf Simons (talk) 12:26, 23 November 2018 (CET)

pdf and other uploads

that should be a switch in the LocalSettings but might also be a database issue.

Uploads fail with this note >Could not open lock file for "mwstore://local-backend/local-public/6/65/test.jpg".<

Wikidata context help when creating an entry not available on FactGrid

Wikidata offers complex context help when users want to create items like a biography - questions we would like to answer as well. Can we have the same?

Commons images not displayed on FactGrid-Item Views

...though we can integrate them in Wiki pages we create.

Foreign Language Labels

Our database is on English as the default language. Those who feed data into the base are - presently - mostly German. An English label is visible and searchable in German. Can we have the same additionally vice versa: that a missing English label is automatically filled with the existing German label?

QueryService related problems

QueryService gives January 1 as default answer for full year dates

If we give a full year (e.g. "date of birth") the Query Service will state that January 1 as the date.

QueryService gives output with wd:Q123 numbers

though the links do actually go into the FactGrid resource

QueryService example searches are Wikidata searches and do not work on our database

though the links do actually go into the FactGrid resource

Weird Results No.1

The following search should show us where Gotha's bakers were living

works fine with the master bakers but here the same on merchants with a totally messy result...

Weird Results No.2

We are trying to step from "given names" as string <given name (string)> (P88) to given names as individual items.

This query should tell us the entries we still have to change -

  • yet it gives us loads of obsolete entries and
  • it cannot be persuaded to add the place in sequence place in sequence (P101) information which we wold try to keep with the new entries to make.

Tools/features one would like to have

Our Reasonator as Standard Interface

We would like to offer our Reasonator-Installation as standard interface for people who are just looking for information. So far it does not really seem to work...

One of the problems is that our instance looks for Friedrich Christian Rudorf (Q969) instead of Q969

A tool to grab and import (selected) Wikidata information

If we have data on a FactGrid Item on Wikidate - could on think of a tool that can be used to grab these data as a set and to convert selected statements into FactGrid statements?

A multilingual interface to just offer information

The ideal development would be an additional tab on all wikibase-items. If you search for Johann Sebastian Bach you get a person's page that extracts information from the J.S. Bach data set and through additional searches. Bach's works will be listed on request - not from the information the specific Q-item is providing but from a database search: list all items with Bach as composer. List all documents with J.S. Bach as author. List all documents with J.S. Bach as receiver... Users get these lists only on request. The J.S. Bach display tells us that we can run this search and feed the information under the present header.

An option to feed information into historical maps

One would love to offer links to Gotha addresses of different centuries and decades and one would have to use different maps for this purpose. Gotha today has housing areas for about 50.000 inhabitants. Gotha in 1800 ended basically with the city walls that were just torn down. We do not yet have the expertise to present visual information on maps other than the default Open Street Map interface.

A recipe how to create Info-Boxes based on FactGrid Information

We need these Boxes for pages like this one (imported from our old Wiki): Q6611. The header information on author, title, source etc., is here handwritten so far. The cool solution will be a standard table with central metadata from the respective data set (of the same Q-number), so that changes of information will only be done in the database and spread from there to pages.

Requests for search scripts

Organisations that share members

It would be interesting to get an idea of organisations and their vicinity or adversity - also: their potential to succeed each other.

Cumulative personal Timeline

A cumulative timeline that which pieces together all the information we have on a person: Documents by this person per day, letters sent to this person, mentionings, meetings he/she took part in, events he/she witnessed etc.

Specific FactGrid wishes

Important in joint ventures.



Important gain a more independent position in the eyes of university, library and archive people.

An interface to move the The Gotha Illuminati Research Base into the FactGrid

The The Gotha Illuminati Research Base https://projekte.uni-erfurt.de/illuminaten/Main_Page is a conventional media wiki and we should win a superior functionality here on the FactGrid.

A clearer idea of how we would like to be quoted

FactGrid datasets have specific research statements - but how do we want them to be referred to in footnotes? See Hermann Schüttler/ Reinhard Markner, Research on the Illuminati correspondence (1998–2007) (Q11305)

Data we should like to have

  • Matrikel of German universities
  • Logis-Verzeichnisse Göttinger Studenten (halbjährlich)