Difference between revisions of "FactGrid:Troubleshooting"

From FactGrid
Jump to: navigation, search
(Requests for search scripts)
(Tinyurl no longer supported =)
 
(46 intermediate revisions by 2 users not shown)
Line 1: Line 1:
* [[Talk:Main Page|Construction Sites]]
+
<p align="right">[[FactGrid:Troubleshooting/archive]]</p>
  
 
== Advice: best practice data structures ==
 
== Advice: best practice data structures ==
=== Repeated information - avoid it or go for it? ===
+
=== Changing entities and cuts through time ===
We have some 7000 documents in the database. Each document has an author, most documents have recipients and most documents mention other persons.
 
  
* [https://database.factgrid.de/query/#SELECT%20%3FDokument%20%3FDokumentLabel%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20%3FDokument%20wdt%3AP2%20wd%3AQ10671.%0A%20%20%3FDokument%20wdt%3AP21%20wd%3AQ133.%0A%7D 375 documents are written by Johann Joachim Christoph Bode].
+
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 with changing owners who give the company names. Our system must be able to make sense of practically any imprint - and it should at the same moment understand how the changing imprint information is actually connected to one and the same company. Munich does not have 57 companies from 1500 to 1850 but six under changing names in this genealogy [https://de.wikipedia.org/wiki/M%C3%BCnchner_Buchhandel_1500%E2%80%931850 Münchner Buchhandel 1500–1850] - and this is an image we want to give on a clear sighted SPARQL-search.
[https://database.factgrid.de/query/#SELECT%20%3FDokument%20%3FDokumentLabel%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20%3FDokument%20wdt%3AP2%20wd%3AQ10671.%0A%20%20%3FDokument%20wdt%3AP28%20wd%3AQ133.%0A%7D 1123 documents have Bode as first recipient]
 
* [https://database.factgrid.de/query/#SELECT%20%3FDokument%20%3FDokumentLabel%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20%3FDokument%20wdt%3AP2%20wd%3AQ10671.%0A%20%20%3FDokument%20wdt%3AP33%20wd%3AQ133.%0A%7D 108 documents mention Bode]
 
  
Organising Bode's data set [[Item: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.
+
* Should we create different items 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)?
  
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 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).
  
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 [[Item:Q133]] is all we know about Bode...)
+
:Daran scheiden sich die Geister... Das ist ein klassisches Ontologieproblem. Man kann es so oder so machen. Denny könnte eine gute Person sein das mal für deinen genauen Fall durchzudiskutieren und zu schauen ob eins mehr Sinn macht. --[[User:Lydia Pintscher]]
  
=== Membership information: have the information on person? on the organisation or on an intermediate membership item? ===
+
=== What should we do with our 1500 transcripts of documents? ===
We have about 1350 Illuminati [https://database.factgrid.de/query/#SELECT%20%3FIlluminatenorden%20%3FIlluminatenordenLabel%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20%0A%20%20%0A%20%20%3FIlluminatenorden%20wdt%3AP91%20wd%3AQ10677.%0A%7D 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 [[Item: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])
+
We have started to put the transcript of [[Item:Q22976]] on [[D-Q22976]]. Was that a good idea? (we want the transcript to appear in full text search), yet we would rather have it on one page with all the meta data.
  
Membership items could be complex but would they be operable? Would users know what to look for? --[[User:Olaf Simons|Olaf Simons]] ([[User talk:Olaf Simons|talk]]) 10:45, 20 November 2018 (CET)
 
  
=== Changing entities and cuts through time ===
+
Could the reasonator (as a standard unser interface) grab transpripts from such wiki pages?
  
See [https://de.wikipedia.org/wiki/M%C3%BCnchner_Buchhandel_1500%E2%80%931850 Münchner Buchhandel 1500–1850] at Wikipedia for the problem.
+
Could we use the Wikisource extension to offer scans side by side?
  
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.
+
:Ich kenne mich leider mit Wikisource nicht aus. Tpt (thomas@pellissier-tanon.fr) hat davon und von Wikidata sehr viel Ahnung und kann wahrscheinlich am sinnvollsten was sagen. --[[User:Lydia Pintscher]]
  
* How do we give the proper picture in queries with time frames (tell me how many bookshops Munich had in 1700)?
+
=== Scholia ===
* 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).
+
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.) --[[User:Olaf Simons|Olaf Simons]] ([[User talk:Olaf Simons|talk]]) 16:34, 27 November 2018 (CET)
  
=== What should we do with our 1500 transcripts of documents? ===
+
:Sowas sollte jeder vernünftige php coder hinbekommen. --[[User:Lydia Pintscher]]
  
We are in need of a good place to offer transcripts (and eventually: scans).
+
== Specific problems of our Wikibase Installation ==
 +
=== "Item:Q123" or direct "Q123"===
 +
Unlike Wikidata FactGrid states Items as "Item:" in the URL. This might be the cause of incompatibilities as we see them in our Reasonator interface. (Reasonator apparently expects the Q123 link where we have the "Item"-link
  
Would [[Q22976]] be a good place for the transcript of [[Item:Q22976]]?
+
* https://database.factgrid.de/reasonator/#/Q123 click the link into the database item to see the problem.
  
Would it be better to have a direct input field for the transcript of full pages?
+
:Dafür habe ich dir ein Ticket aufgemacht: https://phabricator.wikimedia.org/T223548 --[[User:Lydia Pintscher]]
  
Could the reasonator as a standard unser interface grab transpripts from such wiki pages?
+
In the headline of item pages that Item ID is shown, but not the name space, e.g. "human (Q7)". In the project name space the name space is shown "FactGrid:Troubleshooting Range", in the main name space and special name space it is not.
  
Could we use the Wikisource extension to offer scans side by side?
+
=== "Item:Q123" or "Item:123" ===
 +
The "Q" is present in every item ID and therefore does not contain extra information. It should probably be removed. Also, it would be easier for international use to only have numbers in the item ID.
  
=== Scholia ===
+
=== GND Identifiers do not link ===
 +
See [[Item:Q133]]. Why does the GND number not linkt to the GND as in Wikidata?
  
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.) --[[User:Olaf Simons|Olaf Simons]] ([[User talk:Olaf Simons|talk]]) 16:34, 27 November 2018 (CET)
+
We have the same problem with PND book numbers that should refer into to GBV catalogue.
  
== Specific problems of our Wikibase Installation ==
+
Dafür habe ich dir ein Ticket aufgemacht: https://phabricator.wikimedia.org/T223552 --[[User:Lydia Pintscher]]
=== GND Identifiers do not link ===
 
See [[Item: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? ===
 
=== 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) --[[User:Olaf Simons|Olaf Simons]] ([[User talk:Olaf Simons|talk]]) 12:20, 23 November 2018 (CET)
+
* We can set a [[Q123]] link (that refers to a non existing page.
 +
* We can set an [[Item:Q123]] link - and sometimes we get the title on the ink - but not necessarily (works wel after moving a page and ends after saving it again)
 +
* A {{}} template does not work.
 +
 
 +
:Hast du ein Beispiel auf Wikidata, wo es so funktioniert wie du es haben willst? Dann schau ich es mir an. Das sollte gehen. --[[User:Lydia Pintscher]]
  
 
=== Description 250 character limit ===
 
=== 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. --[[User:Olaf Simons|Olaf Simons]] ([[User talk:Olaf Simons|talk]]) 12:26, 23 November 2018 (CET)
+
Many imports failed since they had descriptions of more than 250 signs. Daniel Mietchen said we can modify the character limits on our own Wikibase instance - would be good to allow perhaps 500-1000 characters.
 +
 
 +
:Die Descriptions sind vor allem zur Disambiguierung gedacht zum Beispiel im Suchfeld rechts oben oder wenn du ein anderes Item in einem Statement verlinkst um sicherzustellen dass du den richtigen Fritz Müller auswählst wenn es 10 davon gibt. Deshalb sind die sehr kurz gehalten und die Beschränkung ist von unserer Seite aus gewollt bisher. Kannst du etwas genauer erklären was du machen willst mit den Descriptions und was da rein soll? Vielleicht ist es besser als ein Statement aufgehoben aber das kann ich noch nicht sagen.
 +
 
 +
:Soweit ich weiß ist das im Moment nicht konfigurierbar.  --[[User:Lydia Pintscher]]
  
 
=== Time: Hours and Minutes cannot be stated ===
 
=== 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. --[[User:Olaf Simons|Olaf Simons]] ([[User talk:Olaf Simons|talk]]) 12:26, 23 November 2018 (CET)
+
We could actually give events (like conference papers) on individual days. The software has the option but it does not work in Wikidata or on our platform.
 +
 
 +
:Die Eingabe von genauen Zeiten ist noch nicht möglich weil das eine Menge Komplexität mit Zeitzonen mit sich bringt. https://phabricator.wikimedia.org/T57755 ist das Ticket dafür. Dem müssen wir uns mal annehmen. --[[User:Lydia Pintscher]]
 +
 
 +
=== Time: Format ===
 +
Currently it says on the bottom of that page "This page was last edited on 6 July 2019, at 18:05." and on in the history "18:05, 6 July 2019" - two different formats no statement found what for. Furthermore in the FG blog and other places formats based on ISO 8601 appear. Proposal: standardize on ISO 8601.
 +
 
 +
=== Time: Seconds not shown in page history ===
 +
In the contributions lists seconds are not shown, so one cannot see in which order edits have been made, even worse, a change that is labeled "current" comes before another one on the same page:
 +
18:05, 6 July 2019 (diff | hist) . . (+236)‎ . . FactGrid:Troubleshooting Range ‎ (→‎"Item:Q123" or "Item:123")
 +
17:50, 6 July 2019 (diff | hist) . . (+63)‎ . . Example (Q...) ‎ (‎Added [en] description: human)
 +
17:50, 6 July 2019 (diff | hist) . . (+64)‎ . . Example (Q...) ‎ (‎Added [de] description: Mensch) ('''current''')
 +
17:49, 6 July 2019 (diff | hist) . . (+1)‎ . . Property talk:P163 ‎ (...)
  
 
=== 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 to be resolved in Erfurt:
 +
 
 +
Uploads fail with this note >Could not open lock file for "mwstore://local-backend/local-public/6/65/test.jpg".<
 +
 
 +
:Bin nicht sicher was da das Problem ist. Da kannst du Lucas glaube ich kurz ansprechen und ihn fragen ob das was ist was im Rechenzentrum gemacht werden muss oder in den Einstellungen. --[[User:Lydia Pintscher]]
 +
 
 +
::The problem ist treated [https://www.mediawiki.org/wiki/Topic:Uv9byz8r66j55or5 here] yet I do not get the solution. --[[User:Olaf Simons|Olaf Simons]] ([[User talk:Olaf Simons|talk]]) 19:40, 10 September 2019 (CEST)
  
 
=== Wikidata context help when creating an entry not available on FactGrid ===
 
=== 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?
+
Wikidata offers complex context help when users want to create items like a biography - questions one would like to answer as well. Can we have the same?
 +
 
 +
:Da weiß ich nicht was du meinst leider. --[[User:Lydia Pintscher]]
 +
 
 +
[[File:Screenshot Personeneingabe Wikidata.png|thumb|Creating a person on Wikidata, screenshot]]
 +
 
 +
Ich gebe hier eine Person ein und Wikidata is in der Lage mir die relevanten nächsten Aussagen vorzuschlagen - das ist eigentlich weit besser als ein Formular zu erstellen (wie wir das zuerst vorhatten). Kann man die Vorschläge lenken? Kann man einen Vorschlagpfad generieren? Wenn Du eine Persion hast, dann geht es mit diesen Fragen los. Wenn die schon beantwortet sind, dann gehe mit folgenden weiter... Bei uns jedenfalls erscheint bei Eröffnung einer neuen Aussage kein Vorschlag in irgendeine Richtung.  --[[User:Olaf Simons|Olaf Simons]] ([[User talk:Olaf Simons|talk]]) 08:42, 23 May 2019 (CEST)
  
 
=== Commons images not displayed on FactGrid-Item Views ===
 
=== Commons images not displayed on FactGrid-Item Views ===
...though we can integrate them in Wiki pages we create.
+
...though we can integrate them in Wiki pages we create - the item-pages won't offer them.
 +
 
 +
:Hast du ein Beispiel das ich mir anschauen kann? --[[User:Lydia Pintscher]]
  
 
=== Foreign Language Labels ===
 
=== 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?
+
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: i.e. that a missing English label is automatically substituted by an existing German label?
 +
:Da bin ich mir nicht sicher. Muss ich rausfinden. --[[User:Lydia Pintscher]]
 +
 
 +
 
 +
=== We are still using Tinyurl ===
 +
While Wikidata has switched to a home run solution o short urls.
  
 
== QueryService related problems ==
 
== QueryService related problems ==
 +
=== SPARQL Script Requests ===
 +
* see: [[SPARQL Lab]]
 +
 
=== QueryService gives January 1 as default answer for full year dates ===
 
=== 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.
+
If we give a full year (e.g. on "date of birth") the Query Service will state January 1 as the date instead of leaving the day and month unspecified.
 +
 
 +
:Das Ticket dazu ist https://phabricator.wikimedia.org/T159160. Ich weiß leider gerade nicht was da der letzte Diskussionsstand ist. --[[User:Lydia Pintscher]]
  
 
=== QueryService gives output with wd:Q123 numbers ===
 
=== QueryService gives output with wd:Q123 numbers ===
though the links do actually go into the FactGrid resource
+
though the links do actually go into the FactGrid resource. This problem occurs on all levels: our Q-numbers are displayed in SPARQL searches as wd numbers. Tiny-urls open when activated with a Wikidata welcome page before we get the FactGrid results: http://tinyurl.com/y8zwjosq
 +
 
 +
:Der erste Teil ist glaube ich https://phabricator.wikimedia.org/T194180. Ich habe ein Ticket für den zweiten Teil aufgemacht: https://phabricator.wikimedia.org/T223582. --[[User:Lydia Pintscher]]
  
=== QueryService example searches are Wikidata searches and do not work on our database ===
+
=== QueryService example searches are actually Wikidata searches ===
though the links do actually go into the FactGrid resource
+
...and do not help you on our database.
 +
 
 +
:Das ist seit kurzem konfigurierbar. https://phabricator.wikimedia.org/T223586 habe ich aufgemacht um das für Factgrid zu konfigurieren. --[[User:Lydia Pintscher]]
  
 
=== Weird Results No.1 ===
 
=== Weird Results No.1 ===
Line 94: Line 137:
  
 
* [https://database.factgrid.de/query/#%23defaultView%3AMap%0ASELECT%20%3FKaufmann%20%3FKaufmannLabel%20%3FAdresse%20%3FAdresseLabel%20%3FGeokoordinaten%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20%3FKaufmann%20wdt%3AP165%20wd%3AQ36715.%0A%20%20%3FKaufmann%20wdt%3AP83%20wd%3AQ10279.%0A%20%20OPTIONAL%20%7B%20%3FKaufmann%20wdt%3AP208%20%3FAdresse.%20%7D%0A%20%20OPTIONAL%20%7B%20%3FAdresse%20wdt%3AP48%20%3FGeokoordinaten.%20%7D%0A%7D Map view: all merchants in Gotha whose addresses have geographic coordinates on FactGrid]
 
* [https://database.factgrid.de/query/#%23defaultView%3AMap%0ASELECT%20%3FKaufmann%20%3FKaufmannLabel%20%3FAdresse%20%3FAdresseLabel%20%3FGeokoordinaten%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20%3FKaufmann%20wdt%3AP165%20wd%3AQ36715.%0A%20%20%3FKaufmann%20wdt%3AP83%20wd%3AQ10279.%0A%20%20OPTIONAL%20%7B%20%3FKaufmann%20wdt%3AP208%20%3FAdresse.%20%7D%0A%20%20OPTIONAL%20%7B%20%3FAdresse%20wdt%3AP48%20%3FGeokoordinaten.%20%7D%0A%7D Map view: all merchants in Gotha whose addresses have geographic coordinates on FactGrid]
 +
 +
:Ich habe keine Ahnung. Lucas könnte helfen. --[[User:Lydia Pintscher]]
  
 
=== Weird Results No.2 ===
 
=== Weird Results No.2 ===
We are trying to step from "given names" as string [[Property:P88]] to given names as individual items.
+
We are trying to step from "given names" as string [[Property:P88]] to given names as individual items [[Property:P248]]. In order to get the names which we have to change we need a search for all P88 names with place in sequence information [[Property:P101]] information. Our searches fail:
  
* [https://database.factgrid.de/query/#SELECT%20%3FMensch%20%3FMenschLabel%20%3FVorname_n___string_%20%3FPosition__in_Abfolge_%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20%3FMensch%20wdt%3AP2%20wd%3AQ7.%0A%20%20OPTIONAL%20%7B%20%3FMensch%20wdt%3AP88%20%3FVorname_n___string_.%20%7D%0A%20%20OPTIONAL%20%7B%20%3FVorname_n___string_%20wdt%3AP101%20%3FPosition__in_Abfolge_.%20%7D%0A%7D list all the names which are registred as strings and note the place in sequence]
+
* [https://database.factgrid.de/query/#SELECT%20%3FMensch%20%3FVorname_n___string_%20%3FPosition__in_Abfolge_%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20%0A%20%20OPTIONAL%20%7B%20%3FMensch%20wdt%3AP88%20%3FVorname_n___string_.%20%7D%0A%20%20OPTIONAL%20%7B%20%3FVorname_n___string_%20pq%3AP101%20%3FPosition__in_Abfolge_.%20%7D%0A%7D list all the names which are registred as strings and note the place in sequence]
 +
* [https://database.factgrid.de/query/#SELECT%20%3FMensch%20%3FVorname_n___string_%20%3FPosition__in_Abfolge_%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20%0A%20%20OPTIONAL%20%7B%20%3FMensch%20wds%3AP88%20%3FVorname_n___string_.%20%7D%0A%20%20OPTIONAL%20%7B%20%3FVorname_n___string_%20pq%3AP101%20%3FPosition__in_Abfolge_.%20%7D%0A%7D different search script now with weird link-statements]
  
This query should tell us the entries we still have to change -  
+
:Ich habe keine Ahnung. Lucas könnte helfen. --[[User:Lydia Pintscher]]
* yet it gives us loads of obsolete entries and
 
* it cannot be persuaded to add the place in sequence [[Property:P101]] information which we wold try to keep with the new entries to make.
 
  
 
== Tools/features one would like to have ==
 
== Tools/features one would like to have ==
Line 109: Line 153:
  
 
One of the problems is that our instance looks for [[Item:Q969]] instead of [[Q969]]
 
One of the problems is that our instance looks for [[Item:Q969]] instead of [[Q969]]
 +
 +
:Das genannte Problem können wir hoffentlich mit dem Ticket von 2.1. lösen. --[[User:Lydia Pintscher]]
 +
 +
:* https://phabricator.wikimedia.org/T223548 Ticket gelöst, klappt aber dennoch nicht.
  
 
=== A tool to grab and import (selected) Wikidata information ===
 
=== A tool to grab and import (selected) Wikidata information ===
Line 114: Line 162:
  
 
=== A multilingual interface to just offer information ===
 
=== 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.
+
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 ===
 
=== An option to feed information into historical maps ===
Line 121: Line 169:
 
=== A recipe how to create Info-Boxes based on FactGrid Information ===
 
=== 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.
 
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.
 +
 +
:Das sollte jemand gut machen können der sich mit MediaWiki Templateprogrammierung und Wikidata auskennt. --[[User:Lydia Pintscher]]
 +
 +
=== Open Refine ===
 +
Seen a demonstration of Open refine and it seems it needs an integration on our wikibase installation before one can use the program to prepare data. Another task for someone with a clearer idea of the installation. --[[User:Olaf Simons|Olaf Simons]] ([[User talk:Olaf Simons|talk]]) 11:07, 26 October 2019 (CEST)
 +
* https://github.com/wetneb/openrefine-wikibase
  
 
== Requests for search scripts ==
 
== Requests for search scripts ==
Line 127: Line 181:
  
 
=== Cumulative personal Timeline ===
 
=== 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.
+
A cumulative timeline 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.
 +
 
 +
=== genealogies ===
 +
* Person backwards
 +
* two persons - are they related?
  
 
== Specific FactGrid wishes ==
 
== Specific FactGrid wishes ==
Line 137: Line 195:
 
=== Skin ===
 
=== Skin ===
 
Important gain a more independent position in the eyes of university, library and archive people.
 
Important gain a more independent position in the eyes of university, library and archive people.
 +
 +
We would need someone with Skin expertise...
  
 
=== An interface to move the ''The Gotha Illuminati Research Base'' into the FactGrid ===
 
=== 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.
+
The ''The Gotha Illuminati Research Base'' was/is a conventional media wiki and we should win a superior functionality here on the FactGrid.
 +
 
 +
* Old media-wiki https://projekte.uni-erfurt.de/illuminaten/Main_Page  
 +
* New (and we are still looking for a better concept here on FactGrid): https://database.factgrid.de/wiki/The_Gotha_Illuminati_Research_Base
  
 
=== A clearer idea of how we would like to be quoted ===
 
=== 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 [[Item:Q11305]]
 
FactGrid datasets have specific research statements - but how do we want them to be referred to in footnotes? See [[Item:Q11305]]
 +
 +
=== Website security ===
 +
https://observatory.mozilla.org/analyze/database.factgrid.de : "D-", CSP, HSTS, XFO, XSS missing.
  
 
== Data we should like to have ==
 
== Data we should like to have ==
 
* Matrikel of German universities
 
* Matrikel of German universities
 
* Logis-Verzeichnisse Göttinger Studenten (halbjährlich)
 
* Logis-Verzeichnisse Göttinger Studenten (halbjährlich)
 +
 +
== Hosting FactGrid ==
 +
* https://professional.wiki/ should contact and find out...

Latest revision as of 10:38, 26 October 2019

FactGrid:Troubleshooting/archive

Contents

Advice: best practice data structures

Changing entities and cuts through time

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 with changing owners who give the company names. Our system must be able to make sense of practically any imprint - and it should at the same moment understand how the changing imprint information is actually connected to one and the same company. Munich does not have 57 companies from 1500 to 1850 but six under changing names in this genealogy Münchner Buchhandel 1500–1850 - and this is an image we want to give on a clear sighted SPARQL-search.

  • Should we create different items 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).

Daran scheiden sich die Geister... Das ist ein klassisches Ontologieproblem. Man kann es so oder so machen. Denny könnte eine gute Person sein das mal für deinen genauen Fall durchzudiskutieren und zu schauen ob eins mehr Sinn macht. --User:Lydia Pintscher

What should we do with our 1500 transcripts of documents?

We have started to put the transcript of Item:Q22976 on D-Q22976. Was that a good idea? (we want the transcript to appear in full text search), yet we would rather have it on one page with all the meta data.


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?

Ich kenne mich leider mit Wikisource nicht aus. Tpt (thomas@pellissier-tanon.fr) hat davon und von Wikidata sehr viel Ahnung und kann wahrscheinlich am sinnvollsten was sagen. --User:Lydia Pintscher

Scholia

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)

Sowas sollte jeder vernünftige php coder hinbekommen. --User:Lydia Pintscher

Specific problems of our Wikibase Installation

"Item:Q123" or direct "Q123"

Unlike Wikidata FactGrid states Items as "Item:" in the URL. This might be the cause of incompatibilities as we see them in our Reasonator interface. (Reasonator apparently expects the Q123 link where we have the "Item"-link

Dafür habe ich dir ein Ticket aufgemacht: https://phabricator.wikimedia.org/T223548 --User:Lydia Pintscher

In the headline of item pages that Item ID is shown, but not the name space, e.g. "human (Q7)". In the project name space the name space is shown "FactGrid:Troubleshooting Range", in the main name space and special name space it is not.

"Item:Q123" or "Item:123"

The "Q" is present in every item ID and therefore does not contain extra information. It should probably be removed. Also, it would be easier for international use to only have numbers in the item ID.

GND Identifiers do not link

See Item:Q133. Why does the GND number not linkt to the GND as in Wikidata?

We have the same problem with PND book numbers that should refer into to GBV catalogue.

Dafür habe ich dir ein Ticket aufgemacht: https://phabricator.wikimedia.org/T223552 --User:Lydia Pintscher

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

  • We can set a Q123 link (that refers to a non existing page.
  • We can set an Item:Q123 link - and sometimes we get the title on the ink - but not necessarily (works wel after moving a page and ends after saving it again)
  • A {{}} template does not work.
Hast du ein Beispiel auf Wikidata, wo es so funktioniert wie du es haben willst? Dann schau ich es mir an. Das sollte gehen. --User:Lydia Pintscher

Description 250 character limit

Many imports failed since they had descriptions of more than 250 signs. Daniel Mietchen said we can modify the character limits on our own Wikibase instance - would be good to allow perhaps 500-1000 characters.

Die Descriptions sind vor allem zur Disambiguierung gedacht zum Beispiel im Suchfeld rechts oben oder wenn du ein anderes Item in einem Statement verlinkst um sicherzustellen dass du den richtigen Fritz Müller auswählst wenn es 10 davon gibt. Deshalb sind die sehr kurz gehalten und die Beschränkung ist von unserer Seite aus gewollt bisher. Kannst du etwas genauer erklären was du machen willst mit den Descriptions und was da rein soll? Vielleicht ist es besser als ein Statement aufgehoben aber das kann ich noch nicht sagen.
Soweit ich weiß ist das im Moment nicht konfigurierbar. --User:Lydia Pintscher

Time: Hours and Minutes cannot be stated

We could actually give events (like conference papers) on individual days. The software has the option but it does not work in Wikidata or on our platform.

Die Eingabe von genauen Zeiten ist noch nicht möglich weil das eine Menge Komplexität mit Zeitzonen mit sich bringt. https://phabricator.wikimedia.org/T57755 ist das Ticket dafür. Dem müssen wir uns mal annehmen. --User:Lydia Pintscher

Time: Format

Currently it says on the bottom of that page "This page was last edited on 6 July 2019, at 18:05." and on in the history "18:05, 6 July 2019" - two different formats no statement found what for. Furthermore in the FG blog and other places formats based on ISO 8601 appear. Proposal: standardize on ISO 8601.

Time: Seconds not shown in page history

In the contributions lists seconds are not shown, so one cannot see in which order edits have been made, even worse, a change that is labeled "current" comes before another one on the same page:

18:05, 6 July 2019 (diff | hist) . . (+236)‎ . . FactGrid:Troubleshooting Range ‎ (→‎"Item:Q123" or "Item:123")
17:50, 6 July 2019 (diff | hist) . . (+63)‎ . . Example (Q...) ‎ (‎Added [en] description: human)
17:50, 6 July 2019 (diff | hist) . . (+64)‎ . . Example (Q...) ‎ (‎Added [de] description: Mensch) (current)
17:49, 6 July 2019 (diff | hist) . . (+1)‎ . . Property talk:P163 ‎ (...)

pdf and other uploads

that should be a switch in the LocalSettings but might also be a database issue to be resolved in Erfurt:

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

Bin nicht sicher was da das Problem ist. Da kannst du Lucas glaube ich kurz ansprechen und ihn fragen ob das was ist was im Rechenzentrum gemacht werden muss oder in den Einstellungen. --User:Lydia Pintscher
The problem ist treated here yet I do not get the solution. --Olaf Simons (talk) 19:40, 10 September 2019 (CEST)

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 one would like to answer as well. Can we have the same?

Da weiß ich nicht was du meinst leider. --User:Lydia Pintscher
Creating a person on Wikidata, screenshot

Ich gebe hier eine Person ein und Wikidata is in der Lage mir die relevanten nächsten Aussagen vorzuschlagen - das ist eigentlich weit besser als ein Formular zu erstellen (wie wir das zuerst vorhatten). Kann man die Vorschläge lenken? Kann man einen Vorschlagpfad generieren? Wenn Du eine Persion hast, dann geht es mit diesen Fragen los. Wenn die schon beantwortet sind, dann gehe mit folgenden weiter... Bei uns jedenfalls erscheint bei Eröffnung einer neuen Aussage kein Vorschlag in irgendeine Richtung. --Olaf Simons (talk) 08:42, 23 May 2019 (CEST)

Commons images not displayed on FactGrid-Item Views

...though we can integrate them in Wiki pages we create - the item-pages won't offer them.

Hast du ein Beispiel das ich mir anschauen kann? --User:Lydia Pintscher

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: i.e. that a missing English label is automatically substituted by an existing German label?

Da bin ich mir nicht sicher. Muss ich rausfinden. --User:Lydia Pintscher


We are still using Tinyurl

While Wikidata has switched to a home run solution o short urls.

QueryService related problems

SPARQL Script Requests

QueryService gives January 1 as default answer for full year dates

If we give a full year (e.g. on "date of birth") the Query Service will state January 1 as the date instead of leaving the day and month unspecified.

Das Ticket dazu ist https://phabricator.wikimedia.org/T159160. Ich weiß leider gerade nicht was da der letzte Diskussionsstand ist. --User:Lydia Pintscher

QueryService gives output with wd:Q123 numbers

though the links do actually go into the FactGrid resource. This problem occurs on all levels: our Q-numbers are displayed in SPARQL searches as wd numbers. Tiny-urls open when activated with a Wikidata welcome page before we get the FactGrid results: http://tinyurl.com/y8zwjosq

Der erste Teil ist glaube ich https://phabricator.wikimedia.org/T194180. Ich habe ein Ticket für den zweiten Teil aufgemacht: https://phabricator.wikimedia.org/T223582. --User:Lydia Pintscher

QueryService example searches are actually Wikidata searches

...and do not help you on our database.

Das ist seit kurzem konfigurierbar. https://phabricator.wikimedia.org/T223586 habe ich aufgemacht um das für Factgrid zu konfigurieren. --User:Lydia Pintscher

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...

Ich habe keine Ahnung. Lucas könnte helfen. --User:Lydia Pintscher

Weird Results No.2

We are trying to step from "given names" as string Property:P88 to given names as individual items Property:P248. In order to get the names which we have to change we need a search for all P88 names with place in sequence information Property:P101 information. Our searches fail:

Ich habe keine Ahnung. Lucas könnte helfen. --User:Lydia Pintscher

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 Item:Q969 instead of Q969

Das genannte Problem können wir hoffentlich mit dem Ticket von 2.1. lösen. --User:Lydia Pintscher

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.

Das sollte jemand gut machen können der sich mit MediaWiki Templateprogrammierung und Wikidata auskennt. --User:Lydia Pintscher

Open Refine

Seen a demonstration of Open refine and it seems it needs an integration on our wikibase installation before one can use the program to prepare data. Another task for someone with a clearer idea of the installation. --Olaf Simons (talk) 11:07, 26 October 2019 (CEST)

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 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.

genealogies

  • Person backwards
  • two persons - are they related?

Specific FactGrid wishes

Important in joint ventures.

FactGrid-Logo.svg

Skin

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

We would need someone with Skin expertise...

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

The The Gotha Illuminati Research Base was/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 Item:Q11305

Website security

https://observatory.mozilla.org/analyze/database.factgrid.de : "D-", CSP, HSTS, XFO, XSS missing.

Data we should like to have

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

Hosting FactGrid