Van experiment naar werking: verschil tussen versies

Huidige versie van 29 feb 2024 om 14:23

This wikibase started as an experiment on wikibase.cloud, but we are setting up this production environment at kg.kunsten.be We have some work to be done, before everything is completely operational. Here are the work packages and tasks:

Finalise setup

User management > support needed from professional.wiki
- how do we distinguish between people that can only consult the data
- people that can contribute to the entities (create and edit entities, add statements, ... but no new properties)
- people that can make new properties
- superusers that can also work in the backend and so on
Are all the relevant packages installed and activated > mr henry / professional.wiki / kunstenpunt
...

Metadata transfer

finalise the metadata transfer from the legacy databases to the wikibase > Tom should be able to handle this
identify how to map kg.kunsten.be properties and entities to e.g. https://data.vlaanderen.be/doc/applicatieprofiel/cultuurparticipatie/ or wikidata.org > support needed from professional.wiki (what are the good practices here, automate this?)

Image transfer

also transfer the image files from the legacy databases to the wikibase > help professional wiki? Example REST api call?

Rich text transfer

also transfer the rich text fields from the legacy database to the wikibase > help professional wiki? Example REST api call? best approach for this, e.g. insite link?

Forms

create user friendly forms that accumulate a payload of (meta)data that can be sent to wikibase over the API
- UX has already been done > mr henry
- research if we need to build seperate html forms, or if we can use "Page Forms" in wikibase itself? Mr Henry / professional wiki?

Databank.kunsten.be

create the SPARQL queries to extract the data from the wikibase so that the results can be visualised on databank.kunsten.be > tom can do some, but might need some SPARQL help from professional.wiki
- I'll be starting here https://docs.google.com/spreadsheets/d/1SMGM2KPUFYmCuwSR9ypHU1IXrk2VXwxpedCGH20lQ0k/edit#gid=0
adjust the data management strategy at databank.kunsten.be to handle wikibase > mr henry

@@ Regel 1: / Regel 1: @@
-Begin april hebben we het data model voor actoren en activiteiten min of meer op punt, gebaseerd op wat ervaring en enkele voorbeelden. Tijd om te testen of dit nu ook echt werkt.
+This wikibase started as an experiment on wikibase.cloud, but we are setting up this production environment at kg.kunsten.be We have some work to be done, before everything is completely operational. Here are the work packages and tasks:
-== Ingest van Belgische gemeenten en steden ==
+=== Finalise setup ===
-Op basis van ergens een lijst heb ik op 9 april 2022 belgische gemeenten en steden via quickstatements ingested. Daarbij moet er ergens iets fout gelopen zijn, want een aantal gemeenten zitten er dubbel in:
+* User management > support needed from professional.wiki
+** how do we distinguish between people that can only consult the data
+** people that can contribute to the entities (create and edit entities, add statements, ... but no new properties)
+** people that can make new properties
+** superusers that can also work in the backend and so on
+* Are all the relevant packages installed and activated > mr henry / professional.wiki / kunstenpunt
+* ...
- SELECT ?landLabel ?itemLabel (GROUP_CONCAT(?item) as ?itemURLs) (count(?itemLabel) as ?itemLabelCount) {
+=== Metadata transfer ===
-  ?item <http://osloddt.wiki.opencura.com/prop/direct/P1> <http://osloddt.wiki.opencura.com/entity/Q229>;
-        <http://osloddt.wiki.opencura.com/prop/direct/P20> ?land.
-  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],nl,en" . }
- }
- GROUP BY ?landLabel ?itemLabel
- HAVING (count(?itemLabel) > 1)
-Dit is dus een TODO om die waar nodig te mergen.
+* finalise the metadata transfer from the legacy databases to the wikibase > Tom should be able to handle this
+* identify how to map kg.kunsten.be properties and entities to e.g. https://data.vlaanderen.be/doc/applicatieprofiel/cultuurparticipatie/ or wikidata.org > support needed from professional.wiki (what are the good practices here, automate this?)
-== Ingest van gecombineerde personen, organisaties en venues ==
+=== Image transfer ===
-=== Samenstellen van de lijst ===
+* also transfer the image files from the legacy databases to the wikibase > help professional wiki? Example REST api call?
-==== Uit de legacy databanken ====
+=== Rich text transfer ===
-==== Uit havelovewilltravel ====
+* also transfer the rich text fields from the legacy database to the wikibase > help professional wiki? Example REST api call? best approach for this, e.g. insite link?
-=== Quickstatements ===
+=== Forms ===
-=== Opkuis ===
+* create user friendly forms that accumulate a payload of (meta)data that can be sent to wikibase over the API
+** UX has already been done > mr henry
+** research if we need to build seperate html forms, or if we can use "Page Forms" in wikibase itself? Mr Henry / professional wiki?
-Een massa import gaat gepaard met ruis. Er is dus heel wat opkuiswerk nodig. We denken meteen aan de kunsthogescholen en de cultuurcentra, maar in de legacy databanken zaten ook heel wat personen of organisaties dubbel. Dan is er ook het oude zeer van organisaties die ook venues zijn in de legacy databanken, en die we nu bij mekaar brengen.
+=== Databank.kunsten.be ===
-==== Kunsthogescholen ====
+* create the SPARQL queries to extract the data from the wikibase so that the results can be visualised on databank.kunsten.be > tom can do some, but might need some SPARQL help from professional.wiki
+** I'll be starting here <nowiki>https://docs.google.com/spreadsheets/d/1SMGM2KPUFYmCuwSR9ypHU1IXrk2VXwxpedCGH20lQ0k/edit#gid=0</nowiki>
-==== Cultuurcentra ====
+* adjust the data management strategy at databank.kunsten.be to handle wikibase > mr henry
-==== Personen en organisaties ====
-==== Venues en organisaties ====
-== Ingest van activiteiten ==