Gratisdata:Contact the development team

    Add links
    Add topic
    From Gratisdata

    Contact the development team

    Gratisdata development is ongoing. You can leave notes for the development team here or report bugs on Phabricator.

    If you have questions or bug reports related to search on Gratisdata, please add them to this page. If you have suggestions or requests regarding the entity suggester ranking, please use this page. Any other report you want to give? they all go on this page.

    | On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2023/11.

    Error saving edits on wikibase entities[edit]

    Tracked in Phabricator
    Task T9032
    InvalidWikibase error when adding sitelinks in the miraheze siteLinkGroup (gratisdatawiki)
    Let me just leave a note here; I have been unable to make edit to items, when trying to add aliases, desciption, statements, or sitelinks, it throws an error saying Could not save due to an error.. Although Danniel has said that when he was making this edit, he didn't encounter any errors. @Lois: I would appreciate if you could make any edits to wikibase items and see if it works for you. Ugochimobi (talk) 22:54, 5 April 2022 (UTC)Reply[reply]
    Just a note: this was resolved by changing $wmgWikibaseRepoUrl from HTTP to HTTPS. This should further remain so. Ugochimobi (talk) 21:26, 7 May 2022 (UTC)Reply[reply]

    Find a way to map our property concept URIs with Wikidata[edit]

    So I had a discussion on GitHub with Thad Guidry, a volunteer developer who was around when Wikidata's properties were mapped with Schema.org's properties about 7 years ago as of 2022, and he mentioned that the best way of mapping ours is to link our property concept URIs with Wikidata's properties.

    It can be linked by using the equivalent property property on Wikidata to link to our own properties using our property concept URI as the value.

    Example: If we want to externally map our exact match (P34) property to Wikidata's exact match property, then all we need to do is; on Wikidata's exact match property, add the equivalent property property and enter our exact match (P34) property's concept URI (which is https://gratisdata.miraheze.org/entity/P34) as the value. So on Wikidata's exact match entity it would look like;

    equivalent property
    Normal rank https://gratisdata.miraheze.org/entity/P34 edit
    0 references
    add reference


    add value
    Ugochimobi (talk) 22:35, 7 May 2022 (UTC)Reply[reply]

    Gratisdata props to be mapped with Wikidata's props[edit]

    The following properties are to be mapped, more properties should be added at the bottom of this table
    S/N Gratisdata property Wikidata property Comment Status
    1 instance of (P3) Property:P31 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    2 subclass of (P12) Property:P279 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    3 exact match (P34) Property:P2888 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    4 equivalent property (P169) Property:P1628 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    5 equivalent class (P199) Property:P1709 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    6 occupation (P6) Property:P106 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    7 member of (P97) Property:P463 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    8 member of sports team (P672) Property:P54 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    9 ancestral home (P673) Property:P66 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    10 native language (P674) Property:P103 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    11 title of chess person (P675) Property:P2962 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    12 victory (P676) Property:P2522 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    13 has pet (P677) Property:P1429 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    14 present in work (P678) Property:P1441 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    15 life expectancy (P679) Property:P2250 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    16 total fertility rate (P680) Property:P4841 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    17 external superproperty (P186) Property:P2235 This property should be mapped with Wikidata's equivalent property just as example given above Pending
    18 external subproperty (P89) Property:P2236 This property should be mapped with Wikidata's equivalent property just as example given above Pending

    --Ugochimobi (talk) 15:18, 11 May 2022 (UTC)Reply[reply]

    Disable Wikibase Local Media extension[edit]

    The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

     Resolved per my comments below Ugochimobi (talk) 08:06, 12 May 2022 (UTC)Reply[reply]

    SO, on troubleshooting why we currently can't generate entity data dumps via Special:EntityData with all data formats like .rdfxml, .ttl, .n3, .jsonld, etc, except with just .json, I realised that Extension:Wikibase Local Media has an interference with the entity data formats. So we have to disable the extension to make it possible to generate entity data dumps with the above formats, and possibly more.

    But there's a little problem;

    Wikibase Local Media extension makes it possible to add local media to statements, and it also comes with a datatype Media file for properties. We actually don't need this since we already have Commons media file datatype.

    Now, our image (P386) and logo image (P387) properties uses this Media file datatype, which will break a lot of things if the extension is disabled at once. We have to find a way to change the datatype to Commons media file.

    But there's a good news;
    Tracked in Phabricator
    Task T9205
    ResolvedRun the changePropertyDataType.php against P386/P387

    We can change datatype of these properties by running the changePropertyDataType.php script against them to change their datatype. Ugochimobi (talk) 17:12, 10 May 2022 (UTC)Reply[reply]

    This is ✓ Done by @Reception123
    Related links
    -- Ugochimobi (talk) 07:43, 12 May 2022 (UTC)Reply[reply]
    I'm ✓ Done disabling the Wikibase Local Media extension and taking Facebook (Q101) as an example, I can confirm that we can now generate entity data with the following formats;
    And they all rendered properly as expected, hence this is  Resolved Ugochimobi (talk) 07:59, 12 May 2022 (UTC)Reply[reply]
    The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.
    Retrieved from "https://gratisdata.miraheze.org/w/index.php?title=Gratisdata:Contact_the_development_team&oldid=34033"